Hi,
On Sat, 28 Feb 2009, Alec Leamas wrote:
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...
:-)
No offense taken. I put that comment in to lighten the tone a little.
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:
yeah - it is much easier to avoid such battles and put in cerr
statements...
These battles are a pain and a complete waste of time. They really really
annoy me. Like, autoconf was supposed to remove hassle.
It hasn't.
The kernel does not use autoconf -- which suggests to me that autoconf is
not all capable. The ptlib&opal build system consists of multiple projects
that interdepend on each other. autoconf (ideally) requires us to
duplicate code and directories, and separate the projects out. forget
that.
Derek.
> Derek Smithies wrote:
Hi,
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...
:-)
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
which verifies Andreas' logs i. e., this is what causes the oversized alsa
hw buffer. I made a quick search, there are no references to SetBuffers in
the plugin code. So these calls comes from the upper layers. For the moment
I'll stick to the alsa plugin and will not investigate this any further.
_______________________________________________
ekiga-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/ekiga-list
--
Derek Smithies Ph.D.
IndraNet Technologies Ltd.
Email: [email protected]
ph +64 3 365 6485
Web: http://www.indranet-technologies.com/
_______________________________________________
ekiga-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/ekiga-list
