All,
I cant get the command line parameters to work on Pd-extended. (OSX)
Using the GUI 'startup' option doesn't work for me because I'm using 2 instances of PD spread over a 2 core machine ..... talking to each other via jackdmp.
I need to access the command line parameters so that I can configure the instances differently.
Is there a secret to get command line params to work with Pd-extended?
Etienne
e deleflie wrote:
All,
I cant get the command line parameters to work on Pd-extended. (OSX)
use Pd-0.42
afaik, cmdline args for all flavours of Pd on OSX prior to 0.42 and after 0.38 (or so) did not work, due to the way, things get called (on OS-X Pd will start the gui which in turn starts the dsp (which eats the cmdline args); prior to 0.42 the cmdline args got lost somewhere.
Is there a secret to get command line params to work with Pd-extended?
no secret involved. but since Pd-extended has not yet reached 0.42, it won't work out of the box yet.
fgamtr IOhannes
Hallo, IOhannes m zmoelnig hat gesagt: // IOhannes m zmoelnig wrote:
Is there a secret to get command line params to work with Pd-extended?
no secret involved. but since Pd-extended has not yet reached 0.42, it won't work out of the box yet.
A workaround I once used when being forced to use an older Pd on OS-X was the "startup flags" entry in the Startup preferences panel. You can input command line parameters there.
Ciao
Frank
e deleflie wrote:
I cant get the command line parameters to work on Pd-extended. (OSX)
use Pd-0.42
ok but will that loose all of the extended libs?
yes of course,...
... do I need to do something special to keep the extended libs?
well actually you can still use most libraries from Pd-extended. but things like [import] won't work anymore and you would have to put all libraries o be loaded into your "path" settings.
fgmasdr IOhannes
IOhannes m zmoelnig wrote:
e deleflie wrote:
All,
I cant get the command line parameters to work on Pd-extended. (OSX)
use Pd-0.42
afaik, cmdline args for all flavours of Pd on OSX prior to 0.42 and after 0.38 (or so) did not work, due to the way, things get called (on OS-X Pd will start the gui which in turn starts the dsp (which eats the cmdline args); prior to 0.42 the cmdline args got lost somewhere.
Is there a secret to get command line params to work with Pd-extended?
no secret involved. but since Pd-extended has not yet reached 0.42, it won't work out of the box yet.
I haven't got OSX here at the moment so I can't check, but IIRC it is a bit confusing which binary to use in the bundle, and if you use the appropriate one you can use command line args - for example this script works for Pd-0.40 extended on OSX 10.4
/Applications/Pd.app/Contents/Resources/bin/pd -nogui /Library/Pd/slave.pd; exit
Simon
Simon Wise wrote:
IOhannes m zmoelnig wrote:
e deleflie wrote:
All,
I cant get the command line parameters to work on Pd-extended. (OSX)
use Pd-0.42
afaik, cmdline args for all flavours of Pd on OSX prior to 0.42 and after 0.38 (or so) did not work, due to the way, things get called (on OS-X Pd will start the gui which in turn starts the dsp (which eats the cmdline args); prior to 0.42 the cmdline args got lost somewhere.
Is there a secret to get command line params to work with Pd-extended?
no secret involved. but since Pd-extended has not yet reached 0.42, it won't work out of the box yet.
I haven't got OSX here at the moment so I can't check, but IIRC it is a bit confusing which binary to use in the bundle, and if you use the appropriate one you can use command line args - for example this script works for Pd-0.40 extended on OSX 10.4
/Applications/Pd.app/Contents/Resources/bin/pd -nogui /Library/Pd/slave.pd; exit
ah, this only works if you use the "-nogui" flag. because: in this case, the pd-gui (which would _really_ start the pd-dsp) is not started, but instead the pd-dsp just keeps running and parses the rest of the arguments.
so: -nogui <otherargs> -help -version -invalidcmdlineargument should all work (because no GUI is involved, or Pd is quit before the gui could get involved)
as soon as GUI is involved, this simply does not work anymore.
its all for your benefit: people kept complaining about having a application-title "Wish" instead of "Pd" in the olde days. to fix this, it was necessary to add this who-calls-whom quirks, which lost the arguments in older (<0.42) Pd-versions.
fmga.sdr IOhannes
Have a look at this list email: http://lists.puredata.info/pipermail/pd-list/2008-10/065706.html and a follow-up: http://lists.puredata.info/pipermail/pd-list/2008-10/065709.html
- for ways of getting around the lack of command-line, and loading libraries
- in particular, a method for customising separate Pd instances for
different purposes.
I use this method successfully for working on customised versions of the IEM bin_ambi tool, also RjDj, alongside Pd-extended and vanilla, all on the same computer.
Nick
http://www.limsi.fr/Scientifique/ps/thmsonesp/SonEspace http://soundsorange.net
All,
I cant get the command line parameters to work on Pd-extended. (OSX)
Using the GUI 'startup' option doesn't work for me because I'm using 2 instances of PD spread over a 2 core machine ..... talking to each other via jackdmp.
I need to access the command line parameters so that I can configure the instances differently.
Is there a secret to get command line params to work with Pd-extended?
Etienne
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-
e deleflie -
Frank Barknecht -
IOhannes m zmoelnig -
Nicholas Mariette -
Simon Wise