On Wed, July 11, 2007 03:27, Eliot Blennerhassett wrote: A: jackd reports any kind of actual and potential overrun to its clients through a callback mechanism. The above messages accounts for the number of times the xrun callback function was issued from jackd to qjackctl, which is obviously monitoring it. There's two kinds of messages: ... XRUN callback (N) - this one reports the N-th occurence of a xrun callback since last reset. ... XRUN callback (N skipped) - this one reports that N xrun callbacks have been issued since the last time a XRUN callback message was displayed. As said, these reports are issued by jackd and sure represent some kind of problem, most of the cases are scheduling delays and jitter will be due soon. Either the jackd parameters are too tight for correct and smooth operation or you have a problematic system scenario. This message occurs when the XRUN is detected at the ALSA backend, and sure you will have lost audio data, so glitches will be certainly heard. Oh well, so you're messing with a custom .asoundrc ? There's your systemic problem. You'll need help from someone else which is more knowledgeable about your specific setup: two soundcards? are they identical? how are they synched? word-clock? yada, yada... HTH Cheers. -- rncbc aka Rui Nuno Capela rncbc(a)rncbc.org