22 Jan
2003
22 Jan
'03
2:59 p.m.
Thanks Fernando. I hadn't seen that, and it makes me feel better to know
it's just a standard design problem.
I'll still put Jack in the console, I think, to keep it off my desktop, and
just look there occasionally to see how things have been going.
Actually, can I somehow take the jackstart output that goes to the F2
console and pipe it to a file that I could look at from KDE? That would be
nice too.
-----Original Message-----
From: Fernando Pablo Lopez-Lezcano [mailto:nando@ccrma.Stanford.EDU]
Sent: Wednesday, January 22, 2003 10:38 AM
To: Mark Knecht
Cc: Robert Jonsson; jackit-devel(a)lists.sourceforge.net; Linux-audio-dev
Subject: RE: [Jackit-devel] Re: k_jack v0.0.0.5
I have noticed that there are still a number
of system
oriented things
that, on my system, absolutely guarantee an xrun.
The simplest
is dropping
down to a console. (Alt-Ctl-F2)
It is a known problem and is in the list of "things you should not do"
in Andrew Morton's low latency page (at the bottom):
http://www.zip.com.au/~akpm/linux/schedlat.html
-- Fernando