i aldo ran into this problem, and found out a weird thing:
if any midi-stuff is defined in the start-up script (i.e. -midiindev etc.), setting HIGH priority using the "start" command doesn't work! really haven't got a clue why. so there's several possibilities:
1.) deactivate MIDI in your start-up script if you don't need it. 2.) if you do need MIDI, start a second PD and route your midi stuff to your NON-MIDI PD using OSC or netsend/netreceive 3.) there's a nice little freeware command-line utility called "process". you can download it here: http://www.beyondlogic.org/solutions/processutil/processutil.htm
this allows to set priorities with the command line. it's just an .exe file that you put where your machine finds it. then you also need the "motex" library for the [system] object. give it a message called [process -p PD.EXE High(
you can then automate this thing with loadbang (and maybe a slight delay
- like 1 second...)
i know this is quirky, but at least it works and functions automatically.
good luck
oliver
Josh Steiner wrote:
interesting, i've occastionally set the priority higher in the taskmanager which seems to help avoiding stutters when moving objects around and such, but when i try your command like alone, it works: pd is running at high priority, but if i stick "cmd /c start /High " in front of my big line in the .bat with all the -lib's and -path's and -audiodev's and such, it starts as normal priority... any ideas?
hi, if you're talking WinXP:
i have an audio problem, that results in "scratchy sound" now and then, as long as PD is not at least in HIGH priority mode.
i think by default it is in NORMAL mode and by setting it automatically to HIGH (by batch command "cmd /c start /High D:\pd\bin\pd.exe") i removed the problem. it is important though that "wish32.exe" (the GUI) stays in NORMAL priority
just my 2c
ciao
oliver