Try this
OBX.gig (47.9 KB)
Load this gig file and save 3 presets via GP menu with name A, B and C
When you switch between the variations then the desired preset is loaded
and this is the script used:
//$<AutoDeclare>
// DO NOT EDIT THIS SECTION MANUALLY
Var
OBX : PluginBlock
//$</AutoDeclare>
// Called when you switch variations
On Variation(oldVariation : integer, newVariation : integer)
if newVariation == 0 then
LoadGPPreset( OBX, "A" )
elsif newVariation == 1 then
LoadGPPreset( OBX, "B" )
elsif newVariation == 2 then
LoadGPPreset( OBX, "C" )
end
End
You could also include a widget and depending on the value of the widget load a preset.
There is a function on WidgetValuChanged() which can be used.
And you map a hardware controller to your widget
So when you move your controller, the widget is moved and scripting loads a preset.
Or you assign a PC number to your variation and the above shown script reacts on that variation change.
Or you use the function on ControlChangeEvent and parse the incoming CC message and load the desired preset
You see many possibilities
But in my opinion: build different rackspaces with sounds of the same or different plugins and you will be more than excited about patch persist
Do not try to use GP like you would use a real hardware or other DAW, look at the possibilities and design of GP and you will see a universe of flexible possibilities.