Well... I definitely wouldn't want to leave the midi output at none, because it wouldn't go to the right instrument on my synth. :) That particular channel I used in the video example drives the basses in my orchestral soft synth, and I do a lot of orchestral mockup.
I agree that it isn't really illogical behavior. However, it's an annoyance that I don't see a way around.
The way all my synths work, it doesn't matter if the note/CC data is channel 1 or channel 16: if it's in a track that's sent out to channel X of my softsynth, channel X will respond to it. Synth behavior wise it's not a problem. Navigating and editing my MIDI data, well, it's pretty annoying.
Maybe the thing is I'm actually not using bounce to clip the way it's supposed to be used for MIDI data. If there is a way I'm supposed to use it, please let me know.
As it is, if I'm using bounce to clip at any point with my various tracks, I have to constantly close and reopen CC tracks in order to see my data, because the PRV view doesn't change when opening up different clips. Also, I have cases where in one track, I'll have to open up multiple lanes of what is ostensibly the same data (modulation, expression, attack, etc.) because some stuff has been bounced to clip and others haven't.
I guess another question is, if I (begrudgingly) agree that this isn't illogical behavior: Is there a way to clean up and combine clips of MIDI data in a way that preserves the channel that data was recorded over? The way I see it, bounce to clip is the way of combining multiple clips of MIDI data into one clip, but it's also changing my MIDI data. I want my MIDI data simply combined/grouped together, not changed. I just want to clean up things for easier handling, so I can arrange things and move stuff between various tracks more easily.
post edited by sklathill - 2013/02/13 14:29:07