IOhannes m zmölnig wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06/11/2010 01:49 AM, Kim Cascone wrote:
i thought this is what you were asking for with "is there a way on the
command line to load only certain libs?"
yes, but I'm trying to understand your statement: 'the panel merely
being a wrapper around the -path flag'
ah in understand.
i was referring to the path-entry box, and not to the "apply/save"
buttons in the panels.
OK so I grok that the panel is just a gui for the command line
and that if you do not hit the Apply button all the paths are also 'per
session'
I guess I've been hitting the Apply button automatically and never
checked what happens if I didn't hit Apply
in Max/MSP you can simply enter a path into the 'file prefs' panel and
it will be there after relaunching - so this is the behavior I expected
to see only because I've used Max/MSP for 10+ years
both the cmd-line flags and the .pdsettings are a way to configure your
Pd sessions; none of them are a way to script Pd (which it seems is what
you were expecting:
actually, it seems that the .pdsettings are loaded on start up -- no?
so wouldn't that make them a sort of script too - in a sense?
i.e. changes made to this file are 'persistent' across program startups
so long as the .pdsettings file is unchanged
being able to script Pd from the cmdline to store
it's preferences to a file) [1]
yes, I was only interested in creating a workflow that would make
testing plugin~ smoother
no big deal about not being able to set -flags persistently
unless I'm not understanding something
making these changes from the panel in Pd these settings are persistent
making them from the command line they are not
the question is, why would you want to make the settings persistens from
the console?
and how is this .pdsettings more persistent than cmdline flags or a
shell-scripts.
.pdsettings gets loaded on startup - no?
so, if I make changes directly to this file in gedit won't those changes
be loaded as well?
sorry, I'm just trying to understand all this better :)
is there a way to make this persistent from the console?
use a shell-script.
a shell script would only work on a per session basis as well - no?
all settings are "per session";
whenever you run the shell-script with the same-flags, you will have the
same behaviour of Pd.
.pdsettings are just a more user friendly way to provide Pd-settings
(for users that are afraid of the cli; e.g. i regularily delete my
.pdsettings, because i don't need it and it only interferes with what
i'm doing)
anyhow, since Pd is cool and despite of what i said above, it even
allows you to save your preferences with shell-flags.
[1] pd -lib blu -send "pd save-preferences ;"
ah ha! the truth comes out! ;)
so in trying to understand the flags above
-lib loads the 'blu' library
and -send sends PdX a message to save-preferences?
is this prefs stored as the .pdsettings file?
thanks again for your PdX lessons - they help me understand the
difference between Max and Pd :)
==================================
also, I found some other bugs/issues in [plugin~]
see attached file for info
===================================
one thing not included in the file is a difference between
what analyseplugins <foo> returns in the term
versus what [info] returns from [plugin~] in the console
here is an example for the 'delayorama' LADSPA plug:
sudo analyseplugin delayorama_1402.so
"Random seed" input, control, 0 to 1000, default 0, integer
"Input gain (dB)" input, control, -96 to 24, default 0
"Feedback (%)" input, control, 0 to 100, default 0
"Number of taps" input, control, 2 to 128, default 2, integer
"First delay (s)" input, control, 0 to 5, default 0
"Delay range (s)" input, control, 0.0001 to 6, default 6
"Delay change" input, control, 0.2 to 5, default 1
"Delay random (%)" input, control, 0 to 100, default 0
"Amplitude change" input, control, 0.2 to 5, default 1
"Amplitude random (%)" input, control, 0 to 100, default 0
"Dry/wet mix" input, control, 0 to 1, default 1
"Input" input, audio
"Output" output, audio
=======================================
versus the PdX console sent when sending [info] to plugin~
=======================================
verbose( 1):plugin~: constructed plugin "Delayorama" successfully
verbose( 1):plugin~: plugin ports: audio 1/1 ctrl 11/0
verbose( 1):plugin~: plugin active
plugin~: "Delayorama"
print: port in control Random seed 0 1000
error: [print]: close-paren without open-paren
error: [print]: close-paren without open-paren
print: port in control Number of taps 2 128
error: [print]: close-paren without open-paren
error: [print]: close-paren without open-paren
print: port in control Delay change 0.2 5
error: [print]: close-paren without open-paren
print: port in control Amplitude change 0.2 5
error: [print]: close-paren without open-paren
print: port in control Dry/wet mix 0 1
print: port in audio Input 0 1
print: port out audio Output 0 1
#N canvas 214 100 915 589 10;
#X floatatom 285 80 0 0 0 0 - - -;
#X obj 310 19 loadbang;
#X msg 284 109 control freq \$1;
#X msg 388 109 control amp \$1;
#X msg 388 52 0.7;
#X floatatom 388 83 0 0 0 0 - - -;
#X obj 318 187 plugin~ sine_fcac;
#X obj 416 255 tabwrite~ array1;
#X msg 461 206 1;
#X obj 461 184 loadbang;
#X msg 28 153 info;
#X obj 318 210 print;
#N canvas 0 22 450 300 (subpatch) 0;
#X array array1 100 float 0;
#X coords 0 1 100 -1 200 140 1;
#X restore 538 30 graph;
#X obj 282 686 metro 500;
#X msg 281 664 1;
#X obj 281 642 loadbang;
#X msg 451 515 bindscaled help2;
#X msg 153 516 bind help1;
#X obj 153 476 hsl 128 15 0 8000 0 0 help1-Cutoff empty cutoff_frequency
-2 -8 0 10 -262144 -1 -1 0 1;
#X obj 367 692 tabwrite~ array2;
#N canvas 0 22 450 300 (subpatch) 0;
#X array array2 100 float 0;
#X coords 0 1 100 -1 200 140 1;
#X restore 542 578 graph;
#X obj 453 477 hsl 128 15 0 127 0 0 help2-Cutoff empty cutoff_frequency
-2 -8 0 10 -262144 -1 -1 0 1;
#X obj 368 582 phasor~ 440;
#X text 449 497 or click me;
#X text 155 497 click me;
#X text 246 433 sends values as help1-Cutoff;
#X text 263 454 v;
#X text 263 445 |;
#X text 559 458 v;
#X text 559 449 |;
#X text 542 437 sends values as help2-Cutoff;
#X text 471 374 bindscaled is like bind \, but it translates numbers
from the range 0-127 to the input range defined by the plugin. This
is useful for MIDI controllers.;
#X msg 209 598 unbind;
#X text 91 372 You can use the bind message to bind plugin parameters
to message names automatically.;
#X msg 589 527 bindscaled help2 0 1;
#X text 588 507 You can also override the input range;
#X obj 104 438 loadbang;
#X msg 793 91 \; pd dsp \$1;
#X obj 793 58 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 1
1;
#X msg 285 50 1000;
#X msg 20 87 control #1 \$1;
#X msg 119 95 control #2 \$1;
#X obj 23 38 hsl 128 15 0.5 10000 0 0 empty empty freq -2 -8 0 10 -204800
-1 -1 1400 1;
#X obj 122 73 hsl 128 15 0 1 0 0 empty empty amp -2 -8 0 10 -191407
-1 -1 7900 1;
#X floatatom 31 61 7 0 0 0 - - -;
#X msg 413 139 listplugins;
#X msg 209 622 info;
#X obj 304 607 plugin~ lpf;
#X text 23 188 print: port in control Frequency 0 0.5;
#X text 23 202 print: port in control Amplitude 0 1;
#X text 21 217 control for Frequency can be sent as either;
#X text 23 234 #1 or freq;
#X text 23 251 control for Amplitude can be sent as either;
#X text 25 268 #2 or amp;
#X obj 461 229 metro 500;
#X text 244 313 ------------------------------------------------------------
;
#X obj 250 331 cnv 15 300 23 empty empty empty 20 12 0 14 -258113 -66577
0;
#X text 257 322;
#X text 23 174 [info] will print the info below in the console;
#X text 13 291 *** is using 'freq' or '#1' instead of Frequency clear
or logical to anyone? ***;
#X text 250 333 [bind] & [bindscaled] do NOT seem to be working;
#X connect 0 0 2 0;
#X connect 1 0 39 0;
#X connect 1 0 4 0;
#X connect 2 0 6 0;
#X connect 3 0 6 0;
#X connect 4 0 5 0;
#X connect 5 0 3 0;
#X connect 6 0 11 0;
#X connect 6 1 7 0;
#X connect 8 0 54 0;
#X connect 9 0 8 0;
#X connect 10 0 6 0;
#X connect 13 0 19 0;
#X connect 14 0 13 0;
#X connect 15 0 14 0;
#X connect 16 0 47 0;
#X connect 17 0 47 0;
#X connect 22 0 47 1;
#X connect 32 0 47 0;
#X connect 34 0 47 0;
#X connect 36 0 17 0;
#X connect 38 0 37 0;
#X connect 39 0 0 0;
#X connect 40 0 6 0;
#X connect 41 0 6 0;
#X connect 42 0 40 0;
#X connect 42 0 44 0;
#X connect 43 0 41 0;
#X connect 45 0 6 0;
#X connect 46 0 47 0;
#X connect 47 1 19 0;
#X connect 54 0 7 0;
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
