Hello Jonathan,
To get jack running properly you need: - Planet CCRMA packages (http://ccrma.stanford.edu/planetccrma/software/) which are not available for F9 - low latency kernel, Planet CCRMA also provides these, unfortunately not for F9 - zero latency soundcard, an onboard card probably never works without an xrun every now and then
An xrun is indeed a buffer under/overrun and could be caused by numerous things, always hard to put a finger on it. Could be software, hardware. Best is to run jack with a light weight WM like fluxbox or IceWM and to use as little other programs as possible. And to switch to another version of Fedora (like 7 or 8) for which there are Planet CCRMA packages available, otherwise it's no use I think.
Good luck!
Jeremy
Paulo Cavalcanti wrote:
On Wed, Nov 19, 2008 at 1:28 AM, Jonathan Ryshpan <jonrysh@pacbell.net mailto:jonrysh@pacbell.net> wrote:
In the past I've never had any problems running jackd. Now I'm getting a very large number of messages reading: **** alsa_pcm: xrun of at least 1227061150613.504 msecs I'm running F9 on an x86_64 system with all updates installed. Pulseaudio is not running. Jackd is started via qjackctl. No past problems with audio beyond the usual conflicts between pulseaudio and firefox. Questions: (1) What exactly does this message mean? An "xrun" is a buffer under- or over-run -- but what does the time interval represent? (2) Whatever the time interval means, it looks rather large. 1227061150613.504 msec is many days (or maybe years if msec means millisec and not microsec) This looks like a misconfiguration of some kind or a missing component. Any idea what it might be?The solution depends on your card (I have an Intel onboard card). But this material may give you an idea on what you can try:
http://people.atrpms.net/~pcavalcanti/alsa-1.0.15rc2_snd-hda-intel.html#jack
-- Paulo Roma Cavalcanti LCG - UFRJ