On Mon, 2004-10-04 at 15:29, Florian Schmidt wrote: > On Sun, 03 Oct 2004 12:55:18 +0300 > Sampo Savolainen <v2@xxxxxx> wrote: > > Actually, that's not entirely correct. I've been talking to Paul about > > this. The xruns created by exiting clients is due to jackd having to > > rework it's internals. When doing this reordering, jackd has to lock > > the data it's modifying and sometimes (very often) there will be an > > xrun because the audio thread is waiting for the lock to be released. > > > > Ah, and btw: Shouldn't the audio thread just try the lock and if it > fails to claim it produce a period of silence? What spot in the code is > this? I don't know jacks internals myself. What I posted the other day was simply something that I gathered from discussing the issue of xruns when clients disconnected. The jack development people will know more about this issue. Sampo
