Hi,
 
it looks like it's not possible to store a controller automation in a MIDI clip so that it is being played by the Matrix. The only clip automation option for MIDI clips is velocity. Am I missing something or is there another way to control the modulation, for example, from a MIDI clip being played in the Matrix?
 
Thanks!

If I understand you right, you are looking for editing controllers in MIDI clips:
http://www.cakewalk.com/Documentation?product=SONAR%20X3&language=3&help=EditingMIDI.20.html#1083369
 

azslow3
If I understand you right, you are looking for editing controllers in MIDI clips:
http://www.cakewalk.com/Documentation?product=SONAR%20X3&language=3&help=EditingMIDI.20.html#1083369

Yes, but I don't see a way to add the controller data specifically to a clip. I know how to add controller data to a track, but it appears to remain independent of the clip.
 
For example after adding controller data and then moving the clip, the controller data does not move with the clip. In the same vein, moving the clip to Matrix does not move the controller change with the clip. The clip being played from the Matrix does not affect the controller.
 
I am looking to hook the controller data to the clip, so that whatever I do with the clip, it keeps the controller changes relative to the clip.

May be you are (or I am in attempt to understand you) mixing different things:

• CC data (along with Notes and other MIDI types) are called MIDI clip. So MIDI clip is composed from MIDI events, some of which can be controller data. If you move the clip around (also to the Matrix) these events are also transfered (it will be a kind of nothing to transfer otherwise).
• Clip automations are also attached to the clip. There are a bit hard to use in SONAR and from my knowledge have no sense for MIDI clips.
• Track automations. That (not MIDI) data are attached to the track, not clips. But these data can be copied with clip (see "Special copy" options) and so also pasted into the content which support that (track). Matrix is not a track, so it has no track automation and so these data are not applied.

Please note, that depending on VSTi and parameter you can sometimes achieve the same effect either by track automation or by MIDI CC on its input. For the Matrix view it make sense to use the second approach. If nothing else works, you still can simple render the MIDI clip into audio with all automations applied and put the result into the Matrix.

i believe i read that matrix clips don;t support CC data, maybe someone from cakewalk can clarify?

lawp
i believe i read that matrix clips don;t support CC data, maybe someone from cakewalk can clarify?

That will imply that normal piano MIDI music will not work in Matrix (since sustain is CC 64). So, CC in MIDI clips are working in Matrix. Just to be sure, I have just checked that within X2.
 
I have also checked that "MIDI Learn" inside VST works with hand made CC data and the result works as expected from the Matrix.

ok my bad, sorry for any confusion, we do need a baker to chip in and clarify

If you are recording the clip in the midi track, and record CC afterwards on top, try selecting all data and apply Bounce to Clip before moving the clip to the Matrix.

Recording CC data works and is retained in the Matrix. I wasn't clear on the distinction between track automation and CC data recorded as track events.
 
Another thing that confused me is that I was unable to draw CC data in the piano roll. It only added data for each note event. However after recording the twiddling of the knobs, there is tons of CC data in between notes showing up in the piano roll view.
 
Now after some experimenting it looks like the snap grid was the reason I could not freely draw CC data. Turned it off and now all is well.
 
Thanks to everyone who responded!