OSC triggering problem

[B]

Hi,

I'm trying to trigger QLab from ETC Eos and I have it working by sending a string directly from a cue (/cue/x/start) but I need to send it from a macro for my purposes.

If i try and send the same exact string from a macro it does nothing in QLab.

In the QLab logs it sees both osc messages, yet only acts on one of them?

Screenshot attached.

If anyone can tell whats going on from the logs and can help me out I would appreciate it massivley.

Thanks,

B

[Sam Kusnetz]

Hello B

In this screen shot it looks like you successfully triggered cue 3, then tried to trigger it again about four seconds later. Is that accurate? If so, is cue 3 longer than four seconds? By default, cues in QLab which are triggered while they’re already running will not do anything, so in this scenario if cue 3 is longer than four seconds it would make sense that your second OSC message had no apparent effect.

If that’s not the case, though, I think it’s possible we’ll need more information to troubleshoot. How does the macro assemble the OSC command? Is it just a hard-coded string, or is there some cleverness going on?

Best
Sam

––
Sam Kusnetz [he/him/his] (what is this?)
Figure 53
https://qlab.app | https://figure53.com

--
Contact support anytime: sup...@figure53.com
Follow QLab on Twitter: https://twitter.com/QLabApp
User Group Code of Conduct: https://qlab.app/code-of-conduct/
---
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/a4f9bb2a-465b-4ace-820e-3c8f6e99301fn%40googlegroups.com.

[Ben Smith]

Hi Sam,

Yes that screenshot was just for illustration, I triggered the cue, released it and tried to trigger again.

The macro is just "Send_String /cue/3/start🔸"

If there's some cleverness that should be going on and I don't know about it please let me know.

Thanks,

B

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/144f0429-53c4-4181-8c9d-2889ac16dcfa%40Spark.

[Richard Williamson]

I don’t think you should be using send string in EOS for this - or if you do you would need to send to the raw text port for qlab (I can’t remember what it is but I think it’s in the preferences)

Sent from my iPhone

On 15 May 2021, at 20:14, Ben Smith <fish8...@gmail.com> wrote:



To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/CACwaRAi3osrbFTMUdpT5JEyCofCa5gUHtbv%2BbQrn%2B8iFhL%3Deeg%40mail.gmail.com.

[B]

Okay thanks, the plain text port (53535) works. But what do you think I should be using instead of send string to send OSC from a macro?

Thanks very much

[Richard Williamson]

I’m actually not sure - I thought there was a better way but I think I may be wrong

---
Richard Williamson
www.richard-williamson.com
ric...@theatre.support
07957 457 362

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/d42753ae-7b4c-40f6-ba28-76183e33a440n%40googlegroups.com.

[Sam Kusnetz]

This points out something that many people have trouble with, including me for the longest time when i was new to OSC:

OSC messages are not text, and so simply writing the correct OSC out and sending it as text doesn’t work. An OSC message is encoded in a particular way. What “send string” does is just send the actual text that you enter across the network as text. It does not encode that text as an OSC message.

Port 53535 in QLab exists to deal with just this situation: it accepts plain text and then basically encodes it as OSC and then sends it to itself. If the text that was sent matches up to an OSC message, hey success.

So, honestly if using the “send string” method directed to port 53535 works, keep using it!

Best
Sam

––
Sam Kusnetz [he/him/his] (what is this?)
Figure 53
https://qlab.app | https://figure53.com

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/804FF4A3-E99F-416A-A57C-CF9A7B003B1D%40theatre.support.

[bobhad...@gmail.com]

You can send "straight" OSC from EoS to QLab pretty easily.  The EoS console will send an OSC message for EVERY cue (every time you press Go on the EoS you get an OSC message sent), and you can populate the cue numbers in QLab to match the EoS cue number, so you only trigger the ques that you want to trigger.  That also makes troubleshooting easier since the cue numbers line up.  If you don't want a QLab cue triggered by EoS either remove it's cue number or make sure it's number is outside the range of the cues that EoS is using.

You may know this part already but for anyone who doesn't (this is for the latest EoS release - earlier versions will differ slightly):

1. In EoS, tap Displays, then select Setup and System.
2. Select the Show Control tab on the left side and then the OSC tab along the top.
3. Make sure that OSC TX is enabled, set the OSC UDP TX Port to match the port in QLab that is listening (typically 53000)
4. Set the OSC Cue String field to "/cue/%1/start" so that EoS will populate the Cue Number in the "%1" placeholder and send that string to QLab
5. Set the OSC UDP TX IP Address to the IP address of the machine running QLab.  You can also leave this blank and it will broadcast the OSC, but I have found it's better to use unicast.  If you have OSC RX enabled on the EoS and the OSC RX settings happen to match the OSC TX settings, you'll get a loop within the EoS of it telling itself to Go on the same cue indefinitely.

That's pretty much it.  Use the VERY handy Workspace Status -> Logs window in QLab and enable "OSC input" to verify that the OSC messages are received and look like they should.  EoS has logging as well that you can use to verify it's sending the messages.

ETC has some good documentation for OSC on Eos:

https://community.etcconnect.com/control_consoles/eos-family-consoles/f/eos-family/18865/what-is-osc

https://support.etcconnect.com/ETC/Consoles/Eos_Family/Software_and_Programming/Triggering_Eos_from_QLab_using_OSC

Hope this helps.

Bob

[bobhad...@gmail.com]

Sorry about that - clearly I should not read email before breakfast, I lost the macro bit.

I'll try to reproduce it on an Ion tonight and see if I can see the same problem.

Bob

[bobhad...@gmail.com]

For what it's worth - I created a Macro on an Ion running Eos software 3.0.1, with "Send_String /cue/1/start" and verified that executing the macro triggers cue 1 on QLab 4.6.2.   I then created a second macro and verified that the triggers worked for multiple cues running simultaneously.  There does not appear to be any difference between the OSC generated automatically by the console and the OSC generated by the Send_String macros.

So whatever is causing the problem must be local to the QLab configuration and/or show file.

Bob

[Ben Smith]

Which port are you sending to in QLab, I had it working with plaintext but couldn't get TCP or UDP from a macro. It probably is something on my end though, I'll have another look at settings when I'm back at the desk.

You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/I2hBfBLtORo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/780ea978-69eb-4c23-b946-3c69a22bff62n%40googlegroups.com.

[bobhad...@gmail.com]

I'm sending to port 53000 in QLab.

Bob

[Cal W]

Hi all, I just had some very similar sounding issues.

After chatting with ETC It seems there is a bug (don't know when it appeared/ if it's been there forever) but it seems on EOS 3.2.5 at least. Send_string in macros do not work if they have an enter after them. A valid macro can only be:

Send_String /cue/45/start

with no enter diamond at the end.

This seems to be especially a problem in multi-console systems with a main and client.

If you need to run other things in the macro such as a wait, you need to essentially build a parent macro that then fires a clean macro with only the OSC message in it.

This may not be related to your issue but hopefully this is helpful to someone in the future.