Controling radio group buttons in a global rackspace from a local rackspace

General discussion about Gig Performer
1

Hello,

I am currently experimenting with an vst in which I can change different scenes with CC92 and different values (eight different). In the global rackspace I have eight buttons sending CC92 (with eight different values) to a midi in block linked to the vst and it works if I use the buttons directly in the global rackspace. The buttons are in radio group 1.

I want to control them from local rackspaces, so I copied the eight buttons from the global to the local rackspace, put them to radio group 2 and mapped them to the related button in the global rackspace.

It was working for a couple switches, but then it’s seems to be confused.
Made someobdy similar experiance with a similar set up and can tell me what I am doing wrong?

Thanks Flodder

3

I’ve found that radio buttons are a nice, simple way to select one item from a single button or key on a controller without the need for scripting. However, they don’t work great when doing more complex tasks due to race conditions.

For instance, I made a script that responded to Variation changes, using On Variation( … ). I had planned to read the state of some radio buttons and respond; however, there was a race condition. The callback was triggered before the radio group had responded.

My recommendation is to use radio button groups only for the simplest implementations. If you will do scripting, script the radio button logic yourself.

Crossing the Local/Global divide appears to have similar complications. You might try radio buttons only on the local side or only on the global side. If that doesn’t work, you might need to skip the radio buttons and add the needed scripting.

The radio button groups are great for their basic functionality, but I recommend avoiding them for more advanced features. Fortunately, scripting can bridge the gap.

5

Thanks to all,

the VST has no Problem with all data I am sending (through the midi block). This is absolutely no issue.
It’s the communication in between local and global rackspace, I guess.

I am a couple years now a “power user” of this
fantastic software.
From my experience it”s me whom is doing something wrong and not GP which can not work with that what it offering…

Thanks
Flodder

7

I can answer all with “yes”.

9

Have you tried to only use a radio group in the global rackspace and leave the connected local buttons “un-radio’ed”?

3 Likes
11

Thanks @schamass , that works.
The buttons in the local rs are now in “momentary “.
Even if the buttons in the global rs are in “latching” they behave “momentary”, so I can not see the actual status. If that could be fixed it would work

Cheers
Flodder

12

And why is this so if you need it to be diffrent?
Just make them latching and you are good. What is the problem?

I just tried it:

  • 5 buttons (latching) in the global rackspace
  • put those in radio group 1
  • assign them each to a global parameter
  • “from global rackspace” plugin in local wiring view
  • 5 buttons (latching) in the local rackspace
  • connect each of them to the corresponding parameter of the “from global” plugin.

Worked instantly in both directions local- ↔ global

global-local-radiobuttonsgig.gig (138.2 KB)

1 Like
13

Thanks @schamass , sorry for late response, yesterday was Carneval in town :smiling_face:

Your exemple works, but not if all buttons of the global rs are mapped to
the same midi in, in my case cc92, just with different values