I see its working without setting it to Radio Group 1, is there any reason why we should set it to Radio Group?
Freezing is likely meaning you are stuck in a loop changing rackspaces.
YAS!
(Yet Another Solution
)
Steps:
- Add a System Actions block in the Global rackspace
- Add three widgets in the Global rackspace, and map them to the ‘ProgramChange’ parameter
- Group them into a Radio Group
- Adjust the Scaling Curves of each widget (0, 1m, 2m, respectively).
Here is a demo gig file.
SystemActions-rackspace-execution.gig (71.8 KB)
I was just about to post this
While I applaud your creativity in using the SAFP, it was probably overly complicating things ![]()
I think a key point with the radio buttons is to also use the setting on the Value tab to disable ‘Send on radio button off’. This is good practice when using radio buttons to control the same parameter, as widgets will send a value when they deactivate, which you don’t want in this case.
Standard latching LED widgets (rather than momentary pads) could also help as you can easily see from the widgets which of the 3 rackspaces are active.
Good idea – I made this a tip! ![]()
→ How to set a widget to jump to a specific rackspace