Re: [QLab] Lab control from Pharos/Moasic

[Sam Kusnetz]

Sean

Set your Tessera to send messages to port 53535 and you should be all set. QLab listens on that port for plain ASCII text, and then interprets that text as OSC. Since the Tessera doesn't send actual OSC, just text over UDP, that's he port you want.

Sam

Sean Smallman

February 14, 2016 at 1:36 PM

Hi all,

I am working with my church to theme our children area. I am using ETC's Mosaic (which is identical to the Pharos controls) to control lighting, and using QLab for audio/video playout. 

I am trying to link the two systems so that I am not completely relying on wall-clock triggers. I have a Mosaic Tessera (http://www.etcconnect.com/Products/Architectural-Systems/Mosaic/Controllers/Tessera/Features.aspx  https://www.pharoscontrols.com/products/lighting_controllers/tpc) that I am using for the lighting control. I am able to create buttons on the touchscreen to trigger things but I am having difficulty linking it to QLab. I am able to output UDP ASCII strings, but am unsure how to get that to trigger QLab. (See the attached photo for the UDP settings)

 

Ideally, all I need is a couple triggers on the touchscreen that will trigger cues in QLab. Fortunately, since everything is designed as a themed package, the end users have little control other than a couple basic triggers to turn on, off, and quiet down the entire system.

Any help is greatly appreciated!

Thanks, 

Sean

--
--
Change your preferences or unsubscribe here:
http://groups.google.com/group/qlab
 
Follow Figure 53 on Twitter: http://twitter.com/Figure53
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/30087f65-e1e3-4314-9666-5391f9d085b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Sam Kusnetz | Figure 53
s...@figure53.com

[Chris Ashworth]

To be pedantic about it: OSC is not a text protocol, but we interpret text strings sent to this port according the same rules that we interpret text strings entered into the text box of the OSC cue, and translate them to OSC commands.

This is a bit like “Markdown for OSC” — human readable/writable text to easily translate to OSC.  I’ve taken to calling it “QSC” and will try to be more formal about documenting it.  The simple version is that you can enter the OSC method address, followed by the arguments to the method separated by white space. The argument type is inferred. If you want to send a string argument that contains whitespace, enclose it with quotation marks.

Example:

/path/to/an/osc/method followed by “some arguments” like 4 5 6.7