sorry, if this was an issue before...
i'm not sure whether .pdrc in linux overrides flags specified in the command line or the other way round ?
are there any ways to define different pd-settings for different purposes?
another thing i discovered is, that the iemlib-sliders when used excessively (i.e. by sending a stream of numbers to it ) take a deadly amount of CPU. the speed of the stream of numbers has not been that dramatic (a metro with 200ms) but still my CPU went berserk. is there a way (i.e. by setting a specific flag) to reduce the gui-priority, like the "overdrive"-option in max/msp ?
btw: my system is debian 2.4.16, pd-0.34-4
thanx for any clue
oliver
On 1/16/02 11:52 AM, oliver stotz @ oliver@klingt.org wrote:
sorry, if this was an issue before...
i'm not sure whether .pdrc in linux overrides flags specified in the command line or the other way round ?
command line overrides the .pdrc file.
are there any ways to define different pd-settings for different purposes?
You could create executable shell scripts that call pd with different command line switches. And optionally have a .pdrc for settings that are common to all versions. Otherwise you can do without .pdrc
another thing i discovered is, that the iemlib-sliders when used excessively (i.e. by sending a stream of numbers to it ) take a deadly amount of CPU. the speed of the stream of numbers has not been that dramatic (a metro with 200ms) but still my CPU went berserk. is there a way (i.e. by setting a specific flag) to reduce the gui-priority, like the "overdrive"-option in max/msp ?
It is a known issue that the gui eats up CPU cycles (esp. redrawing). I avoid using complex gui items for monitoring purposes and i get rid of "animated" items altogether when I don't need to look at them anymore. Or hide them in subpatches which you can close and not worry about screen redrawing when performance is at stake.
./MiS
Looking at the source code, I gather that the ".pdrc" actually overrides command line! This is wrong... I'll fix for 0.35...
cheers Miller
On Wed, Jan 16, 2002 at 05:52:15PM +0100, oliver stotz wrote:
sorry, if this was an issue before...
i'm not sure whether .pdrc in linux overrides flags specified in the command line or the other way round ?
are there any ways to define different pd-settings for different purposes?
another thing i discovered is, that the iemlib-sliders when used excessively (i.e. by sending a stream of numbers to it ) take a deadly amount of CPU. the speed of the stream of numbers has not been that dramatic (a metro with 200ms) but still my CPU went berserk. is there a way (i.e. by setting a specific flag) to reduce the gui-priority, like the "overdrive"-option in max/msp ?
btw: my system is debian 2.4.16, pd-0.34-4
thanx for any clue
oliver
hi Miller,
this issue recurs quite often on pd-list. And, while you are changing
the way of .pdrc parsing, could you look at my .pdrc & pd-034'' post from Mon, 01 Oct 2001, and also my.pdrc trouble (0.34-3 & 4)'' post
(and your reply to it) from Tue, 27 Nov 2001? Command line overriding
was mentioned there, and also some other points...
Krzysztof
Miller Puckette wrote:
Looking at the source code, I gather that the ".pdrc" actually overrides command line! This is wrong... I'll fix for 0.35...
hi, in my starting scripts (which i prefer to the .pdrc-file) I get a very long Wurst (as we say in austria - a very long line) of flags, because i think the flags have to be in one line... is this true? and if i have more then one path-flag, can i combine them in one command? also, there once was the problem of comments in the .pdrc file, is there already a solution, this also would make things easier? marius
Am Donnerstag, 17. Januar 2002 12:06 schrieb Krzysztof Czaja:
hi Miller,
this issue recurs quite often on pd-list. And, while you are changing the way of .pdrc parsing, could you look at my
.pdrc & pd-034'' post from Mon, 01 Oct 2001, and also my.pdrc trouble (0.34-3 & 4)'' post (and your reply to it) from Tue, 27 Nov 2001? Command line overriding was mentioned there, and also some other points...Krzysztof
Miller Puckette wrote:
Looking at the source code, I gather that the ".pdrc" actually overrides command line! This is wrong... I'll fix for 0.35...
|in my starting scripts (which i prefer to the .pdrc-file) I get a very long |Wurst (as we say in austria - a very long line) of flags, because i think the |flags have to be in one line... is this true? and if i have more then one |path-flag, can i combine them in one command?
you can use a \ which tells the shell that the cmd is continued on the next line (wurstslicing operator ) like:
#!/bin/sh
pd
-lib Gem
-lib zexy
-etc etc
$@
with path dont know but just try
-path /path/eins:/path/zwei:/etc/usw
|also, there once was the problem of comments in the .pdrc file, is there
|already a solution, this also would make things easier?
|marius
|
|Am Donnerstag, 17. Januar 2002 12:06 schrieb Krzysztof Czaja:
|> hi Miller,
|>
|> this issue recurs quite often on pd-list. And, while you are changing
|> the way of .pdrc parsing, could you look at my .pdrc & pd-034'' post |> from Mon, 01 Oct 2001, and also my.pdrc trouble (0.34-3 & 4)'' post
|> (and your reply to it) from Tue, 27 Nov 2001? Command line overriding
|> was mentioned there, and also some other points...
|>
|> Krzysztof
|>
|> Miller Puckette wrote:
|> > Looking at the source code, I gather that the ".pdrc" actually overrides
|> > command line! This is wrong... I'll fix for 0.35...
|
-- X Ð ¥ · 0 r G
-
_-¯-_ -
Krzysztof Czaja -
marius schebella -
Michal Seta -
Miller Puckette -
oliver stotz