Re: [LAD] JACK + PA Latency

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Fons Adriaensen <fons@...>
Cc: linux-audio-dev@lists.linuxaudio.org <linux-audio-dev@...>
Date: Monday, September 30, 2013 - 3:39 pm

--047d7b33cf64f3aba504e79ba3af
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Sep 30, 2013 at 11:33 AM, Fons Adriaensen 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.

--047d7b33cf64f3aba504e79ba3af
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Sep 30, 2013 at 11:33 AM, Fons Adriaensen <fons@linuxaud=
io.org
> wrote:
On Tue, Oct 01, 2013 at 12=
:04:37AM +1000, Patrick Shirkey wrote:

> The most obvious potential violator is the bridge code between PA and =
ALSA

well at

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.=
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.

--047d7b33cf64f3aba504e79ba3af--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAD] JACK + PA Latency, Patrick Shirkey, (Fri Sep 27, 2:42 pm)
Re: [LAD] JACK + PA Latency, Fons Adriaensen, (Fri Sep 27, 3:29 pm)
Re: [LAD] JACK + PA Latency, Patrick Shirkey, (Fri Sep 27, 4:47 pm)
Re: [LAD] JACK + PA Latency, Patrick Shirkey, (Fri Sep 27, 5:09 pm)
Re: [LAD] JACK + PA Latency, Fons Adriaensen, (Fri Sep 27, 8:53 pm)
Re: [LAD] JACK + PA Latency, Patrick Shirkey, (Sun Sep 29, 7:57 am)
Re: [LAD] JACK + PA Latency, Paul Davis, (Mon Sep 30, 12:19 am)
Re: [LAD] JACK + PA Latency, Fons Adriaensen, (Mon Sep 30, 11:50 am)
Re: [LAD] JACK + PA Latency, Patrick Shirkey, (Mon Sep 30, 12:15 pm)
Re: [LAD] JACK + PA Latency, Fons Adriaensen, (Mon Sep 30, 1:30 pm)
Re: [LAD] JACK + PA Latency, Patrick Shirkey, (Mon Sep 30, 2:04 pm)
Re: [LAD] JACK + PA Latency, Fons Adriaensen, (Mon Sep 30, 3:33 pm)
Re: [LAD] JACK + PA Latency, Paul Davis, (Mon Sep 30, 3:39 pm)
Re: [LAD] JACK + PA Latency, Patrick Shirkey, (Tue Oct 1, 5:22 am)
Re: [LAD] JACK + PA Latency, Ralf Mardorf, (Tue Oct 1, 8:59 am)
Re: [LAD] JACK + PA Latency, Ralf Mardorf, (Sat Sep 28, 2:41 am)