Re: [LAD] JACK latency API clarifications

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Stefano D'Angelo <zanga.mail@...>
Cc: The Linux Audio Developers' Mailing List <linux-audio-dev@...>
Date: Thursday, February 20, 2014 - 10:45 pm

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

On Thu, Feb 20, 2014 at 5:32 PM, Stefano D'Angelo wrote:

> Hi all,

the latency callback will be issued (twice, once for upstream, once for
downstream) after one of two things happens:

* the graph changes
* a client calls jack_recompute_total_latencies()

you would call the latter if something happens that alters your clients own
latency (e.g the change to some parameter of an algorithm that causes your
client to change its latency). then you wait for the latency callback and
reset your port latencies.

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

On Thu, Feb 20, 2014 at 5:32 PM, Stefano D'Angelo <zanga.ma=
il@gmail.com
> wrote:
Hi all,

Let's say I have a client that introduces an amount of latency that&#39=
;s
variable at runtime and potentially unbounded. From JACK's docs it
seems that you need to recompute the min/max latencies in the latency
callback that's called "by the server" whenever it feels like=
, but you
can force that by calling jack_recompute_total_latencies (right?).

The problem is, you are advised to call this last function only after
calling jack_port_set_latency_range(), which you should only call in
the latency callback, which may be called next month... am I dumb
(probably) or is there a deadly loop?t=
he latency callback will be issued (twice, once for upstream, once for down=
stream) after one of two things happens:=A0=A0 * the gra=
ph changes
=A0=A0 * a client calls jack_recompute_total_latencies()=
you would call the latter if something happens that alters your =
clients own latency (e.g the change to some parameter of an algorithm that =
causes your client to change its latency). then you wait for the latency ca=
llback and reset your port latencies.
=A0

--f46d0444ea955be6a104f2de44ef--

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

Messages in current thread:
[LAD] JACK latency API clarifications, Stefano D'Angelo, (Thu Feb 20, 10:32 pm)
Re: [LAD] JACK latency API clarifications, Robin Gareus, (Thu Feb 20, 10:47 pm)
Re: [LAD] JACK latency API clarifications, Paul Davis, (Thu Feb 20, 10:45 pm)
Re: [LAD] JACK latency API clarifications, Stefano D'Angelo, (Thu Feb 20, 11:05 pm)
Re: [LAD] JACK latency API clarifications, Paul Davis, (Thu Feb 20, 11:08 pm)
Re: [LAD] JACK latency API clarifications, Stefano D'Angelo, (Thu Feb 20, 11:09 pm)
Re: [LAD] JACK latency API clarifications, Stefano D'Angelo, (Fri Feb 21, 2:38 pm)
Re: [LAD] JACK latency API clarifications, Paul Davis, (Fri Feb 21, 2:51 pm)
Re: [LAD] JACK latency API clarifications, Stefano D'Angelo, (Fri Feb 21, 3:04 pm)
Re: [LAD] JACK latency API clarifications, Paul Davis, (Fri Feb 21, 3:21 pm)
Re: [LAD] JACK latency API clarifications, Lieven Moors, (Fri Feb 21, 6:51 pm)
Re: [LAD] JACK latency API clarifications, Jörn Nettingsmeier, (Fri Feb 21, 7:34 pm)
Re: [LAD] JACK latency API clarifications, Lieven Moors, (Fri Feb 21, 8:28 pm)
Re: [LAD] JACK latency API clarifications, Fons Adriaensen, (Fri Feb 21, 8:01 pm)
Re: [LAD] JACK latency API clarifications, Stefano D'Angelo, (Fri Feb 21, 3:41 pm)