~] approach; DIO
error crackles.
Any advice very welcome!
Have you had clicks before? In my experience running Linux, I have had much
fewer dio errors (basically none) running pd -rt on a *non* realtime kernel. I
use the basic Ubuntu kernel with realtime privileges enabled, no running pd as
root
as with my regular abstraction / [switch~] approach; DIO
error crackles.
Any advice very welcome!
Have you had clicks before? In my experience running Linux, I have had
much fewer dio errors (basically none) running pd -rt on a *non* realtime
kernel. I use the basic Ubuntu kernel with realtime
errors when I load my abstraction in a pd~ object and don't
switch~ it on, whereas when loading it as a regular abstraction, switch~-ing
it off stops the DIO errors.
Thanks,
Tim
pat
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account
Hi all,
I have a rather heavy patch which causes DIO errors when I switch~ on
several subpatches.
I'm running pd + Jack on a rt kernel (ubuntu-studio Hardy),... Jack shows
little or no Xruns.
Now I wanted to try and optimize the patch by using [pd~].
The way I understood it is that [pd~] will
hi tim,
just to be sure, do you use the -rt flag when starting pd? also, try to
run everything (jack, pd) in root (just to see if the glitches is the
cause of a limitation).
pat
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -
