Settings for saving variations

General discussion about Gig Performer
1

Hello GP-community,
as I´m new to Gig Performer here a basic question about saving variations.
I figured out that changes in plugins, even stock ones like the audio mixers were not saved between the variations. There saved as soon as the control is connected to a widget.
But any changes in the plugin itsself are not saved.
In the stock templates that sometimes work and sometimes not.

In the web I found some information about a function called “Preserve plugin state per variation”.
I cannot find that function anywhere in my version. (GP 5.1.1).
I did several reinstallations even on different PCs, the behaviour is always the same.

Does anybody knows if there are special settings need to be done or has another idea?

Thank you in advance

Ciao
Thomas

2

Where did you find that information?

3

I think it was Chatgpt

4

OK, and where did ChatGPT find that ?

Plugin states can be controlled by widgets and widget values can be stored/recalled by variations.

So without a connected widget to a parameter the plugin parameter is not stored per variation.

That is the concept of a variation.

1 Like
5

Don´t know, but it was said that there should be a setting icon on every plugin in the wiring view (cogwheel) containing that function.

6

Here from chatGPT

In **Gig Performer**, saving plugin parameters per **Variation** is possible, but it requires some clarification depending on **how** you want the parameters to behave. Here's how it works and how you can achieve it:

---

### 🔄 Understanding Gig Performer Variations

* **Variations** are snapshots of a **Rackspace**, and they allow different states of **widget-controlled parameters**.
* **Plugin parameters themselves** are not saved directly per variation—**only widget values are**.
* Therefore, to change plugin parameters per variation, **you need to link them to widgets** (e.g., knobs, sliders, switches).

---

:white_check_mark: How to Save Plugin Parameters per Variation

  1. Add a Widget in the Front Panel of your Rackspace.
  2. Assign that widget to a plugin parameter (e.g., filter cutoff, amp volume, etc.).
  3. In the Widget Properties, make sure:
  • The widget is mapped to the plugin parameter.
  • The widget is variation-aware (this is default behavior).
  1. Now, when you switch variations, each one can store a different value of the widget, and therefore the plugin parameter changes accordingly.
7

The wiring view is for the complete rackspace and not specific per variation.

8

As I described with the stock template I figured out that e.g. the fader position of the audio mixer is stored without a widget connected.

9

That is a widget and the value of a widget can have different values per variation.
But you are talking about Plugin Parameters and that is a total different thing.

10

Ok, thank you for the info. Then I can be save not to have wrong settings done. Maybe the experience with the audio mixer is fortuity.
Thank you once more

11

You should ask ChatGpt if it was serious with this infomation, because it isn’t existent.
IMHO you should also read the manual, which was written by the developers, rather than relying on what some Large Language Model phantasizes!

2 Likes
12

Say no more.

ChatGPT is a terrific tool for busywork but when it just tells you how to do something, or even just answers questions, it will often present you, with complete confidence, total bullshit.

5 Likes