@dougc84: You can decide to make a slot inactive. So actually you could easily go from a 5-slot layout to a 4-slot right now with the present firmware.
The migration problem you mentioned before would persist though.
You could make up 2 kinds of peformances then, 4-slot and 5-slot.
No, that's incorrect. While, yes, you can set up a performance with only 4 active slots... actually, let me give an example.
With all slots active:
Performance #1 uses MIDI Program Changes 1-5 to trigger the individual slots
Performance #2 uses MIDI Program Changes 6-10
If you disable slot #5 on Performance #1, what you end up with is:
Performance #1 uses MIDI Program Changes 1-4
PC #5 now does nothing.
Performance #2 STILL uses MIDI Program Changes 6-10
This causes an issue with any controller that isn't 5 button. More controllers are going to 5-button preset layouts, which doesn't really make any sense (since MIDI spec is base 2 anyway), but whatever - not every MIDI controller is 5-button. If I have a 4-button controller (regardless if it's a POD, Peak, something "vintage," whatever) that has program changes hard-coded into the selectors, what happens with the "disabled slot" is now Bank 2's first button (1, A, whatever it is) is now no longer mapped to anything.
Here's a chart of the incompatibilities, with the 5th slot disabled:
Kemper Performance/Slot |
Kemper MIDI PC |
4-Button Controller Bank |
4-Button Controller Slot (A-D) |
1/1 (enabled) |
1 |
1 |
A |
1/2 (enabled) |
2 |
1 |
B |
1/3 (enabled) |
3 |
1 |
C |
1/4 (enabled) |
4 |
1 |
D |
1/5 (disabled slot) |
n/a |
|
|
2/1 (enabled) |
6 |
2 |
B |
2/2 (enabled) |
7 |
2 |
C |
2/3 (enabled) |
8 |
2 |
D |
2/4 (enabled) |
9 |
3 |
A |
2/5 (disabled) |
n/a |
|
|
3/1 (enabled) |
11 |
3 |
C |
3/2 (enabled) |
12 |
3 |
D |
3/3 (enabled) |
13 |
4 |
A |
3/4 (enabled) |
14 |
4 |
B |
3/5 (disabled) |
n/a |
|
|
If you can't see the issue offhand, performance 1 spans the controller's 1A-1D slots. Great! But, performance 2 now uses 2B-3A. Awkward. You now have to switch banks for that particular performance. Even worse is performance 3 - it will use the controller's 3C-4B slots. This pattern eventually loops around, but that's still an issue.
So, for someone with this kind of controller, the user has two options:
1. Ignore the performance mode's "performances" and bank change off the individual MIDI PCs. This means either naming every performance generically, and moving around sounds means reshuffling slots, not simply reorganizing slots.
2. Keep with the performance mode's "performances" and just deal with it or spend money on another controller, whether that's an FCB1010, a Kemper controller, whatever. This means someone having to sell their perfectly useful controller just to fit within the "Kemper MIDI spec."
A solution to both problems would be global MIDI reassignment based on accepted banks, making the controller's bank match up with the Kemper's performance bank, and the controller's slot match up with the Kemper performance's slot.