On Mon, Mar 19, 2012 at 10:20 AM, Fons Adriaensen <[email protected]> wrote:
> What would be an interesting addition to Jack would be the possibility > to reduce the timing uncertainty for certain clients. At the moment > a client can run anywhere between the start of a cycle and the start > of the next one - no assumptions can be made. If a2j would always > run near the start of a cycle, and j2a never before e.g. 90% of the > cycle has passed, that would enable to reduce the minimum required > latency. re: the j2a part ... given that the server may be otherwise done with the period after less than 5% of the period time has elapsed, this seems hard to guarantee and counter-productive (it would require a double wakeup of the server). _______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/listinfo/linux-audio-dev
