As a somewhat unrelated aside to your actual question, I feel strongly that the drum map view makes it much easier to understand the layout of your recorded drum midi than the standard piano roll view.  While my vieo will have little help for you in recording your individual midi part-at-a-time method, it might make it easier to look at once you've done it.  Check out the drum map video here:  http://blades85.com/music/sonar/88-specific-topics/79-sonar-drum-maps
 
Bitflipper's advice is certainly the key: make sure you have sound-on-sound mode enabled for your recordings so that you don't mow down your previously recorded bits.
 
Hope this helps.

WUTP
Sorry, I did not understand you.
I am in the Piano Roll View.
I've left-clicked with the mouse on the Hi-hat key (ClsHat). It highlighted the whole line.
Next, I've hold the shift key on the computer keyboard and tried to move the hi-hat notes.
Nothing happened. Another failure.
 

You may be having difficulty with the 'smart' tool (the one shaped like a star). When using the smart tool the mouse pointer icon will change as you hover over different areas of a note. The 'move' tool is the one that looks like a 4-way arrow. Hover until you have the move tool or actually select the move tool in the control bar.
 
By the way, you don't NEED to use the shift key, I just think it makes it much easier and faster.
 
 

WUTP
I am in the Piano Roll View.
I've left-clicked with the mouse on the Hi-hat key (ClsHat). It highlighted the whole line.
Next, I've hold the shift key on the computer keyboard and tried to move the hi-hat notes.
Nothing happened. Another failure.

Step sequencer clip events are visible in the PRV, but can't be edited there.
 
The note timing is all determined by the Step Sequencer settings. If swing  is 50, and Time+/- is 0, PRV timing should match the Step Sequencer.

This is probably not the issue, but could it be possible that you have a 1/8 note worth of audio latency?  What are you using for a sound card and how is it hooked up to your speakers?  Are you using the internal card on a laptop/PC or a dedicated device?
 
Glen

brundlefly
Step sequencer clip events are visible in the PRV, but can't be edited there.

Thanks. That was my problem.
I've moved my notes in the Clips Pane (Tracks View).

gcolbert
This is probably not the issue, but could it be possible that you have a 1/8 note worth of audio latency?  What are you using for a sound card and how is it hooked up to your speakers?  Are you using the internal card on a laptop/PC or a dedicated device?
 
Glen

I'm using the PreSonus AudioBox USB. It's a cheap Audio card, but until I learn how to use Sonar X3 and what to expect from a good Audio Card, PreSonus is just perfect for me.
Also, I'm using the headphones connected to the PreSonus Audio card.
I've not noticed issues with latency, especially the 8th note latency while trying to record in real-time.
 
P.S. I think the Cakewalk IT specialists should allow us to post small size snapshots with our comments. All other forums for musicians allow it.

Glad you got it sorted, but just to be different, I will tell you that I record all of my drum kit parts initially as a single Midi track. I do this for three reasons:
 
1) I want to see where there are multiple "hits" in time to make sure I'm not creating parts that a human would not be able to play. I still inadvertently fail to catch a stray hi hat or ride hit that occurs at the same time as a tom fill or what have you, but it is easier to see it when it is all together.
 
2) I change the drums a lot and having to remember which midi track is which kit instrument would be a creativity killer.
 
3) It is very easy to move a hit from one kit instrument to another (hi hat -> ride, for example) when I don't have to worry about keeping everything separated.
 
After I'm done, then I split the kit into separate midi tracks using a CAL script, or by hand.
 
Finally, I bounce each kit instrument to separate audio tracks for mixing, with all FX disabled, if there are any.
 
Regards,
Dan
 
 
 

Hey Dan - what you describe is actually a lot of the reason for drum maps in my opinion.  Further, you don't have to ever split them to separate tracks - at least not for any reason I can think of unless you just like having them split, though it doesn't sound like you do.
 
Have you had a chance to take a look at the drum map video I posted above?

Blades
Hey Dan - what you describe is actually a lot of the reason for drum maps in my opinion.  Further, you don't have to ever split them to separate tracks - at least not for any reason I can think of unless you just like having them split, though it doesn't sound like you do.
 
Have you had a chance to take a look at the drum map video I posted above?

Yes, but I haven't played with them yet. I split the tracks because I want the audio for each kit piece to be separate. I generally end up layering two or more snares together, so I bounce the snare, then select a different snare and bounce that. Same thing with the kick. I mix all of the kit pieces separately and feed them all into a drum bus. Generally, I find that compression and EQ settings are different for each drum to get the sound I want. It's more work than mixing in AD2 (or whatever drum VST you are using), but the end result give me a lot more control over how the drums sit in a mix.
 
Regards,
Dan
 

dcumpian
I split the tracks because I want the audio for each kit piece to be separate.

Blades was talking about using a single MIDI track, not audio.
 
I used to run a separate MIDI track for each kit piece so I could easily mix with MIDI velocity back in the the days when the drum sounds came from an external black box. But now that everything's in the DAW, one MIDI track and multiple audio tracks (or mixing inside the synth GUI) is the way to go.
 
The drum map just makes it easier to differentiate drum parts in the PRV by giving the note numbers friendly names. Its other major function is to allow routing different drum parts to different synths/ports from the same track, but few users do that.