How to re-use endpoint configurations or custom instruments

Dorico
1

When I need to use a special Low Brass instrument (trombone sounding), I select (e.g.) the BBO Hercules VST from VSL and assign a corresponding expression map from Art Conductor. I then give this definition a representative endpoint name (like ‘BBO Hercules Low Brass’) and save the endpoint. I also include that endpoint in my Playback template in the hope that Dorico will be able to reload exactly that combination of VST and expression map when I re-open the project. And it does!

However, if I now wish to add that same instrument to a new project, the “Add Section Player” of Dorico’s Setup doesn’t let me specify a ‘Hercules Low Brass’ instrument and I end up re-entering everything manually, including the player and the expression map…

I tried all sorts of things including creating a new trombone instrument named “BBO Hercules Low Brass” but nothing works. I must be missing something; how do others proceed?

2

There are a lot of unknowns in your description so I’ll start by asking: Did you reapply your custom playback template? Is your endpoint preferred, i.e., positioned in the playback template above the default (assuming you have a default, catch-all like NotePerformer)?

3

Hello, yes fair questions. Absolutely: apply & close done and all endpoints moved up in the playback template list before their corresponding standard VSL entries. Still, after Setup->Add Section player Brass->BBO Hercules Trombone the routing remains “–”, unassigned with no expression map.

--

Part of the problem is that adding a new instrument via Library->Instruments will remain captive of the local Dorico project. Create a new project and it will no longer be there. However, I didn’t expect that behaviour when adding a second time the same instrument within the same project.

Is there a comprehensive step-by-step write-up, anywhere, on the process to follow ?

--

I did something probably ridiculous: I created a single Dorico project with 101 VSL instruments and their expression maps and both saved it as a template and exported as a user library. If I now create a new Dorico project, I can use the Library Manager to “import” all settings and then all the expression maps find themselves in my project. But I still have to create ( Play->VST and midi->Add->select VSL (Synchron player) etc. all the way to assigning the expression map and then assigning that definition in the instrument’s routing). So, I gained nothing from adding a new instrument definition.

4

If you click the star icon, they should saved for any future project.

You can start here and then fill in the gaps with Dorico manual: https://www.youtube.com/watch?v=iFgBr3VqmeY

Something definitely isn’t right with the endpoint. Go over that video and back track your project to see if you did or didn’t do something.

5

Tks. I’ve covered the items. The endpoints are ok because when I re-open the project, everything falls back in place and Dorico loads the proper instruments with their VST and associated maps.
My problem is not in playing back it is in creating.

  1. I can create a custom instrument using Library → Instruments… and the instrument will appear in the list of Setup → Add Single Player or Add Section Player. For example, I like to add VSL BBO Jupiter horns for character. What I have in mind for that is a 12-player ensemble made up of the legacy Big Bang Orchestra: Jupiter VST with VSBB1 Horns sus Jupiter.doricolib as the appropriate expression map from Art Dorico.

However, the add will only bring in the notational properties of the instrument: it will not add the instrument along with its VST and expression maps. Moreover, the definition will only appear in the current project – which defeats the whole purpose. Library → Instruments… is valid only for the current project!

  1. There is no option in Library → Library Manager… to import the complete playback instrument from a user library or from another Dorico project.

You can import specific elements such as expression maps, playing techniques, playback techniques, percussion maps but never the complete instrument “bundle” (meaning: also containing the associated VST and expression/percussion maps).

It is possible to export the current project as a user Library. But if I then use the Library Manager to “import” settings (from that user library or from another Dorico project), this will add the expression maps but only as separate entities in a list of drop-down maps to assign and it will not import the VST definitions. So, I will still haver to undertake the manual creation of the instruments in the Play mode: (1) Play->VST and midi->Add->select VSL (Synchron player), enter the endpoint configuration name, load the VST instrument, configure its properties (perhaps use a VSL preset for that), assign the required expression map, the required playing techniques, assigning the entry to the instrument’s routing, etc. That’s what I want to avoid.

  1. Once inside a Dorico project, I can create and save an ensemble using Setup → Add ensemble.
    However, unlike in project templates, such custom ensembles only save the list of players and instruments. They do not carry over layout options, custom page templates, or specific playback configurations.

  2. If I save an instrument’s VST properties as a preset (this now is a VSL instrument preset), then that preset will not be not saved along in the original File → Save as Project Template… operation. I will have to apply the presets to all my VST instruments after they have been created in Dorico.

Addendum

After creating and assembling each of my VSL instrument, I save the endpoints and load them up IN FRONT of the VSL Assistant-generated playback template, so they are selected by priority. But when I “Add a single player” or “Add a section player” from the Setup mode, I don’t select endpoints, I only select notational “instruments” - none of the entries carries forth the associated playback settings.

