Hey gang, I hope this question is in the right section.  I'm running SONAR X3 Studio with Addictive Drums 1.5.7.  I am attempting to compose drum tracks from scratch.  I have the Synth and Instrument track created, and was able to compose drum tracks using the Staff View.  I am now migrating over to the PRV for ease of use.  This works, however I am looking to get the correct drum names on the piano graphic so I don't have to memorize them.  My research on this forum tells me that I don't need a "Drum Map", instead I can use the "Note Names" dialog.  This sort of works, however the drop down box is limited to General MIDI Drums and various Roland and XG drums.  These get drum names happening, but none of them map to the AD drums precisely.  Am I on the right track for getting the correct AD names, and how do you add the correct AD mapping to this dropdown box?  If I'm not on the right track, do I need to get into drum maps?  I see that an AD specific drum map is posted on this forum, which I have not experimented with.  
 
Thanks in advance!

http://forum.cakewalk.com/FindPost/2927516

Wow I don't feel so bad for being confused.  There are two totally different convoluted approaches to this (.ins file versus .map file) that even the CW community is divided over.  So, I went with the .map file approach, and this was my experience:
 
1) xcopy installed the map file that Subjacent wrote to my X3 program folder (didn't get the location right on the first try)
2) Restarted X3
3) Had to convert my instrument track to separate midi/audio tracks and redirect midi out (don't think this can work any other way!)
4) Drum pane works now and has the drum names and shows my MIDI notes.  Oddly, the piano view is still visible under it but the notes are gone...I wonder why that is??  
5) I experimented with Subjacent's template file, but that throws a missing "Console Emulator Bus" plug-in error.  I don't need to go there.
 
Pretty baffling, but I got it to work.  I'm a software engineer with previous Sonar experience, but I think a lot of newbs will be roadkill when they encounter this.  Really this basic drum editing is the first thing a lot of people are going to attempt, and are quickly going to find themselves off in the "hacker domain" just to get a basic environment set up.

I am not sure two ways to get note names in the PRV says anything about the Cakewalk community. It does indicate some flexibility in the software. Drum maps can do much more than create named slots in the Drum Grid Pane. Drum maps can translate incoming notes to other note values, alter velocity information and route output. Drum maps also rename rows in the Step Sequencer. Adding entries to the "Note Names" dialog just renames the keyboard display in the PRV Note Pane.
 
The notes are gone from the Note view in the PRV because they are now shown in the Drum Grid Pane.
 
Subjacent's Addictive Drums package was designed in response to Addictive Drums being bundled with X3 Producer.  The track template appears to included the Console Emulation plug-in. I doubt there was any thought given to users of Cakewalk products which do not include the ProChannel Console emulation plug-ins. It should be a simple matter to save the tracks again into the template to eliminate the error.
 
As indicated in the thread in post #2, it is up to the plug-in vendor to add the information necessary for note names to appear by default in the Note Pane. XLN Audio choose not to provide the data. This leaves it up to the user to decide if note names are needed. Cakewalk provides a choice of how to display note names. Both FXpansion drum synths and Cakewalk's Session Drummer show instrument names in the Note Pane without any extra effort by the user.

Thanks for the info skook.  Yeah as an comparison I created a Session Drummer instrument track.  That was a much better experience!  I can keep my single Instrument Track, don't have to fiddle with drum maps, and the drum names appear immediately in the PRV.  The Drum Pane doesn't work, but frankly I think I prefer the PRV with drum names as an editor over the clunky Drum Pane.  I went with Addictive Drums because I saw it bundled with Producer and assumed the integration would be tight.  It is not.  The Addictive Drums bundle should be flagged by QC as "DO NOT SHIP" until the drum naming task is completed (IMHO).

The Drum Pane is growing on me, I can work with this.  Not being able to solo the drums when you run them through a drum map though...ouch!  I understand this is a known issue.  I will rip this drum map out of this project just as soon as I can find a way.  It really shouldn't even be there, save for this damn drum name workaround.

Modifying the master.ins take a couple of minutes. A cut and paste job using the Addictive Drums Keymap.pdf. The mute bug with drum maps is not big deal when drums are broken out into separate audio tracks.

Yeah I'm going to stay with what I've got working for now.  I see the post regarding the master.ins procedure, but I don't think the instructions are remotely clear or detailed enough for a layman to pull it off.  I've just barely got a handle on X3.