In his clear and extensive guide about creating expression maps, Paul suggests to go on section by section, and save a Dorico project for each orchestra section. So, you configure all the woodwinds, save the sound assignment to an endpoint configuration, and add that endpoint configuration to the Playback Template. Then, you save the Dorico project, to be able to quickly access that endpoint configuration again when you need to make a change.
I’m building my expression maps for the VSL BBO libraries each time a buy (or win…) one of them. Since these libraries often contain all the orchestra sections, or mixed ensembles, the logic of saving separate Dorico projects by orchestral section wouldn’t work in this case.
What’s the idea? Would you save a separate Dorico project for each BBO library? This should at least give you two advantages:
- keep everything well organized;
- add the expression maps and relative playback techniques for each library to the Playback Template.
Linking Dorico instruments to the actual sounds would have to be made by hand, since there aren’t dedicated instrument definitions for BBO in Dorico, but at least you would have everything ready.
At the moment, I’ve everything in a single Dorico project. This is letting me share some playback techniques, like ‘swell short’ or ‘swell long’, that appear in multiple libraries. I don’t know if this would be, in the end the best solution. Or if, but adding endpoint configurations to the Playback Templates, Dorico will in any case be able to join these redundant playback techniques.