[Bluemusic-users] Parameters - Automatic for BSB and Effects?

[Steven Y. <ste...@gm...>]

HI All,

I'm getting to the point where the infrastructure work is getting to a
usable point for Parameter Automation and I'm about to start
experimenting with Effects and BSB instruments.  I am split on how
exactly to do this.

One method is to make all BSB widgets that are used in Effects or BSB
automatically become automatable parameters.  The widget's object name
then would be what is used for displaying the parameter name.  What
happens then is if the parameter is not automated, in the instrument
text the key <objectName> would simply be replaced with the value of
the widget as it is done currently.  If the parameter is set to use
automation data, the key <objectName> is going to be replaced with a
krate variable (I will probalby use gk signals now as it's easy to
program, but will possibly switch to k- signals later; either way, a
krate sig).

Now, this maintains backwards compatibility in the sense that projects
pre-automation blue will work exactly the same afterwards.  Now, if
your instrument is designed in such a way that if the key <objectName>
is in a place in the instrument code where it is invalid to take in a
k-rate signal, you'll have to revise your instrument code to do so.

The other option for Effects and BSB is to have a table of widgets
used and checkboxes next to them where one explicitly checks off and
enables a widget to be automated.  This seems tedious but then it
allows some other things: one could probably in the table enter what
the Display name should be for the widget when used as an automation
parameter, as well as one can protect other values from not being
automatable.

(Note: Some widgets like the BSB line objects and dropdowns won't be
automatable)

Another possibility is do it within widget's editor, but that might be
a bit tedious to quickly see what parameters are available.

I think the Parameter Table and explicitly setting the option might be
the most flexible possibility.  I can also make it so that one can
reorder the parameters too to the values one would want to use.

Hmm... while writing this I just thought about something else.  One
might want to make a pure text parameter too.  I should probably
explain my plan then for the other non-GUI instruments.  For those
like GenericInstrument, I was planning on adding a table where one
enters in automatable parameters for your instruments (<paramName>,
display name, min, max, default value).  Then in the code, one can put
in <paramName>, and if not automated the default value is used, and if
automated a ksig is used.  This might be an nice option to have for
BSB as well for parameters where users might not want to create  GUI
for it (can't think of a situation off the top of my head but could be
useful I guess).

Any thoughts on this?

Thanks!
steven