[PlanetCCRMA] help debug realtime priority-induced bug in Kmid 2.3.0

Niels Mayer nielsmayer at gmail.com
Wed Jun 2 10:00:43 PDT 2010

I don't have time to do these verifications in a timely fashion,
wondering if others want to help do some sleuthing w/r/t realtime prio
issues that cause a bug in kmid2 -- only the very first time you run
it, before it writes its own config file: ~/.kde4/share/config/kmidrc
... ( https://admin.fedoraproject.org/updates/drumstick-0.3.1-2.fc12,kmid2-2.3.0-1.fc12
<-- this is a great utility on your system, so you can click a MIDI
file and hear it right away with no setup, all with a nice GUI).

I've found just another condition: user realtime priority is activated, for
instance when your /etc/security/limits.conf file has a "rtprio" item for the
user or a group where your user belongs. Without realtime priority the crash
rarely happens, if ever. Can you please confirm this?

I'm running a standard kernel ( ) and my
/etc/security/limits.conf settings are

@jackuser - rtprio 99
@jackuser - memlock 4194304
@jackuser - nice -10

gnulem-103-~/Documents> grep jackuser /etc/group


PS: is there a way to setup realtime priority on a per-process basis
rather than per-user basis? What we really want is for just a few
programs (jackd, and DAW/plugins)
to have realtime priority, but it certainly doesn't mean that a
program like 'kmid' needs realtime priority (although if it's hosting
fluidsynth, it probably does, right?)...
That way I could properly test this without losing all realtime
priority for audio/video that seems to be working well enough at the

More information about the PlanetCCRMA mailing list