I’m an OSC novice, but I’ve had some success using programs like TouchOSC and Osculator.
I’m trying to understand how GP sends OSC messages over the network. Specifically, I’d like to control a DCA fader on a digital mixing desk from a widget, as a proof-of-concept.
The address for the fader is /dca/1/fdr
Where do I actually address this fader from within GP? Does it need to be a script in order to send OSC?
Ah! Thank you. I was trying to put the address in the OSC/GPScript Name and it obviously wasn’t working. I found the direct addressable OSC preference and that should get me on my way!
Ok everyone…thanks for the direction. Reviewing the OSC literature for the Behringer WING desk:
If I want to change FX slot 1 to a Hall reverb, the OSC command is:
/fx/1/mdl/ ,s HALL
I guess the “,s” designates it as a string message. However, Gig Performer doesn’t seem to like that as a format for an OSC command and rejects it. Any idea on how to format that command correctly so that GP can send it? For what it’s worth, I can successfully send the command using a little application called Wing Live Toolbox that was written by Paul Vannatto.
Ok so I found that customized that script from the very useful code templates. But how would I customize it if I only wanted the reverb to switch to “HALL” when a button is toggled on, but not off? I want the activation to only occur if the widget’s new value is 1.
Beautiful. Now, I don’t mean to stretch this topic, but I’m also curious if you can execute multiple functions simultaneously; or in this specific case, multiple OSC_SendString commands?