Thanks for posting the link to the Gearslutz discussion; for what its worth I will post a link to the 2014 thread here--just in case someone else finds it there and is interested in the continuation of the discussion.
Also thanks for helping to confirm that even though I no longer have* the ability to recall specific conversations I have had here [*I used to be able to remember them and locate them!], at least my reconstruction of similar circumstances lead to consistent conclusions. :-)
A few words about RECHANNELIZE INPUT. So far as I can tell, that function only controls whether or not incoming midi data going to a single specific track ("To Track Dest.") gets converted to the midi channel that matches the track you are recording on. With this function set to "off" my 4 midi channels of data coming from SONAR were recorded onto Track 1 corresponding to midi channels 1 through 4. With the function set to "always" or "on record" all 4 channels of midi data were forced to C01A (corresponding with Track 1--the Dest. track.)
As for the MIDI ENABLE parameter, so far as I can tell, that won't help with filtering incoming midi data going to the sequencer. It does do the other thing.
Well, I hope this helps.
Steve"
-----------------------------
From my 2014 post here (with a few typos corrected and a few lines now emphasized):
"I just ran some tests that confirmed what I expected. Basically, I created a short 4 track thing in SONAR (on midi tracks 1 through 4) and played it into my P2500. I tried various combinations of settings within the P2500 (rechannelize, channel assign destination, and midi enable). I have not actively recorded tracks on the E-Mu sequencer in years, so it took a while to relearn what does what. So far as I can tell, the E-Mu sequencer (CS or P2500) will not filter out incoming data based on midi channel. I was successful, however, with my trusted parallel port motu midi express - an 8 x 8 midi router. In fact, it was relatively easy to only allow data from one midi channel to go into the P2500.
A few words about RECHANNELIZE INPUT. So far as I can tell, that function only controls whether or not incoming midi data going to a single specific track ("To Track Dest.") gets converted to the midi channel that matches the track you are recording on. With this function set to "off" my 4 midi channels of data coming from SONAR were recorded onto Track 1 corresponding to midi channels 1 through 4. With the function set to "always" or "on record" all 4 channels of midi data were forced to C01A (corresponding with Track 1--the Dest. track.)
As for the MIDI ENABLE parameter, so far as I can tell, that won't help with filtering incoming midi data going to the sequencer. It does do the other thing.
Well, I hope this helps.
Steve"