A deeply felt THANK YOU to both of you, Jonathan and Michael!!
Greatly appreciated.
I was about to reply that none of my playing & playback techniques were found across other projects when I caught your (Jonathan) explanation – worth ‘five’ stars to me, not just one ( Save as Default [image]! I double-checked with the operation manual and indeed I should have read more carefully - it does say “allowing you to use it in multiple projects” 
And you also explain how to make the maps globally available via the DefaultLibraryAdditions. I saw already a bunch of VSL maps in there.
Merci, merci!
1 Like
I think VSL does this by manually copying the map there. This isn’t something you would normally do as a user - but you could do this yourself, of course.
The general way that users are expected to interact with the systems is that they will first make expression maps, percussion maps, and possibly custom playback techniques that reference those on a lowest level. Following this, they will make one or more endpoint configurations that include the instrument load data (for the VSTi plugin to load the instrument) plus the expression maps, percussion maps, and custom playback techniques. One or more of these endpoint configurations is then bundled inside a “playback template”, which the user makes. So the playback template contains the endpoint configurations, which themselves include the expression maps, percussion maps, and custom playback techniques.
Then the user can take this playback template and send it to another user to use, or apply it to another one of their Dorico projects, and that will apply the endpoint configuration, which in turn installs the expression maps, percussion maps, and custom playback techniques referenced by said maps into that project.
This process when done in this straightforward situation generally works without incident, but even though I am fairly advanced with Dorico playback, the one part that I am not entirely clear on is if you do this and decide to make changes to the template, what do you have to do to ensure those changes are brought to another project file on the same system that is also using the same template? That’s something I’m not entirely certain about and would have to do some experimentation and research to determine.
1 Like
I salute Jonathan’s creativity in finding this work around - which you believe may in fact be part of VSL’s own workflow. And I also think that there should be a more ‘standard’ or normalized way of achieving this result - like the ‘make default’ button illustrated by Jonathan.
I must now create an imaging plan for my telescope computer (tonight may be a once in a month clear sky opportunity, so I don’t want to miss it) but I’ll work out all those things you both said later this week.
I don’t want to be a bother but may I message you both, the next time if I encounter an issue?
1 Like