Hi All, I'm having a problem using Ardour and Jackd with realtime capabilities. The jack package tells you right after installation the following:
--> NOTE: Running jack as root to enable realtime capabilities isn't --> needed any longer. As of kernel-2.6.12 and pam > 0.80-2 you can --> achieve the rights to run real-time on a per group basis, which is --> controlled by /etc/security/limits.conf I diligently edited limits.conf to have amongst others the following: * - rtprio 0 * - nice 0 @audio - rtprio 65 @audio - nice -10 @audio - memlock 40000 After that, I made sure my users are added to the audio group. I fired up qjackctl which fires up jack without any errors like this: /usr/bin/jackd -R -P55 -dalsa -dhw:0 -r48000 -p64 -n2 -S And sure enough, I can run all kinds of jack apps without problems, for example fst 1.7 works great, creates all audio and midi connections automatically, etc. But when I start ardour, I get the following errors: (GUI) [ERROR]: cannot activate JACK client <click on OK button> (TERMINAL) jack_client_create_thread: error 11 creating realtime thread: Resource temporarily unavailable. Now, I'm 100% positive that all executables involved have no suid-root, I'm running everything as the same user, so I think it should work, right? Is this a bug in ardour? Has something changed in jack? At #ardour (freenode) people told me I need the realtime-lsm. I know that the realtime lsm is needed, but to my amazement, the Arch jack package allows me to run jack with realtime at prio 65 using the standard capabilities stuff as per /usr/security/limits.conf! Is ardour maybe not compatible with this? Anyway, as shipped, you cannot run jackd -R + ardour in Arch. due to the aforementioned error. I hope someone could shed some light on this. Kind regards, Rubin. _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
