I've been recording several MIDI takes on my trombone track. Each time I record midi notes it creates a new take lane. As a result, creating 2 mod wheel CC 1 lanes in PRV and 2 CC64 Sustain in PRV. I'm not sure exactly how to repro since I've been consolidating midi clips throughout the recording to eliminate all of the unnecessary track lanes in Track view.
 
I've deleted all of the extraneous track lanes in track view and consolidated all of the midi notes to one lane. But in PRV I still see 2 CC1 and two CC64.  And I just recorded another Mod wheel pass and it created yet another envelope lane in PRV.
 
so i have now all of these envelopes open for one track. 
Velocity
CC1 Mod (chan. 5)
CC 1 Mod (Chan. 11)
CC 64 Pedal (Chan. 1)
CC 64 Pedal (Chan 5)
CC 1 Mod (chad 3)
 
1. How do I consolidate these envelope lanes in PRV?  
2. Is it possible to not create a new take lane every time I make a new MIDI recording on a track?
 
 I realize this can be helpful to have a Mod wheel pass recorded on a seperate lane so you can modify it seperate from the notes. However, SONAR is creating multiple lanes for these controllers.  Getting too cluttered and it's slowing down the scrolling in PRV with so many envelopes visiable! 
 
thanks for the insight

AudioMech
so i have now all of these envelopes open for one track. 
Velocity
CC1 Mod (chan. 5)
CC 1 Mod (Chan. 11)
CC 64 Pedal (Chan. 1)
CC 64 Pedal (Chan 5)
CC 1 Mod (chad 3)
 
1. How do I consolidate these envelope lanes in PRV?  

 
1. Select the whole track.
2. Click Process > Find/Change.
3. Click OK once, change the value in the Max field under "All Non-Special Events" to "1," then click OK again.
 
 

AudioMech
2. Is it possible to not create a new take lane every time I make a new MIDI recording on a track?
 

 
Sonar creates a new lane when the new take overlaps with the existing take. If you don't like it, vote here:
http://forum.cakewalk.com/Auto-merge-of-Midi-when-loop-recording-m3147500.aspx
 

icontakt
 
1. Select the whole track.
2. Click Process > Find/Change.
3. Click OK once, change the value in the Max field under "All Non-Special Events" to "1," then click OK again.
 
 
 

Thanks for the reply!  I tried this and there are still multiple channels of modulation and sustain. Not sure how to proceed. 
 
 

Strange. That should work, unless the clips are locked.

Do you have other tracks selected in the PRV? The controller pane will show a lane for every controller type and channel present in the PRV track selection. But, regardless of what track they are actually on, in order to get controllers on multiple channels by recording, you must be changing output channels on your MIDI controller. Or you've bounced some clips with a forced MIDI channel enabled on the track which will re-write the event channel. This has been a hot topic lately, though it's a longstanding behavior.

brundlefly
Do you have other tracks selected in the PRV? The controller pane will show a lane for every controller type and channel present in the PRV track selection. But, regardless of what track they are actually on, in order to get controllers on multiple channels by recording, you must be changing output channels on your MIDI controller. Or you've bounced some clips with a forced MIDI channel enabled on the track which will re-write the event channel. This has been a hot topic lately, though it's a longstanding behavior.

Thanks @brundlefly. I've tested this with only one midi track selected in PRV (but yes, if multiple midi tracks are selected then I get all of the controllers for each midi track). In this example (noted above) it is for one single midi track. I haven't changed output channels on my midi controller. But I am using a M-Audio Oxygen 49 for Mod wheel input as well as a Korg Triton for playing keys in. So many the 2 midi controllers are causing this excess of controller "tracks"?  

In regards to bouncing clips with a forced MIDI channel enabled, I have bounced some clips (because every time I record an edit to a phrase it creates a new take lane (which is super annoying). So as a result I'm consolidating clips and maybe that is creating multiple controller channels? 

How do I (or is there a way) to avoid creating multiple controller channels when recording new controller takes? Like if I want to add a mod wheel pass to a synth line. then make an edit to that mod wheel pass and record another pass? Currently, SONAR will create another controller channel and "track" in the envelope section below the piano roll.  
 
This just gets really annoying because now I have a mod wheel recording on one channel in one section and in another section it's on another channel. So I have 5-6 envelopes open for Velocity, Sustain, and Mod. Wheel. Where I only should have 3.  

I think your M-Audio controller must be changing channels somehow or some other process is rewriting event channels somewhere between your controller and SONAR. SONAR just records what it receives, and if the channel doesn't change, you should only ever get one controller lane per controller type.
 
BTW, it appears the Bakers have responded to complaints, and Bounce to Clips no longer writes the forced MIDI channel to events in the Dorchester release unless you set RechannelMIDI=1 in Cakewalk.ini. 

brundlefly
I think your M-Audio controller must be changing channels somehow or some other process is rewriting event channels somewhere between your controller and SONAR. SONAR just records what it receives, and if the channel doesn't change, you should only ever get one controller lane per controller type.
 
BTW, it appears the Bakers have responded to complaints, and Bounce to Clips no longer writes the forced MIDI channel to events in the Dorchester release unless you set RechannelMIDI=1 in Cakewalk.ini. 

hmm, I'll experiment using other midi controllers to input Mod. wheel and see what happens. Still doesn't explain why my sustain pedal is also recording data on multiple channels as well.  

AudioMech
Still doesn't explain why my sustain pedal is also recording data on multiple channels as well.  

The pedal itself is just an on/off switch (unless it's a continuous type). In any case, it's the controller to which it's connected that generates the CC messages and determines the channel. And there still the possibility I mentioned that something is translating messages before SONAR gets them.