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?

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).

Thanks b rock.  I'll have to look into the virtual midi cables.  I just remembered, I use automation on a fair amount of busses, which may be a problem because they can't contain midi events, correct?  
 
I don't suppose there are any conversion programs or formats that handle automation well for porting to different DAW's?

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.

I have always kept Sonar set to force the channel number in the Track Out regardless of what is in the Event List, and that is fine for external synths; however, for some soft synths, or to fix the lane problem described above, I agree that Find/Change is a simple fix.