Issues with Scenes / (&MFC)
First let me say, that the idea of "scenes" is very nice! I have doing intensive tests with this new feature, but will give FAS feedback for some issues I have, perhaps some suggestions:
Scenes are the perfect solution and the last argument NOT using the MFC in Axe-Fx=NONE mode:
Now, it is not needed to save up to eight times the same preset on different preset locations in the Axe-Fx with just different IA stats. This is welcome, because of better "organisation" of your presets (think about ONE Song = One Preset with up to 8 different IA stats within the song (intro, chorus, ref., solo, etc.).
So, what I am looking for is using scenes by PC-Change. This could be managed through the PC Mapping in the Axe-Fx. Fine.
Problem: Mapping have to be on "Custom" (=ON), but only the first 128 Presets can be selected to map. Furthermore, if Preset-Numbers above 128 are selected through MFC (MIDI 0-127 + Bankswitch command), it will not work (see some pictures with "funny" Recall screenshots, what happens, if you select presets higher than 128 on the MFC … ).
To select a Preset with a scene higher than the default "1" with ONE PC button on the MFC, you can also do this not by using Mapping (incl scene Mapping), but using a PC command AND (for example) a Internal CC.
Problem: This will work only for ONE additional Scene 2 to 8 (cause Scene 1 identical to "normal" preset select). Internal CCs can only switched globally on or off. If you want more than one scene select within a preset-change, you`ll have to switch up to 8 Internall CCs to ON. Now, these Internal CCs send all on CC 34 but, with different CC Values -> Axe-Fx can not interprete correct, because it receive the order on CC34 to switch to value 0,1,2,3,4,5,6,7,8 at all the same time
Suggestion: Every Scene get it`s own CC command. (i think by default the first ten CCs are not in use?!)
But there will be more problems: You`ll have to program in Axe-Fx Mode=ON Mode in the MFC every Preset with a X-Mapping, to reach with different PCs always the same Preset on the Axe-Fx (with only different scenes).
Next Problem: It seems that sending CC-changes from the MFC to the Axe don`t let the Axe resend the new IA-stats for the different IA-Switches on the MFC (red/green, FX block used / unused).
So, just an idea: What if the Axe-Fx would interprete a Scene-change like a PC-Change? Hopefully, the Axe would resend the new IA stats again to the MFC. Let`s think furthermore that way:
What, if I could give every Scene a dedicated Name? In default, Scene1 = Preset (PC Number xy). Default scene 2-8 get the same Presetname, but could be individually overwritten by user.
So, when I think that to the end, I talk more about "Sub-Presets), than "Scenes". If a command change, equal if it`s just a PC-change OR a CC-Change which correspondend to a SCENE (!!!), the Axe-Fx reacts like it does on a PC-Change, we all know: It re-send the Information of the actual Preset-layout (exactly the actual layout of the selected scene) to the MFC, including all NON-SCENE-CCs and PC.
Again: At the moment, when I just program the MFC to send a CC34 and a value from 001 or higher, the MFC will NOT represent the "new" IA on/off stats, which are programmed in that specific scene! The MFC always shows the stats of the Preset ( =Scene1).
ONLY if you remap through the Axe-Fx Mapping function, the Axe-Fx sends the new scene INCLUDING the new IA stats!
Last, but not least let me say: I recommend to set IGNORE REDUNDANT PC to ON. Why? Because when recall the Scenes by Mapping function and select the on/off stats by using my midi controller (MFC) I would always lose my "programming informations per scene" if I just want to change scene, but NOT RECALL the whole Preset (by loading the Axe-Fx preset new).
Also, this all just will work nice, if TOTAL SYNC on the MFC is set to OFF. Why? Because, if it`s on, it interpretes the PC-Mapping from the Axe-Fx and switch back to that preset …
I know my English is bad, but I would be really appreciate, if you could understand, what i`m trying to say. Furthermore, if FAS would comment this …
Regards
Markus