Re: [Ekiga-list] PTLIB alsa plugin status

Derek Smithies wrote:
On Sat, 28 Feb 2009, Alec Leamas wrote:

Derek Smithies wrote:

On Fri, 27 Feb 2009, Alec Leamas wrote:
I need a whisky.
Coffee is much better. Don't add any impurities though (milk, sugar etc)
I'm was actually using both whisky AND coffe w milk. Sorry, no offense... :-)

After some serious fights w the build system, I've been able to add a simple PTRACE to the SetBuffers method in sound_alsa.cxx. Trimmed output:

13:45:49.348      ALSA    Setting buffers, size: 3840, count: 5
13:45:49.402      ALSA    Device default Opened
13:45:49.438      ALSA    Setting buffers, size: 320, count: 5

It is set in opal in

 where soundChannelBuffers is set to the supplied parameter value.

This comes out of the pcssendpoint class, which

which ends up coming from: a method of the pcss endpoint which gets the user defined buffer depth...
    soundChannelBuffers = pcss endpoint.GetSoundChannelBufferDepth()

so you know what ?

I think this is a bug from outside of ptlib&opal. The default values for codec sizes in ptlib&opal are for a count of 2 buffers (unix) and 3 buffers(windows).


Indeed. I have submitted a temporary patch to Not tested, but should be better than today. If it not makes other problems visible...Many thanks for your help with his, I wouldn't really have a chance without it.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]