On 2010-06-14 22:27, Kim Cascone wrote: > > =============== > first level of confusion > =============== > > occurs when a user is looking for the 'lpf' messages on the command line > using > > analyseplugin lpf > > they won't find it unless they read the console carefully and see the > LADSPA plug is actually called 'cmt.so' > > and if they type in > analyseplugin cmt.so > > they will have to scroll through the dozens of plugins inside 'cmt.so' > for the lpf plug > > not a bug per se but there must be other plugs that come bundled like > the cmt.so which present a similar confusion...?
not a bug per se at all, but rather a problem with "analyseplugin" don't you think so? > > =================== > the second level of confusion > =================== > > occurs when sending [plugin~ lpf] an [info] message in a patch > > the [pd/print] object reports to the console: > > b: port in control Cutoff Frequency (Hz) 0 0.5 > b: port in audio Input 0 1 > b: port out audio Output 0 1 > > leading the user to believe that the Cutoff Freq is controlled with a > float from [0 - 0.5] > instead of [0 - 0.5*srate] (n times the sample rate) > > while 'analyseplugin cmt.so' reports: > [...] > Ports: "Cutoff Frequency (Hz)" input, control, 0 to 0.5*srate, > default 440, logarithmic [...] > "Input" input, audio > "Output" output, audio > > > as you can see the [pd/print] object is not reporting the correct > message to send for 'cutoff freq' > it SHOULD read: > b: port in control Cutoff Frequency (Hz) 0 0.5*srate > > but is reporting > b: port in control Cutoff Frequency (Hz) 0 0.5 > > so it seems the [pd/print] object is not passing the '*' symbol i'm sure you don't want to get a symbol "0.5*srate" for the upper boundary. the idea is of course, to do something meaningful with the data you get, e.g. set the boundaries of a slider or similar. you wouldn't want to parse the meaing of the symbol "0.5*srate" yourself in Pd as it is. (at least: i wouldn't) if you are only interested in some visual feedback (e.g. the printout at the console), then you probably should just use "analyseplugin"... > > is this a known issue or can it be changed? it should be possible to change it. the obvious solution is to pre-multiply with the srate if needed. another possibility would be to add extra information whether the boundaries have to be multiplied by something. fgmadsr# IOhannes
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
