I owe Jerry a favour, so I've created an example song file that demonstrates the technique he mentioned so you can evaluate it.
The following zip contains a song file called TSCTL.SNG
http://daz.korgforums.com/misc/tsctl.zip
It contains a single song. The first four tracks are all assigned to MIDI channel 1 and all have their Status set to INT (i.e. enabled), so if you hit a key all 4 tracks' Programs will sound. All the other tracks/timbres are disabled (Status = Off), except Track 16 which I am using for the RPPR routing.
Jerry had suggested the following :
You could also play your Combi in Sequencer Mode, record the Sys Ex control of the Timbre Status parameter (from INT to OFF) into a Pattern and then map that Pattern to RPPR, and even to one of the Pads to achieve this...
In keeping with that, I created 8 RPPR patterns each of which contains a sysex message to change the Status of a particular track to on or off (INT or OFF). I named the patterns so it is clear what each does ('trk1 on', 'trk3 off' etc.). I then assigned each of those patterns to the 8 keys starting at F7, and configured the 8 pads to play those 8 notes so you have the following actions assigned to each pad :
Pad 1 : Enables Track 1
Pad 2 : Enables Track 2
Pad 3 : Enables Track 3
Pad 4 : Enables Track 4
Pad 5 : Disables Track 1
Pad 6 : Disables Track 2
Pad 7 : Disables Track 3
Pad 8 : Disables Track 4
Feel free to change the notes (and thus patterns) assigned to the pads. You can trigger more than one pattern using a single pad by assigning multiple notes.
====
Let me tell you how I created the Sysex Message that is used by the patterns, 'cos it was a little fiddly.
Firstly I did as Jerry suggested and explored the 'Create Excl Data' page menu option, but found that whilst it can create an amazing number of different automation events (very cool M3XP feature!) it won't create an event to control Track/Timbre Status. So I created a different sysex message type and used the BIN EDIT feature in the event editor to tweak that to the message I wanted.
The sysex message required looks like this :
F0 42 30 75 41 04 00
23
00 03 00 00 00 00
01 F7
The last digit on the first row (23) is used to determine the track whose Status will be changed (23=track 1, 24=track2, 25=track3 etc.) and the second to last digit in the second row is the Status value (0=Off, 1=INT)
I've left my template sysex message in Track 1, so you can easily edit it to give you the function you need and then pull the message into a pattern using the Get From Track page menu option. That is how I created the 8 different patterns/messages myself.
Enjoy,
Daz.