Cubase drum maps don’t really do the same job as Dorico’s percussion maps – they only really provide a mapping between the MIDI note number and a name or label for that note as it appears in the drum editor in Cubase. Dorico’s percussion maps require semantic information about the instruments and playing techniques in addition to the name.
Of course you can! But you will need to work a little bit… For the record, I’ve set up perc maps for the default SD3 library, Hitman and sticks and brushes. That orchestral percussion library was very much into my radar, but I already have percussion library (I made Spitfire’s Percussion Joby Burgess work in Dorico) and these Toontrack libraries are not cheap. If only they would endorse people who create percussion maps for them…
That’s not the problem… I don’t have that library, that’s the problem And you won’t buy it to me just so I can spend some time and build the percussion maps that would allow us to use it seamlessly in Dorico. I’ll wait for the Black Friday offers, maybe it will be worth it. (I mean, 279€ is a lot of money for sounds I already have in Spitfire’s library, VSL prime’s, HOOPUS’, Iconica sketch’s, NotePerformer… although I really love what SD3 provides sonically)
Ok, I’ve just written to their support. If they do endorse me, I’ll do it
The playback template (decompress it and put it in the PlaybackTemplateSpecs folder in the user folder where everything is (keycommands_xx.json, userlibrary.xml, etc.) or drag and drop the playbacktemplatespec.xml file on your dorico file (that might work).
It is set to use manually all the samples I’ve kept in the map and use NotePerformer (auto) for what’s not in there, but that’s something that can be modified, simply by editing it (pen icon in the playback templates window) and removing the NotePerformer bit and adding another auto Endpoint.
Note that I decided not to include the timpani nor the bells, since those are pitched percussion instruments and I could not find a clever way to make this work — Spitfire Percussion Joby Burgess was easier to deal with in this regard, since there were different “instruments”, some being unpitched, other pitched… Here everything is messed up together, it’s probably practical for DAW users but certainly not for Dorico users!
Note that I was not able to import a groove (as I usually do with Superior Drummer stuff) because we’re not dealing with Drum sets here, and the MIDI import window does not seem to be ok with importing different MIDI instruments when they’re percussion and they come from the same VSTi (orchestral percussion I and orchestral percussion II). If anyone has a working workflow here, I’d be interested (although I’m less prone to use existing grooves with this that with the other Superior Drummer stuff).
Here’s a new version of the file, built with kits. I thought it could solve my import problem, and it did to some extent, but not entirely, so I’m not quite satisfied… However, it could prove useful to have each sub-library as a kit, so here it is :
It’s quite easy for you to create them, providing you use the dorico file I’ve uploaded! That’s why I share the dorico file along the endpoints and the playback template: so that you can quickly build up what you need, with every boring routing thing already set up!
please