I’ve been using Addictive Drums for a while now with the standard GM mapping. I have to do a project that needs 7 toms, kick, snare, ride and crash. I figured this is a simple kit, small number of mappings – I can do it manually. So I started building it piece by piece making sure the kit matches the percussion map and the percussion map actually work.
The kit (so far)
Fairly simple. Kick and Snare work fine, neither floor tom work. The percussion map:
Again, fairly simple, but I can’t for the life of me figure out why the tom notes appear with 0 velocity. Not only that, when I try to increase the velocity, it jumps back to 0. See editor:
I’m attaching the project as well. There is definitely something right in front of my eyes that I’m missing and I’m hoping some of the many eyes here can find it.
Thanks
test-lots-of-toms.dorico (426.2 KB)
I have no idea how it happened, but somehow the project got deactivated. Apparently, while deactivated, I added both floor toms and they weren’t wired up to the Addictive Drums VST and didn’t have any percussion map assigned.
Strange… very strange.
Carry on.
Had nothing to do with the project being activated or not. When adding an instrument to a percussion kit, it isn’t automatically wire to the VST and has no percussion map. I’d almost consider this a bug.
Are you absolutely positive that you have not changed anything manually to the Play stuff? Because doing so is considered by Dorico as an override and it stops doing any automagic routing…
Try reloading the playback template to make it automagic again?
Well, I cleared out all the instruments in the kit except kick and snare as they were the easiest to map. I didn’t realize fiddling with the kit (adding/removing pieces) causes Dorico such confusion.
I can replicate it now with every new piece I add to the kit: I have to go to the Play tab and route the new piece myself.
Oh, and it’s not a playback template (yet), just getting started with 1 VST.
You could perfectly have a playback template for one instrument…
Once you fiddle manually, you need to do all the routing and map settings manually by design, this is nowhere near a bug 
1 Like
Well, it’s a kit. By design a kit has 1 VST on MIDI channel 1. I don’t see how adding and removing a piece from the kit should impede Dorico from adding the instrument and wiring it up to the same VST that all the other instruments are wired to.
You’re right. What causes Dorico to stop routing automatically is when you fiddle with routing manually in Play mode. If that’s not what you have done (accidentally, I mean), then I agree there is a problem and you could upload the project here.
I don’t fiddle with routing on drum sets (for the obvious reason, it’s 1 VST on MIDI channel 1 
).
I’m running out of steam now but I’ll try and replicate this on a fresh project in the morning.
Thanks
1 Like
I can’t reproduce it with a fresh project and the GASE playback template (well, the Iconica… GASE template). I think you were on to something earlier about Playback Templates. Perhaps not having all the instruments in the template originally, actually, the Endpoint, Dorico doesn’t know what to do with new pieces added to a kit – although like I wrote above, it’s a kit and should be treated as one instrument.
I liken this behavior to adding a new VSTi (e.g., super-duper-new-strings), routing a fictitious Violin 1 and then enabling IVP – the new track isn’t routed.
1 Like
Percussion kits are not necessarily treated as a single instrument: each individual percussion instrument in the kit can be routed to a different endpoint if necessary.
That much is clear. I guess the conclusion here is that all pieces (instruments) in the kit need to be routed and the endpoint saved before one can delete and recreate pieces inside the kit. Case in point, my VST was just a standalone after I deleted all the instruments (except kick and snare), adding pieces back in weren’t routed. Whereas if I had all the kit pieces assigned in the VST, saved the endpoint and created a Playback template, like GASE, I can freely delete and re-add pieces and Dorico would know how to route them — lesson learned.
It would be fabulous if you had a white-paper(-ish) document outlining the relationships between an instrument, its route, endpoints and playback templates and all the finer details like percussion kits, IVP etc. — would be a fascinating read.
1 Like
