30 Sep
2013
30 Sep
'13
5:39 p.m.
On Mon, Sep 30, 2013 at 11:33 AM, Fons Adriaensen <fons(a)linuxaudio.org>wrote;wrote:
On Tue, Oct 01, 2013 at 12:04:37AM +1000, Patrick
Shirkey wrote:
the linux mobile world has partially adopted PA as a native audio API
(something PA's designer did not intend to happen). there are audio device
streams that are accessible only via PA, much as FFADO is (or was) the only
way in or out of a firewire device. even without this, there are control
issues (related to audio "session management", i.e. when one app has to be
suspended). this may or may not have something to do with it.
The most obvious potential violator is the bridge
code between PA and
ALSA
because it's the one place that no one really
seems to understand well at
the moment.
That would then affect *all* apps using PA via ALSA (which seems
to be the only way)...
I still don't understand the purpose of all this. An application
that can't use Jack can still connect to it using the ALSA jack
plugin, you don't need PA for this. A quick test here shows
that the latency in that case is as solid as it gets.