[EDIT: skip the initial post to find the workaround, if interested]
I must be doing something wrong when trying to set this up … but for the love of Ravel, I can’t figure out where I’ve gone astray. I apologize for the lengthy, confusing post but I found it very hard to articulate this; please bear with me. I appreciate any help/clarification/ideas from anyone kind enough to read this!
In between other tasks, I’ve been trying out the new independent voice playback feature in divisi contexts.
The Goal: To create a dummy-file I can use as a ready-to-go template, containing all the divisi permutations I use most frequently, already routed/connected in play mode, so that I don’t have to make those connections every time I start a new project or new flow.
The original way I approached this (described below), which I thought would be the quickest/easiest way to achieve the goal, somehow didn’t work for me. I’m not wedded to the approach I tried; I’m happy to employ any method that achieves the goal. Any brilliant ideas are most welcome and greatly appreciated — or even just a clarification of how the “Set for All Flows” feature actually works, since despite RTFM, I’ve apparently misunderstood it.
The approach I thought would work: I have each of the various section division sizes on separate channels in Vienna Ensemble Pro. I entered various divisi permutations into different voices, enabled independent voice playback and the “Set for All Flows” option, and routed all the endpoints appropriately. Having accomplished that, I thought that as long as I ensured all music in future flows was notated in the relevant voice(s), everything would play back as “Set for All Flows.”
First minor wrinkle: when changing the number of divisi staves (as opposed to using multiple voices on one stave), the numbering of voices no longer matches intuitively between write mode and play mode. (Real-world example from my test file: 2nd stave’s up-stem voice #2 in write mode = up-stem voice #3 in play mode. This is just to illustrate the behavior; obviously the specific namings would be different if voices/staves had been created in a different order).
No problem, methought; as long as voices/endpoints in play mode are Set for All Flows, all I need to do is be consistent when entering music into the relevant write-mode-voices for any given divisi permutation, and all will play back without further fuss.
But that’s precisely where I hit a brick wall. When I created a new flow, even though independent voice playback and “Set for All Flows” had all been previously routed in play mode and worked perfectly in OriginalFlow, none of NewFlow’s play mode settings matched those in OriginalFlow.
This is a little confusing to describe, please bear with me, but as one example:
— OriginalFlow, 1st stave, up-stem voice #4 in write mode = play mode up-stem voice #7, and plays back correctly as assigned. However:
— NewFlow*, 1st stave, up-stem voice #4 in write mode = play mode up-stem voice #4.
*(where divisi permutations arose in a different compositional order than OriginalFlow)
In other words they just don’t match flow-to-flow, even though “Set for All Flows” was chosen, and thus the relevant virtual instrument channels aren’t being triggered correctly in any flow except OriginalFlow.
With “Set for All Flows” already enabled, I would have expected all voices (bound to their relevant staves) from OriginalFlow to be available in NewFlow via the note input caret. Nope; only the default up- and down-stem voices were present when cycling through the options. Thus I couldn’t jump directly into entering music in NewFlow into voices already created in OriginalFlow … for example, I couldn’t enter into 1st stave up-stem voice #7 straight away, even though that voice already existed in OriginalFlow.
So I tried repeatedly using “Change Voice —> New Up-Stem Voice” until I reached the desired voice. But, it didn’t play back. Nothing “broke” in OriginalFlow, where all plays back exactly as assigned and “Set for All Flows”, but these settings didn’t carry over into NewFlow.
The options in play mode aren’t even listed the same way in OriginalFlow and NewFlow. For instance (another real world example), in OriginalFlow, 1st stave up-stem voice #4 in write mode = play mode up-stem voice #7, set for all flows … but in NewFlow, even when entering into write mode 1st stave up-stem voice #4, there is no up-stem voice #7 listed in play mode — instead of adhering to what was set for all flows, NewFlow voices in play mode were either unassigned (showing up as “- - - “), or assigned completely differently than in OriginalFlow. (e.g., NewFlow 1st stave up-stem voice #4 in write mode was automatically assigned to up-stem voice #4 in play mode – not up-stem voice #7, as is the case for OriginalFlow, and what I expected from having selected “Set for All Flows” when setting everything up)!
I don’t know about you, but I’m certainly wishing I were better at articulating this more succinctly! My sincere apologies.
Bottom line, I must be misunderstanding something about how to set independent voices up for playback on all flows, such that one doesn’t have to manually assign every voice’s endpoint on a per-flow basis as new flows are created. Please help me see where I went wrong, or help me brainstorm a different way to achieve what I’m after.
Any brilliant ideas … ?
Many, many thanks,
p.s. Stupid auto-correct keeps changing “up-stem” into “upset.” I’m not upset; I tried to squelch these auto-correct fails, but if I missed any I assure you it wasn’t a Freudian slip! (Freud was full of it; I prefer Jung )