Red Hat Bugzilla – Bug 141945
Microphone input delay resp. lag.
Last modified: 2015-01-04 17:13:38 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
I file this issue under gnomemeeting since I noticed it with this
application first. However, it could well be rather a sound driver or
Description: microphone input lags behind for more than one second.
This can be seen with gnomemeeting, i.e. a LAN call to a netmeeting
client gives voice delays of over one second, where a XP/netmeeting
call from the same (dual boot) machine gives delays at most of 50ms,
i.e. XP/netmeeting performs way better on the same hardware.
The delay can also be observed eg via cat /dev/dsp > /dev/dsp, where
voice spoken into the mic is heard only after more than one second.
My soundcard chip is identified as Ensoniq 5880 AudioPCI running with
the corresponding Alsa driver.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Any application that processes soundcard input exhibits this
behaviour, gnomemeeting is an example.
Correction: all application tests I did, i.e. cat/aplay etc.,
apparently involved extensive buffering. This was pointed out to me on
the alsa mailing list. I was advised to try arecord/aplay with the
--buffer-size option, and tests with values up to 512 exhibited hardly
noticable to very little lag.
Especially, the gnomemeeting lags which initially made me investigate
the whole situation then must happen on application and not on
To restate the original problem: with gnomemeeting <-> netmeeting
connections on LAN I get noticably more lag when voice is going
gnomemeeting -> netmeeting than in the opposite direction, that lag
amounting to about one to two seconds. According to gnomemeeting irc
this seems to be way to much delay.
I'll now try to optimize gnomemeeting settings, and depending on the
outcome this whole issue may well turn out not to be a bug. In the
meantime, I set the report status to NEEDINFO and will hopefully come
back with a success report in a couple of days.
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem. Please update to this new kernel, and
report whether or not it fixes your problem.
If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.
This bug has been automatically closed as part of a mass update.
It had been in NEEDINFO state since July 2005.
If this bug still exists in current errata kernels, please reopen this bug.
There are a large number of inactive bugs in the database, and this is the only
way to purge them.