I’ve put up a new release of blue available at:
http://www.csounds.com/stevenyi/blue
The big feature for this release is the implementation of Sends in the
Mixer. They can be placed anywhere in the pre and post-fader effects
bins, as well as can be automated on the timeline. A new subchannel
dropdown list object has also been added to BSB to do sends within the
instrument, useful if setting send amounts via score parameters rather
than by setting it up in the mixer.
The mixer code generation has also been rewritten for the Sends
feature and is a bit better optimized. A few other fixes and changes
are in as well, listed in the changeLog below.
Much thanks to Pia Kraft once again for help in testing the Sends feature!
Thanks and enjoy!
steven
[CHANGE LOG]
Notes for 0.114.0<
[released 2007.xx.xx]
Steven Yi———————————————————————–
blue
[new] – Mixer now allows adding Sends anywhere in pre and post fader effects
bins. Sends must follow current mixer contract of no feedback so
can only send forward down the chain. (Dropdown to select outchannel
for mixer and send is auto-updated to prevent feedback). Send amount
is automatable on main timeline.
[new] – BlueSynthBuilder – Added SubChannel dropdown widget that will allow
selecting a named subchannel to use as a replacement value in the
BSB ORC code. This is meant to be used with the subchannel form of
blueMixerOut, i.e. if the dropdown has an object name of REVERB, the
ORC code to use would be:
blueMixerOut “<REVERB>”, aleft * <REVERB_AMOUNT>, aright *
<REVERB_AMOUNT>
This allows an alternate way to do sends from the instrument rather
than from the Mixer itself, and is useful if setting the send value
by score parameter instead of setting within the mixer.
It is recommended when using the subChannel form of blueMixerOut
within instruments to use this widget instead of hardcoding the
subchannel name as this will be portable across projects
[new] – Added “Show Info Tabs Dialog” to Script Menu to make visible the
info tabs dialog that scripts use in case it is closed
[new] – Added <INSTR_NAME> blue variable that is the same as INSTR_ID but
for named instruments does not generate quotes around value
[new] – Script Library now supports drag and drop to manage scripts and
script categories
[updated] – Mixer generation code strategy reworked to better handle sends.
Further mixer generation optimizations to not generate signal
paths that won’t be used. (i.e. if fader is set to 0 and not
automated, remove rest of signal after fader from graph);
documentation for mixer updated to describe optimization strategy
[updated] – Presets – Presets for BSB/ObjectBuilder now save their held
values in alphabetic order of value name; this was done so that
when using with Source Control Management (i.e. Mercurial, SVN,
etc.) there wouldn’t be false positives on detecting changes
(previously the values were coming out in whatever order the keys
were mapped by HashMap which might change between loads of the
project or library)
[updated] – when importing instruments from blueShare, they will now go into
an “Imported Instruments” folder instead of adding to the root of
the user instrument library (matches behavior of what happens when
importing effects)
[fix] – BSB/ObjectBuilder XY object’s view label showing x and y values was
incorrectly displaying value (value held by object and generated by
object was correct for ranges however)
[fix] – Disallow subChannel to be named “Master” as it is reserved for
master channel out
[fix] – blueShare dialog would report a warning message to console when
opened each time after the first time as dialog was recreated each
time; now cached
internal
-BSBObjectRegistry split into BSBObjectRegistry, EffectsObjectRegistry, and
ObjectBuilderRegistry as new components are planned which will apply to some
contexts by not others
documentation
-updated Mixer documentation for Sends as well as details on the rules used
for optimizing Csound mixer code generation