A few years back, I used to be able to send a UDP string like this:
<U2>Edit_Target Label Cue 90000 1 -1 House Out
And it would label Cue 1/9 "House Out"
But now that no longer seems to be working. Was this removed on purpose? Is there a different/new way to label cues via UDP?
It also seems like
<U2> $ Blind #
is no longer working either, when it used to.
Thanks so much for these replies a while back Matt Pumplin ! Super helpful!
Another UDP string which I think should be working but are not:
<U15> $ Cue 1/19 Time_Code 04012314 #
This gives me a Command Line like this:
If I do
<U15> $ Cue 19 Time_Code 04012314 #
It seems to work. But shouldn't I be able to specify the cue list?
I also tried sending an OSC string as a UDP string as in your Blind example and wasn't able to get it to work.
I tried
/eos/cmd="Chan 1 At 75#"#
And in the Diagnostics tab. I see:
OnyxConsole 2025-06-17 23:41:41.549 RecSerial [10.0.1.34:49573] "/eos/cmd=\"Chan 1 At 75\r"
But the command line doesn't get populated.
Also tried
/eos/cmd="Chan 1 At 75"#
and
/eos/cmd="Chan 1 At 75#"
None seem to actually popular the command line.
Is there anywhere where ETC documents all strings that should be valid so I don't have to be guessing? Been looking around and having trouble finding anything.
jakedeg you actually found the answer a couple of years ago - put a space around the '/' which separates the Cue List from the cue: Creating cues via UDP String
So, it would be <U15> $ Cue 1 / 19 Time_Code 04012314 #
I see what you mean about the channel level not being set. This works for me: /eos/chan/1=75#
or <U15> $ Chan 1 at 02#
I generally refer to the User Manual pages for these things, then play around: Receiving Eos Serial Commands – RS232, UDP, and ACN Strings
OSC commands are here-ish: OSC Channel
And as a fallback, I check out the tooltip for the Command box in Magic Sheet Editor:
We are working to improve the documentation around OSC strings for the next major release, v3.3.0. UDP strings generally just follow the format you see and use the target console's language (So if your console is set to French, you must type
<U15> $ Circ 1 @ 15# , Circ instead of channel.
jakedeg you actually found the answer a couple of years ago - put a space around the '/' which separates the Cue List from the cue: Creating cues via UDP String
So, it would be <U15> $ Cue 1 / 19 Time_Code 04012314 #
I see what you mean about the channel level not being set. This works for me: /eos/chan/1=75#
or <U15> $ Chan 1 at 02#
I generally refer to the User Manual pages for these things, then play around: Receiving Eos Serial Commands – RS232, UDP, and ACN Strings
OSC commands are here-ish: OSC Channel
And as a fallback, I check out the tooltip for the Command box in Magic Sheet Editor:
We are working to improve the documentation around OSC strings for the next major release, v3.3.0. UDP strings generally just follow the format you see and use the target console's language (So if your console is set to French, you must type
<U15> $ Circ 1 @ 15# , Circ instead of channel.
