Does anyone know of a way to route expression data recorded into CC11 to dynamic markings on the score automatically (via some sort of automation or macro, or perhaps a built in feature)?
It isn’t so much of a hassle to go back and retroactively add in dynamic markings, but since I haven’t done it yet on this project I worry that adding dynamic markings may override the data that I’ve recorded into the CC.
This is my first project using an expression controller to “play in” my own expression data, so I am unfamiliar with the nuances that coincide with these techniques.
Hi. I don’t think Dorico can do that this way round. The program is suited to create such modifications of CC11 (usually as a secondary dynamics CC in the expression map) according to the dynamics markings available on the page, but AFAIK it cannot create dynamics markings from any CC nor velocity layers. Note that it could be a feature request.
It depends very much on the library used…
I mostly use EWQL libraries - for this particular project I’m working with Hollywood Orchestra. Thanks for the info!
Hello @crodriquenz. I have a similar workflow to you (including EWQL).
My approach is to insert the dynamic markings retrospectively. To avoid any overriding of recorded CC (and/or velocity) data, in the Expression Map I set Volume dynamic to CC2.
EWQL generally doesn’t react to CC2, so this effectively disables the data of the dynamic markings (by sending it “nowhere important”), leaving my recorded CC (and/or velocity) data to do the actual work.
You can always look at the CC lanes in the Key Editor to double-check which CC values are being sent to Play/Opus.
I imagine that writing an algorithm for converting CC data to dynamic markings would be rather difficult. Most people use CC data to simulate subtle swells of bows and breath, but this is not generally notated with dynamic markings, so without some very clever algorithms to define and detect “meaningful” changes in CC data, there would be a lot of false positives resulting in streams of unwanted hairpins and other dynamic markings.
I think even if such an algorithm existed, I would turn it off. Not all VSTs react to CC data in the same way, so I’d much rather play in exactly what I want to hear and type in exactly what I want to see.