I think rechannelize off then explode will do his bidding.
I am having a hard time with this. I must be missing something. On the surface it sounds like simply dubbing from one sequencer to another. If that's the case why not simply export a midi file from sequencer 1 and upload it to sequencer 2?
I am guessing there is something more. Hmmmmm.
Let me ask: If I would hook a midi keyboard into my P2500 and play sounds on an external module in record mode on the P2500 such that I periodically change the midi channel of the keyboard, does that come close to what you want to do (although I would be playing one channel at a time because I am not setup to play 16 channels at the same time)?
It seems to me that by the time I start sending midi data on channel 16 (if it works), I will have a 15 channel track (still in record mode) playing 15 channels (that I just recorded) on external gear, and once I add data on channel 16 and press stop, I will have recorded a single 16 channel track that will play 16 channels on my external gear all from one track.
So far as I can see, that is what you want--except that I am do it serially. I suppose if I have 16 pairs of hands, 16 keyboards, and a 16 channel midi merger, I could do it in parallel--to simulate going from one sequencer to another.
Hmmmm. Maybe I figured out the missing link--possibly: Are you wanting to use the track mute buttons to turn different midi channels on and off going to the external gear? If that's part of the equation, I doubt it can be done since the buttons function as >>track<< mutes, not channel mutes.
I think you could use the knobs in volume mode to bring channels in and out. Or you could have a device with 16 buttons in the midi flow that use the expression CC as kind on an on/off switch.
Anyhow, I am curious to know what the performance goal is.
Steve