-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/11/2010 10:36 AM, Kim Cascone wrote:
> > plugin~: "Delayorama" > print: port in control Random seed 0 1000 >
looks good, doesn't it?
er, sure if it matched the console report (when plugin~ is sent [info]) it would look even better! ;)
it reports all "relevant" information.
ahhhhh...I now see why you say that it reports 'all relevant info' given the console info you posted below
because I've been (unknowlingly) using the GridFlow [print] and I'm missing this info
[see attached patch]
I tested this with both [pd/print] and [print] and here are the results:
using the [print] object [info] reports to console: a: port in control Random seed 0 1000 error: [print a]: close-paren without open-paren error: [print a]: close-paren without open-paren a: port in control Number of taps 2 128 error: [print a]: close-paren without open-paren error: [print a]: close-paren without open-paren a: port in control Delay change 0.2 5 error: [print a]: close-paren without open-paren a: port in control Amplitude change 0.2 5 error: [print a]: close-paren without open-paren a: port in control Dry/wet mix 0 1 a: port in audio Input 0 1 a: port out audio Output 0 1
using the [pd/print] object [info] reports to console: b: port in control Random seed 0 1000 b: port in control Input gain (dB) -96 24 b: port in control Feedback (%) 0 100 b: port in control Number of taps 2 128 b: port in control First delay (s) 0 5 b: port in control Delay range (s) 0.0001 6 b: port in control Delay change 0.2 5 b: port in control Delay random (%) 0 100 b: port in control Amplitude change 0.2 5 b: port in control Amplitude random (%) 0 100 b: port in control Dry/wet mix 0 1 b: port in audio Input 0 1 b: port out audio Output 0 1
this is really confusing for people using [print] not knowing they are using the GridFlow external instead of the standard Pd version
how do we disentangle this and make it obvious? and why isn't there a GridFlow [print] external called [gf_print] instead?
is this a bug or known issue?
> error: [print]: close-paren without open-paren >
oops; seems there is a problem with displaying symbols with parenthesis.
I'm assuming here that not all LADSPA plugs send info with parentheses? so this would be a problem only for those plugs that send data with parentheses
correct. anyhow, when i try your plugin i get:
<snip> plugin~: "Delayorama" a: port in control Random seed 0 1000 a: port in control Input gain (dB) -96 24 a: port in control Feedback (%) 0 100 a: port in control Number of taps 2 128 a: port in control First delay (s) 0 5 a: port in control Delay range (s) 0.0001 6 a: port in control Delay change 0.2 5 a: port in control Delay random (%) 0 100 a: port in control Amplitude change 0.2 5 a: port in control Amplitude random (%) 0 100 a: port in control Dry/wet mix 0 1 a: port in audio Input 0 1 a: port out audio Output 0 1 </snip>
looks good to me.
yes and this matches the analyseplugin <foo> data
??
i don't seem to have this problem here (though i don't have the delayorama plugin;
I've attached it - see if this works for you?
and the "invada_mono_tube_module_0_1" works just fine (with pd-vanilla 0.42.6)
***do you have any info on how params are listed in [info]->[plugin~] versus [analyseplugin <foo>] in the term? how does one understand what to name the params when controlling a plugin?
the message is: "port symbol:direction symbol:type symbol:name float:lowerlimit float:upperlimit"
with symbol:direction being either "in" or "out" with symbol:type being "control" or "audio" with symbol:name being the name of the port (e.g. "Amplitude random (%)")
and lower/upperlimit define the valid range of the value.
for controlling, you use "control symbol:name float:value"
symbol:name is not case-sensitive, and it tries to find a simple match. e.g. "Amplitude random (%)" can be controlled with "amp" or "AMPLItude" or "Amplitude random (%)". it will take the first port that matches, so if you have parameters "FrequencyUpper" and "FrequencyLower", then "freq" will match "FrequencyUpper", in order to conrol the other param you have to use at least "frequencyl"
thanks a million for this :) -- let me chew on this info today and I'll see if I have any more questions
also, I also noticed that I can't use a number in the [print] external in my current version of PdX that I'm working in without causing the error: 'expected symbol' but in the latest version of PdX I can use a number as well as a symbol in [print]
well, you can use [print :1], if you want to stay compatible with e.g. Pd-vanilla.
ok -- a good tip -- thanks again!
mfgasdr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkwSNM0ACgkQkX2Xpv6ydvRhdACgpld4N/mRShDv/OT6p9Z8D/MT MyMAn0b1mNdDPvlGn8FuMOf7Fp4iNhZ4 =v7Gc -----END PGP SIGNATURE-----