FullThrottle64
Inspired
Sure - it's on a different laptop, so it will be a separate post.Can you share your LF+ programming file?
Scenes absolutely propagate the change to the LF+ in real time. I've tested this multiple times, and it works flawlessly. Once you let the External Device Sync function set up the 8 IAs as SCENE selectors, you the IA set to "SYNC DEVICE | AXE_FX III" and they read the scene names from Axe-FX III every time you load the preset or change Scene.Something must be misconfigured either in your Axe-Fx III or LF+. If you change the name of a preset or the name of a scene or the state of a block in one of your Axe-Fx III presets (Not the LF+) and save it, does the LF+ automatically show the changes when you step on a button to select the changed Axe-Fx III preset?
I don't have the Presets linked to automatically update, because the Axe-FX preset names are too long for the button screens.
True, at least in theory. I'm not 100% sure why it needs to work this way, but it does. What I "think" is happening is that the PC command loads the Preset, and the Preset Trigger activates the Scene selection links to the SCENE IAs.IA's aren't presets, so I don't understand how one could sync an Axe-Fx III preset name. You can manually name an IA the name of an Axe-Fx III preset and assign a PC# in the IA programming to select an Axe-Fx III preset but it won't know how to sync. If you have the PC# command and the "Preset trigger" command in an IA, that doesn't make sense because that would send a PC# to select an Axe-Fx III preset and then select a LF+ Preset that would send another PC# to select an Axe-Fx III preset, so you'd be sending 2 PC# commands in a row.
For my main "Kitchen Sink" Preset where I don't use Scenes, I am only using the PC command, and not the Preset Trigger. That works OK to load the Axe-FX Preset, but does not reset the SCENE names (which is OK when I'm not using Scenes).
OK, this is really helpful - and this wasn't clear AT ALL in the documentation (at least not to me). While it doesn't explain why the Presets were randomly shifting, it does give me a direction to start looking into.When you assign Preset B#11 to a button on a Page, that's not assigning LF+ Preset 011 or Axe-Fx III Preset 011 to that button. It's assigning the 11th preset in a bank of presets.
I understand that Presets in LF+ don't have to map directly to AFX Presets in any given order - that's already clear and I've got that piece working.
How do you assign a specific Page Button to a specific Preset without it having anything to do with Preset Banks? The only way I've been able to make that work is to use the IAs. I don't care about Songs, Set Lists, or any of that other junk, I just need a specific Button on a specific Page to call up a specific Preset. Is there a way to globally lock down the Bank so that Preset B#01 is always Preset 1 and cannot be changed, offset, shifted, or scrolled?
What was happening was this:
I had set the upper two left buttons (9 and 10) to select Presets on each of the first 10 Pages. When I would go to, say, page 8 and hit button 10, it would call up preset #20 (as it should). Trouble is, when I would scroll back to page 1, I now had Preset 21 where Preset 1 should have been. The entire board's Preset selections were offset by the number of the Preset I had selected. This makes zero sense to me - a Preset number hard coded to a Button should be that Preset, right? I was careful to not have the "Trigger Scrolls" enabled, as well, so that wasn't it.