Displaying drum names in PRV ...

I know. It was a hassle removing the magic marker from my screen when I would switch from Toontrack to Addictive and then to Slate.
 
Now I use drum maps.

It is not that hard. Both FXexpansion and Cakewalk manage to add the information needed for the VST2.1 effGetMidiKeyName opcode in their plug-ins. Ask the other plug-in manufacturers to do the same. Drum maps and adding entries to master.ins are the only other solutions.

swamptooth
I can't imagine how exposing that parameter in a vst like battery would be helpful, especially when i replace snares vith various barnyard noises.

rfreeze
 All I want is an easy way to a list of drum kit piece names instead of a sideways piano keyboard when I'm working with drums.

I'm trying to envision this. Is it possible to "mock up" what you mean?

bapu

rfreeze
 All I want is an easy way to a list of drum kit piece names instead of a sideways piano keyboard when I'm working with drums.

I'm trying to envision this. Is it possible to "mock up" what you mean?

Sure.  In this pic the top left is what I want, the lower left is the default.  Specifically, I want the upper left without having to define mappings, I/O and other such tech stuff.  I just want to see the name of the kit pieces whether they're are "cowpeeonflatrock" or "Kick" or "Snare".  The worst part of this is that by following the instructions on the cake site, I ended up with the picture ... but now the drums are silent.
 
Hopefully I'll find what I want via instrument def, but my hope is limited.
 

rfreeze
The worst part of this is that by following the instructions on the cake site, I ended up with the picture ... but now the drums are silent.

 
Is your MIDI track at the top of the drums folder?
 
It was discovered by brundlefly that the MIDI track needs to be at the bottom of the drums folder in order to work.

Good to know.  Thanks.  That's one more point that says the display and routing pieces should be uncoupled.
 
 

thanks Blades, I'll check it out

Blades
Hey rfreeze - have you watched my drum maps video.  It shows how to completely use them from setup to routing and whatnot, but the actual setup part is fairly short and not that difficult.  You basically only have to do it once for the basic drum layout you use, assuming that you have any consistency in your song-to-song setup.  Since I've got vDrums, using the drum map is the only way things are usable, and for me, it's always the same map with the sam ins and outs so it's never a problem to setup.
 
Go to this address and spend the few minutes it takes to watch the video.  Hopefully you will get enough from that to quickly understand and build your map: http://blades85.com/music/sonar/88-specific-topics/79-sonar-drum-maps
 
If you have already gone through this and still don't get it, I'm sorry if I've wasted your time! :)

Great video blades.  The whole drum map process is very fiddly.  The mapping you do to different sample sources is pretty cool, but I still believe it's way too much work to get note names.
 
IMO, it's a waste of time for potentially 100s of users to each do the same basic map creation work.  I can imagine one Cake resource that knows the process really well spending a few minutes, for example, to get AD2 maps created.  To me that makes way more sense than 100s (1000s?) of people each spending a lot longer to get the same end results.  Especially for stuff Cake is going to bundle.  IMO, this is one of those border, differentiating opportunities that has been missed.
 
Oh well.  I guess I'll spend some time wheel-building so I can roll ...
 
Thanks again for the vid

That's how Linplug RMV loads up by default here.  The names are whatever is on the pad.  As mentioned before it's up to the plugin to report note names to the host.  Some don't like EZ Drummer etc........

Now that drum folder soloing is in place (for my workflow) I can finally sit down and make maps like EZD2->AD2 so that if I initially create patterns in EZD2 that I'm not happy with I can map/translate that EZD2 MIDI to AD2s mapping and try out kits in AD2.
 
It's going to be a ton of work.
 
You know what they say. Be careful what you ask for.

rfreeze
Now we're talking!  It would be awesome to be able to use the MIDI and song tool from EZD to build a track, then point it at the AD2 engine ...
 
I can see a need for the depth of drum maps for this kind of thing.

There is a forumite who actually was supplying this very thing recently. It mostly works, although the velocities are a bit off, as are a couple little things.  But basically, it works.  If you want that map, pm me with your email and I will send you a copy of the AD to EZ  map he sent me....

bapu

sven450
It mostly works, although the velocities are a bit off, as are a couple little things. 

Therein lies the rub. As each drum vendor may not supply the same level of velocity layers at the sample level, a velocity of 90 for AD may sound like a velocity of 72 when played back in EZ. 

I'm even finding kit pieces moved around from note to note amongst the same vendor's kits.  So just making straight up maps for a single vendor is a bigger deal than it should be, IMO. 
 
I'm sure the idea is to make it difficult users to mix-match, which is really too bad for XLN as I have a larger investment TT stuff at this point.
 
Oh well, thanks folks.  AD isn't my reason for upgrading anyway.

teego
I have already made a note name list for AD2 and use it in piano roll view. You have to  right click the keyboard and tell it to use these note names instead and it populates with the drum names. I would be happy to share the list if someone can tell me the best way. I suppose I could just copy the master.ins and put it up somewhere for download because it is the stock one with the ad2 add on.
 

If you don't have a cloud account, I'll share the file online if you email it to me.  I'll PM you an addy to send it to.

me, I wish I could NOT see drum maps in PRV.
At least turn off the little diamond markers and turn them back into lines.