Bah! Could someone please quickly tell me where to find the CC#s in SD3?

Okay. tl;dr... I just need to see the CC#s for the separate kit pieces. I know it's dumb I just can't figure out where they are.

You have to insert a softsynth with a drumkit. For example, the TTS-1. 
Go to the MIDI track and set the TTS-1 as the output
Set the bank to the Preset Rhythm Bank and select a drum kit as the patch, i.e., Room Kit
Open the Piano Roll view. 
You should see the drum names in the PRV at the top. If not you have to adjust the size of the pane. 

daveny5


You have to insert a softsynth with a drumkit. For example, the TTS-1. 
Go to the MIDI track and set the TTS-1 as the output
Set the bank to the Preset Rhythm Bank and select a drum kit as the patch, i.e., Room Kit
Open the Piano Roll view. 
You should see the drum names in the PRV at the top. If not you have to adjust the size of the pane. 

?????????????????????????????????????????????????????????
 
What post are YOU  (people) responding to? What on earth does this have to do with controlling a softsynth using an external controller via CC messages? Ya lost me...

What CC#s are you referring to, i.e., volume, expression, note bend, etc...?

@daveny5... Just the notes for now and I checked out the PRV like you said. I can indeed see all the kit pieces but there just aren't any CC#s there. I just want to be able to view them so I can create a "Scene" on my pK. Right now I am essentially just scrolling through the note numbers on the pK until I a) see that I am triggering the correct piece on SD3s GUI and b) figuring out which of two possible sounds I want to use. It is very laborious and I'd prefer another method. As I said though it will do for tonight but any suggestions as to how I can do this more efficiently would be great. Such a silly simple thing but it just isn't working the way I want. I found the CC# chart in the SD3 help topics but the darned things are WAY off from how the pK is translating them (ie: what should be the snare comes up as a cymbal or a gorilla fart). It's pretty annoying. It is however my own lack of knowledge so I'll learn... goshdarnitalltoheck I WILL LEARN!!! Thanks again guys. You rule.

And that is obviously what I am missing here. However when I go to change the kit piece each pad controls the pK only allows me to scroll through CC#s. Not the 1-127 numbers. Anyway, I'm gonna just keep working this way for tonight and see how far I can get. Keep the ideas coming though. It is more than appreciated. Cheers!

@Stoons... "MIDI note number 36 corresponds to C3 for example., which will trigger the kick sound." Okay now we're getting somewhere. I need to see which MIDI note number will correspond with which key value I guess. Sorry I though those letter notes were called CC#s. As you can see I am still very much muddling my way through all this MIDI wackiness. Ugh. Just smashing drums and plonking my gueetar is so much simpler. :-( Thank you for the help.

Beepster


@Stoons... "MIDI note number 36 corresponds to C3 for example., which will trigger the kick sound." Okay now we're getting somewhere. I need to see which MIDI note number will correspond with which key value I guess. Sorry I though those letter notes were called CC#s. As you can see I am still very much muddling my way through all this MIDI wackiness. Ugh. Just smashing drums and plonking my gueetar is so much simpler. :-( Thank you for the help.

There are charts all over the net which will give MIDI note numbers and tell you the corresponding note name eg. 37=C#3. Just download one. Oh well, growing pains but you're slowly getting where you want to go.

Beepster


Yeah... I really thought it worked the way I described but obviously I am again missing an element. I'll look up the charts and I thank you again. Growing pains indeed. I will not let this shiny light box out smart me though! NO SURRENDER!!!

Well, it doesn't work the way you described, simple as that :-). CC# are used to control specific parameters like breath controller, pitch bend, envelope release, chorus depth etc. Pretty much anything except the actual musical data, MIDI Note data. MIDI Note data are things like which note, how much velocity, duration etc.
 
Midi note value is seperate from CC data.
Select a MIDi track and go to Process>Interpolate. You will see "Note" and then the relevant data that can correspond to note data.Then under you will see Control etc. These are the main categories of MIDI data.
 
http://en.wikipedia.org/wiki/MIDI
 
Read the section called "Messages" as an overview.

Well, my question would be why even be arsed with the step sequencer? Why bother? What is it offering you as opposed to just hitting record and playing in the groove you want? In my opinion it's an unneccesary "step" and the thing is friggin' limited. You want robotic rhythms? Why?

Beepster


Had to tear everything down for the night. Sorry for the delayed response. I actually have had some really good results with my very limited experiments with the step sequencer in regards to realism. I just went in and drew in velocities and stuff by hand but those were on beats I programmed in just by clicking on the buttons with my mouse. I wanted to duplicate that except live with the pK and while the Sequencer was playing. Seems like it would be a lot easier to get things done and get the rhythms I wanted as I used to play drums. I probably would have done just a hi hat to get the timing going then played kick AND snare on the second pass then whatever frills on the third pass. I also wanted to drag the sequencer out so I could create more elaborate stuff. I know what I want to do is more suited to PRV but that is even more confusing. I just thought I'd start simple and work my way up. Isn't this the type of thing DJs and electronica musicians do all the time? I'm obviously missing something AGAIN. I'll figure it out. I'm just disappointed I couldn't get this happening tonight. But you guys taught me a bunch of useful stuff I needed to know so I'll be happy with that. If anyone knows how to do what I'm talking about I'd love your input. I got SOOOO close but not close enough.

First off, open the Session Drummer manual. Go to the Index tab, down to Drum Kit and look at MIDI Note Numbers. It details every possible stock drum hit option, what MIDI number and each corresponding name. If you already found this then never mind.
 
Now as for the step sequencer...DUMP IT! OK, just my opinion but bear with me. Pick a MIDI track. Route it to Session Drummer. Select 4 measures. Set it to Loop Record over this 4 bar section. Arm it. Hit record. Now as it records it will loop and you can start adding stuff. For example, play in your kick first or kick and snare. As it loops add in hats, cymbals, whatever. If you don`t like it, stop, Ctrl-z and try again. If you have the Metronome enabled while recording there is no need to add or record a click as you were suggesting for the step sequencer. If the rhythm you end up with is good but the timing is too off, quantize or groove quantize it. Open up the PRV and look at it. If you click on the left pane where it says Snare it will highlight only the snare hits. Now you see the snare velocities but no other velocities in the Controller pane of the PRV (depending on how you have it set up) which makes them easier to adjust. I don`t know if X1 continues the tradition of D is Draw tool, S is Select etc. but if those tools are still valid use Select to drag notes around and Draw to add notes, although you likely know these new smart tools better than me in X1 so...have fun.
 
Anyways, I`m sure the step seq has some good qualities but ùnless your goal is mostly techno stuff then you should learn the basics of editing this way. It is exceptionally quick, easy, very `visible`and intuitive once you understand it, and these tools will serve you for all other instrumentation as well - keyboards, bass, whatever. Dive in, man!

No worries, hope it helps.
 
As for notes not matching up, check to see if it is an issue of -octave- assignment. Some manufactures use a different note for middle C such as C4 or C5. Very easy to adjust if that is the case.

Beepster


That is exactly what it

Well, if that is what it is  (geez, now I confuse myself) then just go to the Key+- option of the MIDI track and set it to 12 (up an octave) or -12 (down an octave) to sort it out instead of screwing with the pK - let Sonar do it internally instead of messing with that thing. Once you sort that out I think you can set a global option to compensate. Good news is, once you have it sorted out your workflow will be much easier.