I got the same errors using the 2.6.32 (or maybe it was .33) kernel, does that matter?

On Mon, Jan 31, 2011 at 4:38 PM, linuxdsp <mike(a)linuxdsp.co.uk> wrote: > Gabbe Nord wrote: > >> Hello guys! >> >> I'm trying out the pianoteq-trail, which is awesome! But I get pretty bad >> performance, and when I start the app I get this error-msg: >> >> Midi thread could not acquire real-time scheduling, error 1 -- Operation >> not permitted >> Midi thread could not acquire real-time scheduling, error 1 -- Operation >> not permitted >> Midi thread could not acquire real-time scheduling, error 1 -- Operation >> not permitted >> Jack error: Cannot use real-time scheduling (RR/5)(1: Operation not >> permitted) >> Jack error: AcquireRealTime error >> Multi-core: could not acquire real-time scheduling, error 1 -- Operation >> not permitted >> >> Do you guys have any idea what the problem might be? Googling it has given >> me nothing so far! I have both my username and the groupname "audio" setup >> properly in limits.conf (rtprio, nice and so on) via a tutorial I found a >> while back. I'm using ubuntu studio 10.04 but with the latest >> 2.6.38-1-generic kernel. >> >> Best regards! >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Linux-audio-user mailing list >> Linux-audio-user(a)lists.linuxaudio.org >> http://lists.linuxaudio.org/listinfo/linux-audio-user >> > > Perhaps it has something to do with this: > > http://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg2710524.html > > >

_______________________________________________ Linux-audio-user mailing list Linux-audio-user(a)lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-user

On 02/01/2011 01:02 AM, torbenh wrote: Hello Torben, I've searched for more info about this but I couldn't find anywhere that 100 might be an invalid setting. Do you have more info on this, a link maybe? Best, Jeremy

Priority 100 is the absolute max on Linux. When you use that, nothing else will stop jack in case of errors. And nothing else has a chance to run, not even interrupts handlers for hardware. Using priorities above 80 seems save, above 90 there is a good chance that your jack-threads take up your cpu and nothing has enough priority to stop them... Don't test what happens while all is well, test what happens when you have a high dsp-load and then a cpu-hogging client.

On Tuesday 01 February 2011 08:43:38 Jeremy Jongepier wrote: Priority 100 is the absolute max on Linux. When you use that, nothing else will stop jack in case of errors. And nothing else has a chance to run, not even interrupts handlers for hardware.

_______________________________________________ Linux-audio-user mailing list Linux-audio-user(a)lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-user