Send OSC Boolean value

1,044 views
Skip to first unread message

Clay Benning

unread,
Feb 16, 2014, 8:12:33 PM2/16/14
to ql...@googlegroups.com
When sending a custom message via an OSC cue, is there a way to have QLab specify a Boolean value? QLab seems to send the string argument for every value that is not an integer or float value. That is, if I type 'True' or 'T' for Boolean true, QLab packages that argument as a string, which cause the message to fail on a device expecting a Boolean argument.

Is there a special format I should be using? I can't seem to find anything documented for this...

Thanks,
Clay

Christopher Ashworth

unread,
Feb 16, 2014, 8:23:17 PM2/16/14
to ql...@googlegroups.com
Not yet-- I plan on adding a way to do this. It currently only handles the four requires types in the 1.0 spec.

(mobile)

Joe H

unread,
May 7, 2015, 7:11:51 PM5/7/15
to ql...@googlegroups.com
Did this get resolved? I'm trying to set Boolean, as well as float,  values on a Meyer Galileo and running into snags. 
Thanks!
Joe.

Christopher Ashworth

unread,
May 7, 2015, 8:46:41 PM5/7/15
to ql...@googlegroups.com
Apologies Joe I have not added support for it yet.

(mobile)

Joe H

unread,
May 9, 2015, 3:08:31 PM5/9/15
to ql...@googlegroups.com
I figured it out - you use a float instead of an integer, and it works! 
For example: the spec says /Output/1/Mute,T - that doesn't work in Qlab's wrapper, nor does 
/Output/1/Mute 1
BUT /Output/1/Mute 1.0 mutes the channel, and /Output/1/Mute 0 unmutes it. 

Problem solved! 

Matthew Miles

unread,
Jun 9, 2015, 9:07:43 PM6/9/15
to ql...@googlegroups.com
I'm wondering if you could tell me what port your are sending to?  I'm trying to get qlab to mute inputs and outputs on a Meyer Galileo as well.  Not having any luck though.  Did you have to enable anything in the Galileo?  Any help would be greatly appreciated.

Thank you.

Andrew Keister

unread,
Jun 9, 2015, 10:22:05 PM6/9/15
to ql...@googlegroups.com
Galileos listen on port 15006 and should reply on 15007. I've had some units that did not reply by default on 15007, but that is easily fixed with /setudpreplyport followed by the desired port as a int32 number.

You can test the connection with /ping which will cause the Galileo to reply /pong.


Meyer's OSC implementation is pretty good at this point. I'm re-matrixing cue by cue via OSC commands on a show right now. We tested changing filters dynamically too, though so far I haven't needed to do that in performance so far.

Andrew

Matthew Miles

unread,
Jun 11, 2015, 9:21:05 PM6/11/15
to ql...@googlegroups.com
Thank you very much for your reply. I had some time to try it again today, but still no luck. I have a osc cue in qlab. It's set to custom osc message. I have the Galileo as a osc patch in qlabs settings at its IP address and port 15006. The osc cues message is /Output/1/Mute 0 and another as /Output/1/Mute 1.0 as I saw in other messages. Am I missing something? I'm assuming that if I wanted to mute the inputs it would be something like /Input/A/Mute 0? Like the outputs? Thank you again for any and all help. I really appreciate it.

Andrew Keister

unread,
Jun 12, 2015, 2:05:21 AM6/12/15
to ql...@googlegroups.com
I've not tried using a float instead of a boolean to change the mute state, though others have reported success with that method. (I don't want to start a debate but 0 is an Integer - 0.0 would seem the correct syntax for a Float). If I have time in the morning I'll try it and see what syntax works on our system.

Have you tested the network connection between the Qlab computer and the Galileo? Are the IP addresses of both your Mac and the Galileo in the correct range with matched subnet masks? Using Network Utilities on the Mac, can you successfully ping the Galileo? If that is all working, try running OSC monitor on your mac to monitor port 15007 and send /ping from Qlab to the Galileo, if your connection is good the Galileo should respond with /pong. Assuming all of that is working, if your mute commands still are not functioning, perhaps you could try recalling a snapshot with the mutes in the state you are trying to achieve. /recall with a snapshot number between 1 and 999 will trigger a recall on the Galileo. 

Best,

Andrew

Joe H

unread,
Jun 12, 2015, 10:08:26 PM6/12/15
to ql...@googlegroups.com
Andrew: It is weird that the integer 0 works but 1 has to be a float, that's why I mentioned it. No debate!
Matthew: As Andrew said, confirm connection with Compass or ping, with matched first three groups of IP address, matched subnet mask, etc. 

Sean Boyer

unread,
Feb 18, 2020, 8:31:49 PM2/18/20
to QLab
Just a note to say that when sending OSC via TCP, the reply port is 15007, however, if using UDP, it will reply on port 15006 - same as the origin port.

Sean Boyer

unread,
Feb 18, 2020, 8:35:53 PM2/18/20
to QLab
I've been using a little app called sendosc (which you can get on homebrew) to send messages to my Galileo. It supports sending boolean types, so this always works for me: sendosc 10.10.10.10 15006 /Input/A-D/Mute b false

I'm actually working on a more fully featured commandline tool to communicate with the Galileo so I can do predicate statements (like "if the profile is x AND inputs C-D are MUTE, then UNMUTE C-D"). 
Reply all
Reply to author
Forward
0 new messages