I don't know if this would be useful to those using drum maps but for me as a BFD3 user I would love to see this in the piano roll view.
 
Given that BFD3 doesn't require a drum map and is able to list all it's kit pieces in the piano roll (see pic)
 
http://www.mediafire.com/view/3t6x14gnq85bkjm/Piano_roll_kits_named.jpg#
 
I would love to see a feature in sonars piano roll that is in the BFD3 drum editor and that is to be able to hide unused articulations.
At the top of the BFD3 drum editor is a, "view" button where you can select to either show, "drums" used in groove, or show, "articulations" used in groove. maybe cake could go one better and have the ability to select which drums and articulations you want to add or remove from the view individually.
 
I know this wouldn't be much use to those using drum maps as they can kind of do that already but would be great for me
 
 
Steve
 
 

twaddle, of course as a BFD3 user, I really like this, would get rid of much clutter when trying to do drum editing in PRV. Don't see it getting much traction however, since Cakewalk is more likely to do enhancements for Addictive drums which they have partnership with. (I'm not very familiar with Addictive drums, and whether it comes with preset drum maps . . . since I always use BFD3)
 
Why is it that BFD3 doesn't require creating a drum map ?
You just install, and it appears in PRV set up and ready to go.
Why can't everything be this easy ?
 
I guess it would have to be implemented as hide / unhide various line items from the drum piece listings in PRV, maybe even add colour coding, and just grey out the unused pieces ?

noynekker
Why is it that BFD3 doesn't require creating a drum map ?

Both FXpansion and Cakewalk add the necessary data for VST2.1 opcode effGetMidiKeyName in their drum synths. SONAR makes use of the data if present for PRV note names.

Thanks scook . . . fairly technical, I may have to google to find out what you mean, but I always appreciate your depth of knowledge here on the forum . . . I think you're saying that Sonar and BFD3 talk the same language as far as midi note naming, so it may be just great programming, and worth paying extra for.

There is a function in the VST spec called effGetMidiKeyName  which provides a way for plug-ins to supply names for MIDI notes. FXpansion and Cakewalk add data in their drum synth programs to support the function. Other vendors like XLN and Toontrack do not. SONAR calls the function when the plug-in in added to the project. If the plug-in returns data, it is used to name the PRV keys.