hi i just starting to use pd, on a osx machine.
real time in osx?
amos.
Not if you make the pd executable setuid root. To do so, run this (assuming your pd is installed in /usr/local/bin/pd):
sudo chown root /usr/local/bin/pd sudo chmod u+s /usr/local/bin/pd
Then pd will always run as root regardless of who started it. This is a modest security risk though, setting any app setuid root is.
.hc
On Monday, Sep 15, 2003, at 07:25 America/New_York, Amos Elmaliah wrote:
hi i just starting to use pd, on a osx machine.
- i compiled it myself. my question: is it necessary to sudo pd to get
real time in osx?
amos.
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
On Monday, September 15, 2003, at 07:25 AM, Amos Elmaliah wrote:
hi i just starting to use pd, on a osx machine.
- i compiled it myself. my question: is it necessary to sudo pd to get
real time in osx?
...well, I guess you've already seen the other posts, and I just wanted to come down on the side of "realtime isn't very helpful on OSX"...which brings up a question or two that I had posted, oh, last week, but which were quietly unanswered:
seem to notice it otherwise...and lately it doesn't print anything but a carriage return: is this correct?
...also, I would strongly recommend removing the schedule priority setting stuff, especially if using GEM, because it allows pd to take over the machine, thus necessitating a reboot! This may be sparked by the extremely inefficient implementation of TCL/TK on OSX, as it seems to happen when changing parameters "on the fly" via number boxes or the like...again to repeat a previous post:
"searching through the code, I found that the param.sched_priority "fix" has worked it's way into s_inter.c:833:848...if I remember correctly, this was a "fix" for audio glitches? The problem with using it and GEM is that it makes pd a higher priority than the window manager, and so it's very easy to get locked out, forcing a manual reboot! If audio people really need this (I thought the audio glitch was fixed elsewhere, too?), could we make a compile flag to disable this? Also would be a good idea to notify people who are using this current version and GEM to be ready for a lock out and sadness..."
good luck, jamie