> Once you have a low-latency kernel, check related > configuration in: > > /etc/security.d/limits.conf , or > > /etc/security/limits.d/audio.conf >
Oops, I meant: /etc/security/limits.conf , or /etc/security/limits.d/audio.conf Mine had at least: @audio - rtprio 70 @audio - memlock unlimited @audio - nice -10 it means your userid, which start jackd, needs to belong to the groupid called "audio". I think in Debian, the "/etc/security/limits.d/audio.conf" portion is done by the package manager when jackd2 is configured to use realtime priority. But you need to check the userid that starts up jackd belongs to the audio group. The command "groups" should list all the groupid's that the current user belongs to. This is the "low-latency" configuration portion of a pre-compiled low-latency kernel. You can check to see similar configuration done within the Musix liveCD environment. Again, once you understand all the numerous steps and things which need to be in placed, you can configure any Linux distro to do similar thing, but each distro may have done things slightly different. If any of those are out of placed, you may not get Linux MIDI to work, or may have numerous problems like no sound, latency (out of sync, long delayed note) issues, skipped notes... Jimmy ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Rosegarden-user mailing list Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
