I will say this again. Step Sequencer does NOT play well with drum maps, AND Cakewalk technical support advised me that it is NOT intended to be used with drum maps.
This is despite some of the Sonar videos, help documentation, and even the Sonar X2 Power book explaining how drum maps can be used with Step Sequencer. Yes, clips can be created with them, BUT, once editing is attempted, sometimes things work, and sometimes they don't, and the nature of weirdness changes all the while.
I had LOADS of problems when trying to open clips for editing
, when the clips were created in Step Sequencer with a drum map assigned to the midi track.
Weird things began happening in an inconsistent fashion, and the final word on it from Cakewalk technical support is to NOT use drum maps with Step Sequencer. Sometimes notes would not display. Sometimes the wrong clip would open, meaning I would double-click on one clip, but a vastly different one would open up. Things like that, and more.
The workaround for ME, as I had already created all of these clips, was to bounce them all to a midi track, which breaks the association between those clips and Step Sequencer. Then everything was OK.
The lesson for ME there was to avoid creating future clips in Step Sequencer using drum maps. This was after lots and lots of frustration and trying lots of different things, only to come back to that being the reality.
So now, I keep a cheat sheet I built in Word, with a document containing a table of Kit Piece Names, Note Names, and Note Numbers, that I now use to enter drum events in Step Sequencer. It works, and until they change the current functionality of Step Sequencer, that's just the way it is.
Bob Bone