Hey all,
Thanks so much for all your help with all my MIDI questions, it's really helping me learn and get better at it! One quick thing, I have been using a MIDI controller and I want to have all the voices except 1 be controlled through the controller with a number of the combi's I am working with. That last sound will stay on the Korg only. I can do this by sending every voice to the MIDI controller's transmit channel, and the last one set to the global MIDI channel of the Korg, but is there a quicker way? Since I want to do it with a number of combi's, it would be easier if there were some way I could just have the default be to be sent to the MIDI controller, and the 1 voice in the combi that I would want on the Korg I would just select another channel not associated with the controller.
It seems like a simple thing, sorry for the very wordy post, I thought I would be able to emplain what I wanted quicker than that!
Easily transmit all sounds in a combi to MIDI controller
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
Anyone at all have any thoughts on quickly doing this? I am fearing by the lack of response that the only way to do this is to send every voice except 1 to the controller, but I was really hoping for an easy way to only keep 1 voice with the kronos, and all the other voices controlled by Tue controller.
I really see no easy way to do this. Many of the Timbres in the Combi are assigned to Global Channel. Therefore, no matter which Global MIDI Channel you set, the Combis will still be controlled locally.
So, the only chance to reduce a bit the required work is to heavily transpose the note ranges for the sound you want to play locally. For example you transpose the whole keyboard to play from C7-C12, then for the Timbre you want to play locally, modify the range to match C7-C12 and at the same time you transpose the Timbre downwards so it will play on your desired range.
At least, this solution involves editing just one Timbre... If and only if the rest of the Timbres have no open note range...
BTW, in this case, both the external controller and Kronos are set to the same MIDI Global Channel
So, the only chance to reduce a bit the required work is to heavily transpose the note ranges for the sound you want to play locally. For example you transpose the whole keyboard to play from C7-C12, then for the Timbre you want to play locally, modify the range to match C7-C12 and at the same time you transpose the Timbre downwards so it will play on your desired range.
At least, this solution involves editing just one Timbre... If and only if the rest of the Timbres have no open note range...
BTW, in this case, both the external controller and Kronos are set to the same MIDI Global Channel
Current gear: 
Access Virus TI2 Whiteout Keyboard (111/150), Access Virus TI2 Polar DarkStar Special Edition, Gibson Custom Lite 2013, Roland MV-8800 
Access Virus TI2 Whiteout Keyboard (111/150), Access Virus TI2 Polar DarkStar Special Edition, Gibson Custom Lite 2013, Roland MV-8800 
not to be a pain but......... 
Don't you mean the MIDI controller does the sending and the Kronos does the receiving of the MIDI signal.
Other than that, it sound like you have a solution, but you'll have to configure the Combi MIDI, for each Combi you want this type of performance on.
sorry I did not have a real answer to your question, I'll have to look it up in the manual(s).
good luck and you've convinced me that I need a MIDI Controller keyboard, I can dedicate to the Kronos
Don't you mean the MIDI controller does the sending and the Kronos does the receiving of the MIDI signal.
Other than that, it sound like you have a solution, but you'll have to configure the Combi MIDI, for each Combi you want this type of performance on.
sorry I did not have a real answer to your question, I'll have to look it up in the manual(s).
good luck and you've convinced me that I need a MIDI Controller keyboard, I can dedicate to the Kronos
Kronos-6, Krome, M3, Radias, KingKorg, microKorg, KP-2, KP-3, KO-1, KO-1 PRO, Karma, microX, monotron, monotribe, PadCONTROL, Wavedrum Mini, Volca Keys, Beats, Bass, Sample, monotron Duo & Delay, microArranger, M1, Wavestation, Volca Sample, Keys, Beats & Bass, MS-20
JD-XA, JD-Xi, Aira (system 1, TB3, TR8, MX-1), Prophet 12, Mopho X4, Jupiter-80, FA-06, D50, CS1x, CZ101, DX200, AN200, analogFOUR, MachineDrum, MonoMachine, Motif XF6, Virus Snow, Nord Lead 2X, OP-1, MFOS, Tenori-on, QY100, QY70, meeblip se, miniBrute, microBrute, Bass Station 2
JD-XA, JD-Xi, Aira (system 1, TB3, TR8, MX-1), Prophet 12, Mopho X4, Jupiter-80, FA-06, D50, CS1x, CZ101, DX200, AN200, analogFOUR, MachineDrum, MonoMachine, Motif XF6, Virus Snow, Nord Lead 2X, OP-1, MFOS, Tenori-on, QY100, QY70, meeblip se, miniBrute, microBrute, Bass Station 2
The simple answer is that you can't send voices/sounds from any synth or workstation to a midi controller. The voices/sounds/programs/patchs stay on the synth/workstation. The midi controller sends midi events like "note C3 on with velocity 127 to midi channel 3" to the midi receiver, which responds by playing whatever sound for C3 with velocity 127 that has been assigned to midi channel 3. The sound produced by the receiver is sent to its normal audio outputs assigned to the program on midi channel 3.
Midi normally deals with metadata - like an electronic version of a musical score. That's the simple version.
The advanced answer is that midi also allows for proprietary commands unique to each device through system exclusive (sysex) commands, and some devices allow programs/sounds/patchs to be loaded and retrieved via sysex, but only editor software or compatible keyboards can do anything with that data. A general midi controller has no programming to understand the sysex for programs/patchs of synths. So programs/sounds can be sent via midi, but only to software/hardware that knows how to do it for each device, and every device can have different sysex for how that is done. There's no standard for how this data is sent via sysex, since sysex and midi itself was designed a long time ago, before there were software editors and programs to be transmitted to/from music gear. Sysex was defined to be able to send data stuff that wasn't defined at the time. Unfortunately, midi hasn't been replaced with any standard ways to send/receive programs, nor is there any standard way to translate programs between different kinds of gear that can communicate with each other.
Midi normally deals with metadata - like an electronic version of a musical score. That's the simple version.
The advanced answer is that midi also allows for proprietary commands unique to each device through system exclusive (sysex) commands, and some devices allow programs/sounds/patchs to be loaded and retrieved via sysex, but only editor software or compatible keyboards can do anything with that data. A general midi controller has no programming to understand the sysex for programs/patchs of synths. So programs/sounds can be sent via midi, but only to software/hardware that knows how to do it for each device, and every device can have different sysex for how that is done. There's no standard for how this data is sent via sysex, since sysex and midi itself was designed a long time ago, before there were software editors and programs to be transmitted to/from music gear. Sysex was defined to be able to send data stuff that wasn't defined at the time. Unfortunately, midi hasn't been replaced with any standard ways to send/receive programs, nor is there any standard way to translate programs between different kinds of gear that can communicate with each other.