What is the best way to clean up Midi Event Channel numbers?

I used the Find/Change which was very fast. 

BrundleFly - I'm not certain about this - I am assuming if I have midi events on a track where the track is set to send out info on a certain channel, that the track channel overrides whatever channel the midi event is.  Is this correct?  I'm changing all events to channel 1 just to keep it easy.  But maybe I'm mistaken?

Thanks John.  Are you sure about that?  I've got note events with channel 1 in a track that is routed to channel 3, and these notes are going correctly to the instrument in Vienna Ensemble that is receiving on channel 3.  And when I draw a note in this track and check the note in the event list, it has channel 1.  Is it different between note events and controller events?

If it didn't work a type 0 file wouldn't work either.

Having wrestled many a midi file, I see this kind of thing all the time. It's basically that type 1 midi files can have multiple tracks, but channel numbers are hard-coded within midi data (Which is why type 0 midi files can work multichannel). You can have controllers for channel 10 in track one, or vice-versa, it's all legal. I find that most of these come from keyboard workstations - Composition there appears to be important, but not necessarily an elegant data stream.
 
It's a pain to sort out. Many times I just convert the embedded midi controls to automation lanes (to the appropriate track), so I can further modify it.
 
BTW, automation and embedded midi controls are not mutually exclusive; they are both active simultaneously and you can easily trip over your own feet if not careful. That's probably the number one reason to convert them to automation.
 
 
 
 

But now I'm wondering if you can convert Sonar's automation to MIDI events so that you could port a project over to another DAW?

 
I've always used a virtual MIDI cable for that (Maple MIDI for 32-bit; LoopBe1 is 64-bit).  Two MIDI tracks; the first plays back the automation curve, the second records it as MIDI.  The drawing tool variations really come in handy here with this kind of conversion technique.
 
Automation (MIDI) Track:  Input N/A.  Output set to virtual MIDI cable.
MIDI Record (MIDI) Track: Input set to virtual MIDI cable.  Output N/A.  Arm for recording.
 
As for your original question, Bounce To Clip(s) - with a forced / redirected MIDI Channel dialed in - will convert all of your various MIDI Channel-ized tracks to the forced channel.  If I recall this correctly, it will also force all MIDI notes to that specific MIDI channel.  Selections are ignored.  None / Omni preserves channelization on the Bounce (see brundlefly).

guitartrek
SuperG - Thats interesting.  I've never converted midi controller events to automation.  But I was thinking my existing Sonar automation prevents me from porting a project from Sonar to for example Logic, because Sonar's automation is totally different from another DAW's automation.  But now I'm wondering if you can convert Sonar's automation to MIDI events so that you could port a project over to another DAW?

The one sure-fire way to get lane automation over to another Daw is to save the project as a midi file. The automation lanes will be saved as midi-control messages. Obviously, this won't help with the audio tracks, but you can easily import those manually into another Daw - just be sure to bounce them out with any effects you need first.