And if I turn to the Library manager and try to import from a user library or from a Dorico project, it also doesn’t import the complete instrument with VST and assigned map: it imports the maps as separate items and none of the VST definitions.

6

That doesn’t necessarily mean that the stand-alone endpoint or the playback template is OK. Saving a project saves the entire playback infrastructure (and many other things). Your issue is adding a player/instrument and if the endpoint and playback template functioned correctly, the VST would self-load with the expression map and be properly routed. That’s not happening.

No, that is what an endpoint is for.

Correct. VSTs (expression maps etc.) are stored as endpoints.

Therein lies the problem. There is something wrong with the endpoint + playback template.

Those all should be saved with the project template. I’ve never seen a reversion to defaults using a project template. You might need to save the project template checking the “save flow” (I think that’s what it’s called) check box.

If I were in your situation, I would start very simply

  • create a new, empty project and apply the silence playback template
  • create your custom instrument (hit the star so it is saved).
  • Add it in setup mode
  • Add the VST, routing etc. and save that as an endpoint.
  • Add the new endpoint with that one instrument to a new playback template - just that one endpoint.
  • Save playback template

Create a new project, add your custom instrument and apply the template. Does that work? If it does, continue until you break it. Then you’ll know what is causing the problem.

7

Thanks for your patient and methodical approach. I have used your suggestion but gone in perhaps a slightly different route (see later, below).

I think one of the issues is that when you add an instrument to a score, it is only the notational definition that is involved. For example, you don’t add a VSL BBO Jupiter Horn section or a Spitfire Horn section; you just add a horn section. And although there can be several possible horn playing configurations (e.g. Horn a4, horn a8 and horn a12), to Dorico the only distinction is between a single player and a section player: the Add Section Player doesn’t make the distinction between a4, a8, a12 nor the distiunction between VSL Horns a4 and Spitfire horns a4.

My desired workflow would be (after adding the three section horns into the score) to use a new dialog within Play → MST and Midi wherein I could scan possible end-points and select/assign the ones that suit each of my three horn definitions.

Anyhow, here is what I did to (partially) solve my problem; it is based on your suggestion:

a) I built a single, ridiculously large Dorico project containing all my likely-to-be-used VSL instrument definitions & maps, and saved it as a Project Template (VSL FULL Orchestra). It names the different horns a4, a8, a12, etc.

b) I also saved a global view of all the endpoints (Play → VST and Midi → Save Endpoint configuration (2nd icon at the bottom) in that project. I called it VSL FULL Orchestra and it is stored in AppData\Roaming\Steinberg\Dorico 6\EndpointConfigs.

VSL FULL Orchestra
VSL FULL Orchestra800×615 171 KB

c) I then added this single VSL FULL Orchestra endpoint IN FRONT of the SILENCE entry in a new Playback template which I called VSL Playback. Later, I will add that endpoint in front of the Vienna Assistant-generated playback template content.

d) I then set this VSL Playback template as my default playback template, in preferences.

Now for the Creation part:

a) When I start a new project, I will select the 'FULL VSL orchestral as my initial project creation template – from the Orchestral category under ‘Create New…’; Dorico will create the new Project with all my VSL instruments and their playback settings.

b) Of course, I will make sure NOT to activate the project, at this point

c) I will then go into Setup and delete all unwanted instruments for the current project in mind.

d) I will then save that pruned version of the score as my new, working Dorico project.

e) For added safeguard (not to lose the content of the large orchestral beast) I will make the VSL FULL Orchestra template a read-only file, using Windows File Manager. I can change that prior to any updating of the template.

I think it will work. However, I still deplore the fact that I cannot easily create different instruments with their playback settings from Setup → Add Section player (it doesn’t discriminate a4, a8, a12 neither does it discriminate horns rendered by VSL, by Spitfire, by XYZ). I deplore having to go through that complicated (initial large project creation) and potentially risky (subsequent items deletion from the large project) process every time I create a new Dorico Project.

8

If you are playing around with Endpoints and Playback Templates, set your default playback template to Silence (Preferences>Play>Playback Template…).

Then, when you add a new player, nothing will be added to the playback and you can configure things yourself.

9

My template is also “every conceivable instrument I’d ever use” but I just “Save As…” first. I then have 4 layouts to work in: Full Score, Play, Print, Sketch. Play layout has section instruments while Print removes them and my Sketch is just piano, strings and single woodwinds. For each layout, I just tick or untick the instruments needed in said score. If I want to print (which I rarely do), then I go in and delete unnecessary players.

10

“tick or untick”… you are quite right! Quicker and more ‘generous’ than brutal delete (e.g. can still add more if need be). Tks… small details like that sometimes go a long way :slightly_smiling_face: