I am working with setlists. I adapt the parameters in my rackspaces for each song in the setlist and then store it with the floppydisk sign on the top right.
This works fine (I dont have any variations in the rackspaces.)
I used to have transpose knobs in each rackspace, which I recently removed and replaced by a transpose in the Global rackspace.
I noticed that the transpose in the Global rackspace is not stored for each song in the setlist, while it was stored when I had it in each rackspace. Am I doing something wrong or do I have to reintroduce my transpose knob in each rackspace again. I thought it was more efficient and less error prone if I had only 1 transpose in the Global rackspace.
Hello, I like this one. It is a bit of a test of my own understanding (someone can correct me if I am wrong).
First, you may think you you do not have any variations, but you actually do. Each local rackspace automatically has at least one variation. When you use the “floppy disk” you are saving changes in the variation to the song part (“Capture variations”).
So, it seems like you also used to create a widget in the local rackspace to control transpose (I mostly just either bypass or no bypass).
So, now you use a transposer tool in the Global Rackspace? You have that linked to a widget in the Global rackpsace panel? If you do, I think you need to expose them as global parameters that local rackspaces can control then you can save the widget setting in the local rackspace to a song part using the “snapshot” tool you mentioned (the little disk).
To control a widget in the Global Rackspace using a widget in a local rackspace in Gig Performer, you need to link them through a dedicated Global Parameter Assignment. You can achieve this using either a quick shortcut method or a manual setup. [1]
Method 1: The Quick “Shift + Paste” Method
This is the fastest way because Gig Performer handles the background routing and block insertion automatically. [1, 2]
Go to the Global Rackspace (click the globe icon).
Enter Edit mode, select the global widget you want to control, and map it to your desired plugin or system parameter.
Look at the Advanced tab in the Widget Properties inspector on the right, and assign it a Global Parameter Assignment slot (e.g., Param 0).
Right-click the widget and select Copy (or press Cmd+C / Ctrl+C).
Exit the Global Rackspace and go into your local rackspace.
Enter Edit mode, then press and hold the Shift key while pasting the widget (Shift + Cmd+V / Shift + Ctrl+V). [1, 2, 3, 4]
Gig Performer will automatically generate the corresponding local widget, link it to the correct parameter slot, and place the required routing blocks in the background. [1, 2]
Method 2: Manual Setup (Wiring View)
If you prefer to configure the routing yourself or want to link an existing widget in your local rackspace, use the manual approach:
Step 1: Configure the Global Widget
Open the Global Rackspace.
Select your widget in Edit mode, open the Advanced tab in the properties inspector, and choose a slot under Global Parameter Assignment (e.g., Param 0). [1, 2, 3]
Step 2: Configure the Local Rackspace
Switch back to your local rackspace and open the Wiring view.
Insert the From Global Rackspace block into your workspace.
Switch to the local Panels view and enter Edit mode.
Select the local widget you want to use as the controller.
In the Mapping section on the right, select From Global Rackspace as the plugin.
Select the parameter position that matches the slot you picked in step 1 (e.g., Param 0). [1, 2, 3]
Thank you for your reply. I understand what you are trying to do, but this was not my question.
I do not want to control a global widget via a local one through a parameter. May be that’s what i have to do in the end. I just was wondering whether global widget parameters cannot be stored as part of a song part like local ones are stored.
