One problem solved then another pops up. I created divisi on the Violins and Violas and enabled independent playback. Here’s a small sample of what appears in CC7 & 11 controller lanes:
It’s playing havoc with playback. How do I delete these - I think this info was in a lane before I created the divisi and was deleted by selecting it. I’ve tried everything I can think of but they keep coming back. Thanks, CD
It does no look like manually entered automation. What are the control parameters defined in your expression map (EM)?
Do note that as mentioned in many posts that Dorico sets CC7 the main volume to 100 at playback start or when you stop (it does not matter). I thought they had finally abandoned this undesired intervention in the users plugins but it is back although I could not exactly find out when it intervenes. I therefore reallocated all CC7 faders in my instrument plugins to CC127.
Normally it does nothing with CC11 however. In my plugins CC11 is set to 127 and CC1 and velocity control the instruments in the plugin. However e.g. Spitfire uses CC11 instead of velocity for the dynamics. Maybe you defined it as such in your EM.
I’m working with a trial of Dorico 6.1 and I’ve just run into this. A screen grab is attached. I have a little context that makes this even more peculiar.
The score came via MusicXML. It was exported from Sibelius, which had imported it from a MIDI file. The original MIDI file had all velocities set at 64 and no CCs of any sort. The Sib file had only a single MF dynamic set at the beginning, with no accents, crescendi or anything else (this is just a note collection for purposes of my own research). The expression map that I wrote for this piano lists velocity as the volume dynamic, with CC11 as secondary. But the map never causes cc11 to be emitted. Even if it did, CC11 would always have a steady value. Instead, it jumps up and down as you can see. Sonically, it’s obviously having an effect.
I can overwrite this lane with fresh CC1 data, but I can’t change or delete these “ghost” values. They have no business being there in the first place. What in the world is going on?
By default Dorico will apply humanization (unless you switch it off) in Playback Options>Dynamics. In particular it will apply the polyphonic voice balancing to a Piano by default. This likely accounts for the variations you see.
Also Piano VSTs usually use the Default expression map. The instrument only responds to Velocity dynamics (since a piano can’t respond to anything once the note has been struck).
I just learned by accident that EW Pianos use CC11 for overall volume and CC1 for attack (lower=smoother/normal; higher values=shorter to the point that 127=short staccato) - quite the surprise actually.
Thanks Janus. There were a lot of places in the PB options to tweak, but I’ve gotten that taken care of. The only reason I mentioned MusicXML is because it doesn’t carry any direct controller stuff (I just wanted to eliminate any source of “pollution” along the way).
Only reason I had an expression map was to support the Una Corda and half-pedaling capabilities of the pianos I use. But yes, the default map is useful in a lot of spots.