OSC Controlling GP

OSC
1

I think I’m missing something here. Probably not formating my OSC strings properly when typing it out whilst programming. Trying to automate Rackspace & Variations based on a timeline.

Read through the OSC documentation on at least 20+ times OSC Messages And was able to get…

/GigPerformer/NextRackSpace
/GigPerformer/PrevRackSpace
/RackSpace/NextVariation
/RackSpace/PrevVariation

…to work properly. So I know OSC is being sent AND received. But I’d LIKE to just shoot straight to the Rackspace & Variations needed. Unfortunately, every permutation of…

/GigPerformer/SwitchToRackSpace Rack_A:Var_2

…I’ve tried is not working. I know it’s probably something simple & I’m just too boneheaded to get it. What am I missing?

2

First you send the OSC message to selects a rackspace and then this message
/RackSpace/SetVariation Integer
Switch to the (zero based) variation

3

But when you want to synch 2 instances of GP there are options in the global OSC options to achieve that

4

/GigPerformer/SwitchToRackSpace <String | number> <number>?

Meaning you can pass one or two parameters to this OSC message. The first parameter can either be the name of a rackspace or its index number starting from 0. The second one, if there, is the variation index where the first variation would be 0

5

Thank you both, your replies got me thinking about it. And working through & checking my OSC syntax. @pianopaul solution required 2 commands which DID work…kinda! And was actually the smoking gun.

So I WAS setting up to rewrite my commands. Got distracted by a phone call, walked away from my desk. Saw @dhj replied as well, read it.

When I came back to my desk, neglected to remember where I was in the process. Ya ever forget? Happened to me.

Absentmindedly wrote out @dhj solution <String | number> (minus the colon I had added for whatever reason)
…it worked, first try!

Come to find out, I had written
/GigPerformer/SwitchToRack
already from the first part of @pianopaul solution to switch the appropriate Rack…

Going over the syntax further. Noticed that I was just “Rack” instead of “RackSpace”. Changed it to “RackSpace”…It failed.

Changed it back to just
/GigPerformer/SwitchToRack<String | number>

And it worked perfectly. :man_shrugging:

I’ve tried it with my WHOLE automated timeline. Works flawlessly.

Not going to argue with results! Just to note then, That some of the OSC Syntax in OSC Messages on the Gig Performer 4.x User Manual could use some looking at. Might be time to revise or release a 5.x version

But…Hey I’ll take it!

Wanted to let you guys know, it was a happenstance mishmash of your replies.

6

I was using version 5 of Gig Performer — we added /GigPerformer/SwitchToRackSpace in GP5

7

Dunno what to tell ya :man_shrugging:
I have the newest released version of GP 5.0.20 on both my Editing Desktop PC & On Stage Macbook.

Tried it on both, just to confirm. And it did NOT work with the word “Space” in the syntax. Works flawlessly the other way.

8

Actually, 5.0.28 has been released quietly — we will be announcing it shortly.

Go back to regular downloads and just download again, you should be able to get that new version

9

Updated both studio rig & show rig to 5.0.28

Still works off the

/Rack[space][space]

No need to add the word “Space”.

Just held practice Saturday night. Worked flawlessly. :+1: