Keep IA State between presets?

J

JOHN ORANGE

Member
Hi all,

I have two amps and I want to be able to use them on the fly in either of Amp A, Amp B or Amp A+B (these would be on a page called Amp Config Page). I initially thought of having two IA buttons, one for Amp A, one for Amp B and if I decide to use both I press both. What I do not know is how to make it so these IA buttons remain unaffected by presets changes, i.e. if I decide I would play Amp A only, once its IA is active it should not be affected by preset changes throughout the show.

Another scenario I am trying to mimic is the following. I have a PCM 81. I programmed one IA to activate or deactivate the corresponding PCM81 loop in my mixer (I will call this the PCM IA). I intend to have another page with IA Buttons corresponding to programs within the PCM81 (I will call this the PCM 81 Presets Page). So, on this page I want to select what program should be loaded in the PCM81, and with the PCM IA I just add or remove the PCM from the signal chain. Here I would also wish any PCM 81 Preset that I selected on the PCM Presets Page is not affected by preset changes throughout the show.

Basically, I see these as config pages, where i should be able to set a default, but if decide to change that default during the show, such change should not be affected by the loading or changing of presets.

Any advice would be much appreciated.

Many thanks,
JO
 
The setting Update on Preset Change is what you're looking for. Turn it off on any buttons that you want to be unaffected by preset changes.
 
Thanks for the prompt response. Will try this and revert. Send on Preset Change should be on or off in this case? I am trying to figure out how to set up the default behviour. Eg by default a preset should have a specifc IA Button on (let's call this the default IA Button), but once that is changed - because I turned on another IA Button within the same group with the default IA Button - , when loading a new preset the default IA Button should not turn on again. Hope this make sense. :)

Added an example of what I am trying to do:

GT Preset #1 has:
IA Button #1 - Loads Program #1 on PCM81 - this is on by default
IA Button #2 - Loads Program #2 on PCM81
IA Button #3 - Loads Program #3 on the PCM81

IA Button 4# - Turns on/off the corresponding loop for the PCM81 in the mixer
Buttons #1 - #3 are part of a group.

Because the PCM81 loads programs in 1-2 seconds, I need to preload the program well in advance of turning on IA Button #4 - corresponding to the loop of the PCM81. Basically, with the help of IA Buttons #1 - #3 I select the program on the PCM81, and then with IA Button #4 I just add it to the signal chain, or remove it. By so doing, IA Button #4 may turn on a chorus, or a delay, or a reverb, depending on which IA Button #1-#3 is selected.

What I want to do is when I load GT Preset #1, IA Button #1 sends its actions - so that a default program is always loaded on the PCM81. However, if I turn on IA Button #2, whatever preset I load on the GT, including GT Preset #1, IA Button #2 should remain on.
 
Last edited:
If the IA buttons are the only thing that sends messages to the PCM81, then you probably don't need or want Send on Preset Change to be turned on.
 
Hi there, finally had the time to program the above and I am half where I wish to be, i.e. presets do not change the state of IA Buttons. Thanks so much for your help!

Now the other issue I am trying to solve is how can I set, among these buttons, the one which should be on by default when the GT boots up.
Example:
IA Button #1 - Loads Program #1 on PCM81 - is sent an on message when the GT boots up.
IA Button #2 - Loads Program #2 on PCM81
IA Button #3 - Loads Program #3 on the PCM81

These are grouped in a group which has Allow all buttons off disabled - basically one should always be on. The problem is, because all these buttons do not have enabled Send on Preset Change or Update on Preset Change, I cannot change the state of the buttons through presets and I did not find a way to turn one of these buttons on by default when the GT starts.

I was thinking of creating a Macro named Load Defaults, but do not know what action to run (Set IA perhaps with Force State On, or a Sysex message?) Thanks so much for the guidance. I am absolutely amazed by the mirriad of options the GT provides.
 
Last edited:
You're correct that a Macro with a SetIA action was going to be my answer. Set IA does cause all actions on a button to be run, as if the button had been pressed.
 
John, I’m interested in the exact same thing. Have some IA buttons start with the state on. You seemed to have solved this with macros, but where do you put the macros to run on? If it’s in the button, you’ll have to press the button to trigger the macro.

Thank you,

Joao.
 
Jcharnet said:
John, I’m interested in the exact same thing. Have some IA buttons start with the state on. You seemed to have solved this with macros, but where do you put the macros to run on? If it’s in the button, you’ll have to press the button to trigger the macro.

Thank you,

Joao.
Click to expand...
If you're referring to setting button states on powerup, then you can choose a startup macro in global settings.
 
Thanks, just tried it out. Set the Startup Macron in Global Settings to 0, and my Macro looks like this:
1743983428399.png
I have 2 buttons with the IA ID set to 10. First button sets Channel 1 to AMP A, and second button sets Channel 1 to AMP B. I'd like these 2 buttons to start on, since the amp will always have one channel on, and I don't mind if it's always channel 1 to be honest.
I must be doing something wrong, because I don't see the buttons starting up ON.
Here's a screenshot of one of the buttons:
1743983557215.png

Any ideas what I'm doing wrong?

Thank you,

Joao.
 
Your buttons are grouped and IA linked, so that might have something to do with it. Does it work if you disable those features?
 
They have to be grouped, because I have Channel 1, 2, 3 buttons and doesn't make sense to have both on. The IA link was a test I did, but I did have that turned off, and just tested with IA Link off. Still can't get the buttons to start with ON state. Any other ideas?
 
Please send me your settings file, it would be a lot easier to debug it if I could try it here.
 
Here you go, it's the same file for the other thread I have going to manage Axe Fx and QC, so if you'd like to take a look at that as well.
For this case, the buttons are on page 4.
My intention is to have MK VII\CH1(button 5 page 4) and 5150\CH1 (button 8 page 4) turned on by default when starting up G22.
 
I checked your older file from the other thread, and it doesn't have a page 4. Can you send again? I now remember that you had to send the file to our support email address to get it to go through.
 
I just realized, if the buttons are grouped, all you have to do is turn off Allow All Buttons Off for the group(s) and it'll force the first button to be on.
(found in Group Settings on the Global tab)
 
Yeah, weird why I can't attach it here, trying a zip version.

I do have Allow All Buttons Off. But now I see what happens. When I start GT22, both buttons are turned on ( I don't think they send the midi commands though, because I tried to set my amps to different channels and startup GT22 and even though the buttons were on, the amps did not change channels, but that's ok), however, if I change anything through the editor and transfer the changes to GT22, both buttons gets turned off. I guess I was imagining that when we update, it was like a reboot, maybe not, and not sure why it get's turned off. I think I'm good with the way it is right now. Unless you tell me that at start up the midi commands for both buttons should be sent, then we still have to troubleshoot.
 

Attachments

  • mmgt_complete_devices.rjs.zip
    59.1 KB · Views: 0
If I have a start up macro sending the midi commands for channel 1 for my both buttons, then on startup it is selecting channel 1 and the buttons are on by default because they are a group, with Allow all buttons off disabled.
This might be enough for my home setup.
 
Jcharnet said:
If I have a start up macro sending the midi commands for channel 1 for my both buttons, then on startup it is selecting channel 1 and the buttons are on by default because they are a group, with Allow all buttons off disabled.
This might be enough for my home setup.
Click to expand...
Ok, that sounds good. and should work reliably.

Just FYI, startup macros only run when the unit powers up. Sending settings to the device doesn't trigger a full reset.
 
You must log in or register to reply here.
Back
Top