Digging into the automation lanes lately to help smooth out certain instruments, I’ve noticed that many times there is automatic data on usually either CC1 or CC11 (I believe based on the dynamic settings under humanize etc, where the actual dynamic lanes seems to effect them), where it appears like a stair-steppy shadow line.
I’m just trying to figure out why sometimes, this data gets automatically placed on CC1:
I would just like to be able to make it consistent for my workflow, probably CC1, and wondering if there is some reason that a few of them get dynamics data placed on CC11 instead.
Hi @wing, sorry if I don’t understood your request. But are your screenshots (and the corresponding CC1 and CC11 lanes) from the same instrument/track? Probably not because of the different colours. Are they from the same library/using the same Expression map?
You know this for sure:
the used CC1 vs CC11 (for dynamics) are set in the expression map. For example: Note performer uses always CC11 (and always note velocity for the secondary dynamic), while Iconica Sketch uses CC1 for the Longs, and note velocity for the Shorts.
So depending on the used mixed libraries in the same project (and their assigned EM) you have different CC being used.
(again sorry if I totally misunderstood your question)
No I think you understood it correctly! I use a lot of combination between NotePerformer and some VEP/VSL/Kontakt/etc. Even though I’ve made many expression maps before, I wasn’t aware that it sort of plots out this data automatically (as that shadow line in my screenshots) based on the expression maps themselves. I thought maybe this data was determined within the humanization options, and was confused why it would be CC1 for some and CC11 for others (and yes, the above were different instruments/staves). I will take a closer look next time I open a hybrid project which uses both NP and others and can perhaps have a look under the hood to confirm this is where I might be seeing the difference. But in short, based on what you’re saying, the data on those lanes are based on (or generated by) whatever the connected expression maps use, if I understand you correctly?
Yes, this is how I think it works. When you write a dynamic into the score, Dorico looks for the expression map and which CC is assigned to the dynamics, and creates the appropriate CC lanes. These dynamics that you input into the score are also visualised nicely in the Dynamics lane.
If you edit the Dynamics lane (that is interconnected to the written dynamics of the score), also the corresponding CC is changing in the CC lane.
If you edit the CC lane (assigned to dynamics in the EM) directly, this will not change the Dynamics lane visualisation (nor the score), but will have a direct effect on the heard dynamics (its CC data will be sent to the VST). If you then delete the manual editing in the CC lane, the CC lane will use the informations of the Dynamics lane to redraw its data.
So as sum-up it seems to work in three levels:
Score
Dynamics lane
CC lane
This gives a great control: 1) of the appearance into the score, 2) editing possibilities in the Dynamics lane (that will, depending on the circumstances, change or not the visualised dynamics of the score), 3) and even more granular manual editing into the CC lane (that will not change the Dynamics lane, nor the score).
Hopefully is clear what I explained (and I hope that is also correct (I tested it, at least ), otherwise please someone correct me)
Yes yes! You understood it perfectly, that was it I also tested on an instrument by simply switching from the NotePerformer expression map to another one I use often which I know uses CC1, and when observing the key editor I could see the shadow line immediately shift from CC11 to CC1. I also tested the “Modwheel Dynamics” default map (which is CC1) and the “CC11 Dynamics” default map (even without switching the actual VST), and I was able to visually see which lane was impacted by the dynamics.
Finally the mystery is solved! I usually know which CC my selected VST prefers (and now knowing that NP prefers CC11), so this can be helpful to be aware before even adding manual automation overrides. Thanks Christian!
), otherwise please someone correct me)