Re: [GnomeMeeting-devel-list] Choppy Audio / Audio Dropout
- From: Damien Sandras <dsandras seconix com>
- To: GnomeMeeting development mailing list <gnomemeeting-devel-list gnome org>
- Subject: Re: [GnomeMeeting-devel-list] Choppy Audio / Audio Dropout
- Date: Fri, 31 Mar 2006 11:53:52 +0200
Thank you Craig, for your investigations.
I do not understand why the problem occurs on your system, and not on
mine. I have a very old P3 500, and I can successfully compile while
using Ekiga with audio and video at the same time, without any audio
dropout.
Le vendredi 31 mars 2006 à 10:44 +0100, Craig Shelley a écrit :
> On Fri, 2006-03-31 at 09:31 +0200, Damien Sandras wrote:
> > Hi Craig,
> >
> >
> > There is a variable named "soundChannelBuffers" in src/opal/pcss.cxx.
> >
> > Just to make sure, can you try changing its value to 1 and to 3, 4, ...
> > to see if it makes a difference without your patch or not?
> >
>
> Hi,
>
> I have not actually tested it, but I can see that this variable
> eventually gets copied into storedPeriods within the pwlib alsa plugin.
> Therefore this should eliminate my need to use the following override
> hack:
>
> //Try to get a bigger buffer (this only seems to work for playback)
> //FIXME this is a hack, it should be done in opal, or somewhere else
> storedPeriods = 15;
>
> I originally changed that value to 15, and it is all that is required to
> eliminate the choppy playback. It makes me wonder that if so many people
> are able to get away with a value of 2, my system must be really quite
> bad.
> I just tried it again with various values, and found that if using chrt
> to set the priority of the ekiga process, this value can be left at 2,
> without hardware audio dropouts. Otherwise without using chrt, it has to
> be left at 15.
>
> One thing that concerns me a little is that the Lost Packets, Late
> Packets and Out of Order packets statistics remain solidly on 0.0%, and
> yet I can hear the effects of loading on this Internet connection which
> is shared with other machines.
>
> Also, I think my kernel is a bit dodgy, on two occasions I have had a
> hard lock when issuing the chrt command. It usually happens when the
> command is issued as the the ekiga process is spawning its threads.
>
> One final observation is that I have just this second noticed my X
> server running with a nice value of -10. This is the likely cause of
> some of my trouble. Investigating...
>
> Cheers,
>
> _______________________________________________
> Gnomemeeting-devel-list mailing list
> Gnomemeeting-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnomemeeting-devel-list
--
_ Damien Sandras
(o-
//\ Ekiga Softphone: http://www.ekiga.org/
v_/_ FOSDEM 2006 : http://www.fosdem.org/
SIP Phone : sip:dsandras ekiga net
sip:600000 ekiga net
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]