Hello all,
we are using Pulse Audio API to playback audio received from network. So
far we are using pa_simple_api, with this we get latency of 2+ seconds.
>From internet documents we got to about PA_STREAM_ADJUST_LATENCY flags. But
it seem this flag can be set for PA_STREAM_API. We tried to set
On Mon, 2013-08-26 at 15:04 +0200, Svein Seldal wrote:
On 08/26/2013 02:36 PM, Tanu Kaskinen wrote:
No, PA doesn't offer that. Reading and writing to the sound card is
handled completely separately, from different threads, so there's no
read/write synchronization in the server either.
On Mon, 2013-08-26 at 13:31 +0200, Svein Seldal wrote:
Hi
I'm working on using a [dedicated] linux box for an audio filtering use.
My intentions is to take stereo audio in, process it, and play the
result on audio out (all on the same sound device). The catch is that
this app requires as
Too bad. Using PA is convenient, as it's already integrated into most
distros. And I am apparently misinterpreting the PA claim Good low
latency behaviour -- but I guess that this depending on the definition
of low latency...
Dedicated box means that this PC is a prototype for some real-world
On Fri, 2013-04-05 at 11:10 +0200, David Henningsson wrote:
2) Second is all the atomic operations we do, in handling our flists.
There seem to be quite a penalty for doing memory fence operations, and
there are plenty of those for just getting/putting something into an
flist. Here it might
Not sure what you mean with sink and ring buffer. When mixing, data
goes from the sink-input / client-server buffer into the DMA buffer
directly.
Please look at protocol-native.c. I am not sure why there is this
division of latency in two, for low-latency you can probably decrease
the
On 11/07/2012 09:59 PM, Pierre-Louis Bossart wrote:
For those who aren't following the planet, thought I'd like you know
that I've put up notes from PulseConf up at:
http://arunraghavan.net/2012/11/pulseconf-2012-report/
One comment on the low-latency case for desktop gaming with a 16ms
