guenter geiger writes:
On Mon, 19 Jan 2004, Frank Barknecht wrote:
Hallo, guenter geiger hat gesagt: // guenter geiger wrote:
On Mon, 19 Jan 2004, Miller Puckette wrote:
well, now it's pd and jack ... in the future, there's no telling how crowded the space of "real-time" hungry processes will get. So maybe it's worth finding a general way to determine which level Pd should live at. Perhaps it should be just below the one jack chooses (and does anyone know that one?)
seems to be 10 for the server and 9 for the client. (from jackd/jackd.c:static int realtime_priority = 10;)
Since jack triggers a callback it should be higher priority (which is as a realtime priority in the new kernel 2.6.0 a lower number 1..99 for realtime which is mapped to 20-N, effective 140-N on 2.6.0 with the priority library call, to talk about he same numbers).
But also I saw clients priority number: res->realtime_priority = engine->rtpriority - 1; in engine.c of jackd
which means jack itself makes a client call (callback) one less than jack, so pd should be at least 2 less than jack, so that the callback always has priority to pd.
mfg winfried