On Wed, 2006-03-29 at 22:21 +0200, torbenh@xxxxxx wrote: > jackd produces xruns most of the time when the process graph is > reordered. which occurs on start stop of apps and port connection. > > ignore these xruns. they are not a problem. > Some of them are - a bug was just found in Ardour where stopping the transport can cause it to unlink() in the process callback causing an xrun. If it's a real xrun it will either show up in the regular latency tracer (/proc/latency_trace) or the user triggered atomicity debugger (described earlier in the thread). Lee
