Yes. Look at this demonstration I made a few years back (video below this paragraph). The expression map contains two sets of expressions: one starting with “a” (for the principal instrument) and one starting with “b” (for the other instrument). Each expression group (group a and group b) routes the note to a different patch in the multi timbral VSTi.
The point is to have the flexibility of editing CC points for each patch (patch for Violas1 and patch for Violas2), independently. And by “Patch” I’m refering to a program/player that responds to articulation key switches. I’ve described my current workflow (my workaround) in another post that I’m pasting here:
My workflow/orchestra template
In order to edit something in a project with 80 tracks (32 staves in the score editor), it’s a bit tiresome for me to keep looking at the Track List (to make sure I’m not copying / splitting / resizing / etc the wrong MIDI part).
One suggestion would be to color the tracks differently, but I’d rather not do it, because I want my template to look like this:
- Green, for parts containing MIDI notes only (staff track).
- Grey, for parts containing controller information only (expression track).
These grey tracks allow me to control the expression (gain, attack, release, pitch-bend, etc) of principal (1st) and supporting (2nd) oboe / flute / etc… independently, while both play on the same stave.
There’s also a “C” articulation, which — if selected — will make both patches (players) receive — at the same time — the same MIDI note message.
Screenshot (Expression Map window)
Original topic of the above workflow: here.