Selon Thomas Grill gr@grrrr.org:
Some others don't work, like fftease and vasp (wtachdog).
Hi Julien, i would be interested under which circumstances these don't work. Do you have an example patch etc.?
It's only about the loading, and actually I was wrong, as it's only a problem of launching time -- just see this commentated "screenshot" :
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| [root@localhost j]# pd -jack -rt -lib vasp priority 2 scheduling enabled. memory locking enabled. priority 4 scheduling enabled. memory locking enabled. <------ here the whole linux system becomes very slow watchdog: signaling pd... watchdog: signaling pd... watchdog: signaling pd... <------ here the Pd windows begins to draw slowly watchdog: signaling pd... watchdog: signaling pd... watchdog: signaling pd... <------ here everything become normal again ; Pd seems to work normally
VASP modular 0.1.2
vector assembling signal processor (C)2002-2003 Thomas Grill
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
I got the same situation with fftease. I first thought they didn't work because of the watchdog messages, but actually you just have to wait and the normal situation gets back after, say 10 seconds.
I use the PlanetCCRMA/RH9.0 distribution of Linux (with the PlanetCCRMA low-latency kernel), the sound card is a RME Hammerfall Multiface.
I hope this will help. If you need some more information, please ask me
Sorry but I didn't have the time to test your objects inside patches, if there's a later problem in use I will tell you.
-j