Right now I am listening to mp3 through Juk. Arts is running setup to interface with jack. It works almost completely. The buffer is:
Realtime scheduling is on (emerge realtime-lsm), according to lsmod and that jack wouldn't start with the -R option if I rmmod the realtime module.configuring for 48000Hz, period = 1024 frames, buffer = 3 periods
Any time the hard disk is accessed too much the sound is interrupted.
I don't know if I get the maths right but if I say (1024 * 3 / 48000) = 64 ms.
That's a rather large latency, given the purpose of jack... Still it interrupts now and then.
qjackconnect says the CPU load is around 1.00. I guess that means 1%. I watched it go up to around 51.00 before, so it oughtta be percents.
such a low load sounds nice, but still it doesn't work very well.
I am trying to find a kernel and jackd setup that works in all cases. It is not an easy task.
I was on gentoo-sources (2.6) up until tonight when I read this from the kernel guide:
ck-sources and gentoo-sources are not equal, but I read sometime about a year ago that gentoo-sources had very similar, if not equal scheduling patches.ck-sources is Con Kolivas's kernel patch set. This kernel is HIGHLY tuned for desktop performance at the expense of throughput and some of the scheduler's ability to prioritize applications.
So tonight I went for the vanilla 2.6 kernel, to get rid of the desktop scheduling patches.
Now everything is a lot better, but sporadic disk accesses still cause big interrupts in the music.
Questions:
How should a linux PC be setup to get the most out of jack with a 2.6-kernel?
Is there any kernel patch out there that deals with this issue alone?

