I’m running two lovely apple 30" LCD’s on a pair of NVIDIA GFORCE 8xxx’s with the Nvidia driver (same problem with NV driver btw) and I get consistent xruns if the screen scrolls (in other words if I am zoomed all the way out I don’t get xruns.) Obviously this sort of works and mostly sucks. It also xruns if I move the mouse over any other windows or over buttons that flash when you mouse over them (basically if you make anything change on the screen.) I’ve dropped down to twm to rule out gnome/kde business. I’m sort of feeling like it’s something to do with scheduling but I’m pretty close to the limits of my knowlefe. In other words… I’m at my wits end! Any thoughts?
I managed to get keep it at 2 periods and even was able to drop the Frames/Period down to 128 and the latency to 32 and still record 4 live tacks while playing back 8 that already were recorded (plus a click!). I even got brazen and clicked over to firefox (which always caused xruns) and it just kept on cruisin with the DSP barely even working and plenty of room left.
So what did I do? Who knows… I’m an idiot. While I was waiting I decided to completely blow away jack and qjackctl and recompile them… somehow that did the trick… wtfk. anyway… I’m going to try dropping the bitdepth and latency as well just to see exactly how much I can crack out of this thing but at this point it’s just screaming. Thanks for the ‘help’.
“I’m also setting chrt -f -p (80 for jackd and 70 for ardour) once they start.”
do that. jackd has several RT threads that are setup automatically correctly if you start with the -R option and the priority. Same goes for ardour. It will run it’s RT thread at rt privs, and nothing else.
Several threads in both programs are intended to run at a lower priority than everything else. Don’t make it all run at RT privs.
I HAVE noticed some improvement sometimes by starting ardour with nice -10, which
bumps the gui up above other processes in the system, but keeps it below all the rt processes…
Glad you are cookin with oil. Am very jealous of those 30 inch monitors.
Thanks for the tips. I tried NOT doing that and you are right that everything works just fine. I think you must be right about what happened during the recompiles, though I’m not sure how I managed to screw that up. No complaints though. Sometimes just asking for help is enough of a sign of humility that the computer will let things start working.
I had the same thing on an early version on 64studio on an Asus board (also on NVidia graphics btw)
I finally bought a graphics card. The only relatively cheap PCIe card I could find was a GeForce 6600 and I seriously doubted getting that - nVidia as well!) but all went well!
No problems for me anymore.
I’m sort of feeling like it’s something to do with scheduling but I’m pretty close to the limits of my knowlefe. In other words… I’m at my wits end! Any thoughts?