ACTION TYPE: IA STORE WHEN BUTTON OFF

MarMaZ

Active Member
PLEASE, add the ability in the "IA button setting - action type: System / IA Store" to store even when the button is Off (currently the command stores only when the button is On...)

I know that the "IA Store" type button exists, but (at least to me:)) it would be a huge benefit - THANKS!
 

Attachments

  • ia store.jpg
    ia store.jpg
    91.5 KB · Views: 4
Thanks for your suggestion.

Can you please provide us with a detailed step-by-step idea as to situations when you'd use this and how?

Thanks again!
 
I state that the use I make of the GT-16 is not the "orthodox" one, since I use it in the context of creating live improvised music...

From my brief experience I deduced that (for me) the most convenient way to set it up is to use pages; however, since I have to be able to control several devices (five at the moment, but I will add at least three more) the pages are not enough; so I set it so that, for some devices, each preset uses its own "local page": in this way I have 768 presets/pages available!

However, in this way the problem arises of having the presets of a given device distinct and separate from those of another, in order to be able to recall them based on the device you want to use at that moment

E.g.: in the Roland VB-99 I programmed 30 presets

in the Boss SY-300 I programmed 25 presets

So I have to find a way that allows me to quickly choose and select the presets of these devices.

To solve this problem in the most effective way I use the songs and setlists in this way:

  • with the songs I group different sets of patches for a given synth, naming them according to precise sound characteristics;
  • With the setlists I group these songs, naming them according to the device to which they refer;
e.g.: for VB-99 I create the song "Leads" which contains 5 presets that recall as many patches with that characteristic ("leads" sounds), the song "Distort" which contains 4 presets that recall patches with another characteristic (distorted sounds), the song "Ambient" which contains 8 presets that recall patches with a different characteristic (sounds suitable for "ambient" atmospheres) and so on...

Of course, I also adopted the same procedure for the SY-300 synth.

Es.: the setlist "VB-99" contains the song "Leads", "Distort", "Ambient"...

the "SY-300" setlist contains other songs ("Rhythmic", "Solos", "Spatial"...)

  • then, with the "Setlist Menu" command I can quickly choose the device I am interested in, select it and then choose and recall the various presets for that specific device;
  • moreover, with the "Song Menu" command I can quickly choose and select presets based on their sound characteristic, great!
However, in order to better manage the other devices (a loop station, a reverb/delay unit and a drum machine) I had to follow a different procedure:

even if, like the others, they are displayed and called up by the "Setlist Menu" command, instead of the "local page" they use certain pages (3-4 for each);



For example, for the delay/reverb unit this is the procedure:

  • 1 - Using the "Setlist Menu" command I call up the device (delay/reverb), which is set to call up page 1;
  • 2 - On page 1 I set various buttons (On-Off, not momentary) so that they turn on or off the different delays and the reverb: one for the delay type "A", one for the type "B" and one for the reverb –
  • 3 - in addition, I added the "AI Store" action in each of them in order to automate the memorization of the visual state without having to use an "IA Store" button every time
  • 4 - Since you need more pages to have total control, I copied these three buttons to the other pages (where you can find other options related to the parameters of delays and reverbs) so that, even browsing between these pages, I can always see if a certain delay or reverb is on or off (via the "IA link" option)
  • 5 - One of these pages is dedicated to patches with which it is possible to recall the status (On/Off) and the settings of the various parameters of the delays and reverbers of the device,
ES.: the "LIQ-TAP-HALL" button calls up a patch that sets the delay "A" with the "Liquid" type, the delay "B" with the "Tape" type and the reverb with the "Hall" type and requires that they are all on (ON);

the "GLX-CRYS-PLATE" button calls up a patch that sets the delay "A" with the "Galaxy" type, the "B" delay with the "Crystal" type and the reverb with the "Plate" type and provides that the delays "A" and "B" are on (ON), while the reverb is off (OFF);

And so on

to achieve this I set a specific "IA ID" for each of the three buttons related to delay and reverb and I added the "Set IA" action in the buttons of the patches;
but evidently this setting (Set IA) creates a problem in the delay and reverb buttons, since it "forces" these buttons to always assume the visual state set in the patch when I change setlist without taking into account the "AI Store" action (see point 3):

  • If I turn On a delay and then change device (e.g.: "Setlist Menu" > VB-99) when I return to the delay/reverb device the button maintains the correct visual state (On)
  • If, on the other hand, I turn Off a delay or reverb and then change the device (e.g.: "Setlist Menu" > SY-300) when I return to the delay/reverb device the button does NOT maintain the correct visual state (it changes to On instead of remaining Off)

Basically, the "IA Store" action present in the three delay and reverb buttons is performed only when the button is in ON and is ignored in OFF
I know that before changing devices I could use the "IA Store" command every time I put a delay or a reverb in Off, but this is exactly what I would like to avoid!

Sorry if I wrote a very long explanation but I hope I was clear-
 

Attachments

  • IMG_20251115_104819.jpg
    IMG_20251115_104819.jpg
    1,012.8 KB · Views: 2
  • IMG_20251115_101446.jpg
    IMG_20251115_101446.jpg
    1 MB · Views: 2
  • IMG_20251115_104338.jpg
    IMG_20251115_104338.jpg
    727.2 KB · Views: 2
Last edited:
Thank you very much for taking the time to explain your requirement in such great detail. This will help us consider whether it can and/or if we should implement it in a future update.

As you mentioned; "...the use I make of the GT-16 is not the "orthodox" one..." which is something we need to consider. Sometimes making changes that will only apply to a small number of users isn't practical, for a variety of reasons, and we sincerely hope people can understand this.

That said, we do take every suggestion seriously and do think about each one and consider adding them in future updates.

It's obvious from your requirements that button real estate is very valuable and having to press another button is something you'd like to avoid. But while that's not possible right now, if I were in your situation, I would use an external button as an IA Store. Yes it would require another button press, but it would at least not take up a valuable button (with a display).

I hope this helps and please keep an eye out for future updates to see if it's been implemented.
 
You could use a macro as a workaround. Macros have the ability to turn an "off" event into an "on" event, or vice-versa, If you create a macro with an IA Store event in it, then set Force State To On, you can call that macro from your buttons. Every time that macro is called, it will perform an IA store, regardless of the state of the button that triggered it.
 
Thank you for your answers and valuable advice but I inform you that my neurons have started working again:D!

The problem was caused by "Update On Preset Change": just uncheck this option and everything works perfectly!
 
Back
Top