When doing CC11 automation overrides, it would be nice to have an idea where Dorico normally sets things at a default level before I mess with it. For example in Cubase or Logic, even with no manual automation added, there’s always a line or nodes (grayed out) which allow you to see where the value is currently set automatically by the program.
I am using a lot of VSL instruments lately which are very sensitive to CC11 and sometimes doing automation throws other parts completely off. I am wondering if there is a value I could set at the beginning of my composition so when I playback from the start it always resets to a default value. I just have no idea what that might be.
If Dorico isn’t changing any values in CC11 (e.g. because it’s not specified in the expression map for anything), then it won’t be sending any values. The controller will be reset (because all controllers are reset) so I would expect it to remain at value 0.
Oh, well, I mean – I definitely hear something – unless I manually turn it all the way down to 0. So I imagine it is some kind of middle range value, perhaps somewhere between 90-100ish? Since a lot of instruments do treat CC11/expression practically like a volume (similar to CC7). So I don’t know what their neutral starting point is.
So I’m looking to make the sections which I don’t manually override with my own automation to reset to a neutral/default value. Otherwise when playing back the instrument goes silent at the parts I don’t touch (ideally without having to automate everything manually - if I could just add a ‘neutral’ automation point that would be fine).
You could try to route the midi from dorico to a DAW, and record there what happens when you start and stop the playback in dorico. I don’t know what the baseline is, if there even is one…
In an exposed solo moment which needs love, I am more inclined to hone in with manual CC11 data, to really shape the expression and dynamics. However, for other sections where I’m simply doubling or it’s less critical, I wish it could just snap to a default where the instrument always sounds typically neutral out of the box. Where my playhead is parked there, it will now be too quiet, but in the next section I manually cranked it all the way up (127) and it will be too loud. So my thinking was to add “reset” nodes in between my custom automations. I guess I’ll run some tests and find a number which seems to reflect the neutral starting point.
After doing further research and digging into my different libraries, it appears there is no default standard (as I thought there might be), but it varies from developer to developer.
Turns out all my VSL patches load by default with CC11 set to max 127, whereas the particular patches I’m using with expression maps have them set to about half that - default 63.
So knowing that, I guess what I could do is create a “reset” automation node at the beginning and end of 63, so that any automation I add in between should reset to that baseline.
The starting point for CC11 is almost universally 127, so assuming the default, you can make the instrument quieter, but not louder.
To my knowledge, the only time this wouldn’t be the case is when CC11 is used for the non-standard purpose of a dynamic controller (like with Sample Modeling Brass), doing the dynamic crossfade instead of CC1.
Whenever CC11 is used for its normal purpose as a secondary volume controller (with CC7 being the primary one), it always defaults to 127 in every library I have ever used, as well as old MIDI sound modules (Roland SC-88, E-mu Proteus) that I used to use a few decades ago.
Thank you, that’s very helpful. With my combined template using non-NPPE VSL instruments, the CC11 dips and resets were resulting in lots of crazy volume balance issues. I think just adding an automation point at the beginning of my compositions (for 127) will solve that so I always have a baseline to tweak from. Cheers!
