Michael Canavan wrote:bayswater wrote:Maybe there is something simple I'm missing. Do you have a set of a set steps that work reliably?
Sure, I just completed one for EWSO 11 violins!
So forgive me for walking through the whole thing since you've done most of it.
1- Pull up the instrument you want to use, and (IMO) two MIDI tracks. One for the keyswitches and one for recording the instrument notes.
2- Go into Device groups, create one with only that instrument in it. (in my case here EW Play) Name it after the Keyswitch patch you're using it for.
3- take one of the MIDI tracks and point it's output at the Device Group ( in my case 11V M for 11 Violins Master KS )
4- Name the MIDI notes the names of the Keyswitches.
5- Check to make sure it works.
6- Erase all notes from the tracks and select all three tracks.
7- Copy to Clipping Window, I have several for various things, hardware, Virtual Instruments etc. Name it ( in my case EW 11 Violins KS ).
8- When you instantiate the Clipping in a project, for some reason DP doesn't recognize my master audio out from the Clipping, (reported to DP in my case as
Analog 1-8 1-2) so you stupidly have to select the output from the virtual instrument in the track and select... Analog 1-8 1-2. Play, Kontakt etc. then gets activated and you can use the named Drum editor keyswitches.
Basically saving the whole set up as a Clipping works, it would be cool if the Drum Editor just had presets that worked, but you have to save the virtual instrument as a Device Group to name the Drum Editor notes. and I don't know any other way to save Device Groups and named Drum editor notes besides saving the tracks as a Clipping. This IMO is all a lot better with the Content Browser, Clippings become even more useful and easy to deal with.
Thanks. I'll go over this in some detail and follow it with a new project to see if there is anything different from what I've been doing. At this point I think it is pretty much what I've done to set up drum VIs with drum names in the Drum Editor.
I can of course do this. I set up a Device Group (who knows why you need to do this, rather than simply creating and saving a set of drum notes, but there it is), associate it with the VI, and assign the MIDI tracks to it. It all works, but it appears to be specific to the project. If you go through all the same steps in a new project, and bring up the preset with the note names, nothing happens -- you have to edit the note names all over again. It not only has to be the same track, Device group, VI, and note name file, it has to be the same project.
I've got around this by stopping at the point where you deleted the notes in the MIDI file (which I don't actually have to do, BTW) and save what I have at that point as a template.
So this is not such a big deal. The VI can be in a V-Rack, so if you don't need it you can just ignore it. but even then I have to repeat the assignment of the VI to the Device Group, then the MIDI tracks to the Device Group before the MIDI tracks play the VI, even while the routing is already set up this way in the template. Again, not a lot of work, but possibly a bug that plays up when a template is loaded. This is not necessary if it's a project being loaded.
But where this fails miserably, is if I want to use a different Drum VI, I have to start all over from scratch. I can't even set up the Device Groups, VIs, MIDI tracks etc, and then load in the Note names. If I do, it doesn't actually show the saved names in the Drum Editor. You have to enter all the Drum note names yet again.
I think Logic has a much simpler and more effective solution. You can enter note names in the basic MIDI editor, and set the display options so only notes that are used show up in the note lanes. Done. If these options were added to the MIDI editors, the Drum Editor would be redundant.
Doing this, I've also noticed that MIDI has to be unpacked to show up in the Drum Editor. If you pack it or record it as clips, nothing shows up in the Drum Editor, even if that's where you are recording it. I'm wondering if this is going to be fixed in DP 10.12. It looks to me like the Drum Editor has been deprecated. I noticed some of the themes don't work properly in it, so it doesn't look like it gets checked properly in updated.