Static NamesOk, in thinking about this there are two possibilities for scene names:
Option 1: Dynamic Names
With this option, scene names are downloaded every time you load a preset, and scene buttons are automatically updated to display those names.
Advantages:
Disadvantages:
- Scene names will always represent what's currently stored in the Axe-Fx, no need to explicitly download scene names
Option 2: Static Names
- Scene names are not stored, so they will not be visible in the editor
- Scene names have to be queried upon each preset change, one by one. This will be fairly quick (less than a second), but probably slow enough that you'll see each scene button visibly update one after the other after you change presets.
Using this option, scene names are downloaded using Get Preset Names, and are (probably) stored in each GT preset.
Advantages:
Disadvantages:
- Scene names will be visible and editable in the editor
- Scene button names will change as quickly as any other button
- You need to do a Get Preset Names (or manually edit names) to update scene names if they've been changed on the Axe-Fx
Any opinions on this? I have a preference, but I won't mention it yet.
I pick option 2 because I want to be able to see the scene names and be able to edit them in the editor. Having to GetPresetNames is fine to me but I’m sure others may disagree.Ok, in thinking about this there are two possibilities for scene names:
Option 1: Dynamic Names
With this option, scene names are downloaded every time you load a preset, and scene buttons are automatically updated to display those names.
Advantages:
Disadvantages:
- Scene names will always represent what's currently stored in the Axe-Fx, no need to explicitly download scene names
Option 2: Static Names
- Scene names are not stored, so they will not be visible in the editor
- Scene names have to be queried upon each preset change, one by one. This will be fairly quick (less than a second), but probably slow enough that you'll see each scene button visibly update one after the other after you change presets.
Using this option, scene names are downloaded using Get Preset Names, and are (probably) stored in each GT preset.
Advantages:
Disadvantages:
- Scene names will be visible and editable in the editor
- Scene button names will change as quickly as any other button
- You need to do a Get Preset Names (or manually edit names) to update scene names if they've been changed on the Axe-Fx
Any opinions on this? I have a preference, but I won't mention it yet.
Guys, as I mentioned to Ron in another thread, the Scenes-to-Presets thing is growing on me.
You might want to give it a chance.
Here's my experimental GT layout, based on it. And it works fine, aside from a few bugs which will be fixed.
Scenes on the bottom (names fetched from the Axe), presets accessible through a Presets button (which actually is "Song Menu"), IA Mode reveals other IAs at the bottom, etc.
Works quite like the old system, with benefits. Just have to get used to the "scenes=presets" paradigm.
View attachment 967
Warning: in MIDI Settings do not change the MIDI Rx Channel (off by default). When you change it to channel 1, unexpected things start to happen.
This does mean that the GT doesn't adhere to preset switching on the III itself.
Only thing not working with this setup is that on subsequent pages, you can’t mess with the bottom row. I think it was more flexible before on the II. I could gig with this but it would be a big change.