Qlab OSC command parsing port 53535

[Christoph Tiefenthaler]

Hi there,

I´d like to send OSC commands to Qlab to port 5300 in the same way it is possible with port 53535. There obviously is a built in parser in Qlab, which is great, but I´d like to have a look, what the parsed commands look like.

For example I´d like to see, what Qlab is doing with "192.168.0.3:53535:/cue/1/start", because it doesn't get along with the same command on any other port. I´m pretty sure, that it´s got something to do with byte padding. But at this point my computer skills are over.

Is there a place or log-file I can see the output of the parser?

I´m sending my OSC commands from this device.

Thanks a lot

Christoph

[Chris Ashworth]

Hi Christoph,

Welcome to the list!

OSC can be a bit confusing because it looks so much like a plain text protocol, but is not a plain text protocol.  It is likely that the message you’re sending to 53535 is not an OSC message, and you will need a mechanism (e.g. a programming library or other tool) that is able to generate well-formed OSC messages to send them to 53535.

For now, the place to find information about what OSC messages QLab is receiving is in the Console.app utility.  You’ll need to turn on Log Level 2 in QLab (QLab —> Preferences —> Log Level 2) and then you should see some information about what is getting in. If that doesn’t show much you could try bumping to level 3.  Good luck!

Best,

Chris

[Andy Lang]

On Fri, Oct 28, 2016 at 9:23 AM Christoph Tiefenthaler christo...@gmx.at wrote:

Hi there,

I´d like to send OSC commands to Qlab to port 5300 in the same way it is possible with port 53535. There obviously is a built in parser in Qlab, which is great, but I´d like to have a look, what the parsed commands look like.

Hi Cristoph,

I think my teammate Chris missed the part about using other ports in your original question when he answered you a little while ago. Using other ports than those normally used by QLab is not possible. QLab will only listen to two specific ports:

-On port 53000, it will listen for messages formatted as per the OSC specification; the commands are structured as per our OSC API, and then formatted with the appropriate byte padding, etc as definied in the official OSC specification.

-On port 53535, it will listen for messages formatted as per our OSC API, but as plaintext strings, without the formal OSC formatting, just as you’d type them into an OSC cue.

No messages can be received by any other port, or in any other format, so trying to send to port 5300, or any other, will simply not produce any response.

If you can let us know what are you trying to do that requires listening to another port, we may be able to offer suggestions of other solutions, although in the end, you'll need to send the messages to QLab on the port it expects to receive them on. (You could, potentially, use a program like ETC's OSCRouter to receive on one port and retransmit on another. But in most cases, that's complicating things more than is necessary, when just sending on the correct port is a simpler solution.)

Don’t hesitate to reach out if we can help with anything else, and have an awesome weekend!

-Andy

—
Andy Lang
@SoundGuyAndy
sup...@figure53.com

​