'Send OSC Command' when a cue starts?

[Matt Padden]

Hi,

Is there a way to send an OSC command when a cue is started in Go Button? All the OSC documentation seems to relate to controlling Go Button from elsewhere; is there a way to make Go Button the controller instead?

I want to create a 'sound-to-light' effect in a show where Go Button is always the source of playback (to a minirig speaker via bluetooth). If I could remotely trigger a QLab laptop from Go Button, then I could run the identical audio cue in QLab and use its 'LiveAverageLevel' OSC method to translate audio level to lighting intensity.

Many thanks,

Matt

[Brent Lord]

Hi Matt --

That sounds like a really neat effect, but unfortunately Go Button is not able to send arbitrary OSC messages at this time. The OSC library in Go Button is mainly focused on allowing other devices to remote control it.

We do have this feature request on our list though, and we have added your vote!

--

Brent Lord | Figure 53

http://gobutton.tips | https://figure53.com/gobutton

[Matt Padden]

Thanks Brent; I’ll keep an eye on the updates.

Cheers,

Matt

--
Change your preferences or unsubscribe here:
http://groups.google.com/group/gobutton
 
Follow Go Button on Twitter: https://twitter.com/gobuttonapp
Follow Figure 53 on Twitter: https://twitter.com/figure53
User Group Code of Conduct: https://figure53.com/help/code-of-conduct/
---
You received this message because you are subscribed to a topic in the Google Groups "Go Button" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gobutton/MMOYcs7VVH4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to gobutton+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gobutton/49688944-904a-4e20-9388-806ff4951969%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Matt Padden
matt.pa...@gmail.com

www.mattpadden.com

[Mic Pool]

This is easy to do  to do with OSCULATOR

From QLab send a network cue with duration for as long as you are likely to want to standby to receive a GO from Go Button

 /cue/playhead/goButtonText

OSCULATOR will then capture a new unique OSC message each time  goButton advances through the QList and the Go Button message changes.

You can then map the message that indicated the relevant cue has started to send an OSC /cue/{number} start cue to QLab 

like this:

Mic