Re: [Jack-Devel] issues with latency management with "complex" clients

Paul,

> So the question is: should anything be done about this? Should ardour
> force a recompute of the latencies when a track changes modes? This is
> quite expensive and definitely non-RT in jack1; its doable with
> tschak. jack2 does not have an implementation of this latency API yet.
> Could we just redefine the latency specifications into something that
> is still useful, but avoids this issue? Or something else?

The question is: Does jack want to stay confined to a single system? If
not, I'd propose using timestamps on incoming samples and defininition
of a system latency. This not only allows to specify exactly when data
is to be played out (sample synchronicity across all clients, even with
different path lengths), it also would allow jack to keep in touch with
upcoming audio standards.


Flo
-- 
Machines can do the work, so people have time to think.
public key B3B9226C          x-hkp://wwwkeys.eu.pgp.net

1298364309.12688_0.ltw:2,a <4D637783.8080002 at faberman dot de>