Eos Scenic Objects Movable via OSC

204 views
Skip to first unread message

Alexander (Mailing List) Taylor

unread,
Apr 29, 2022, 7:34:57 AM4/29/22
to ql...@googlegroups.com
Hello,

I’m working with Augment3d in Eos, and am trying to change the position of an object via a Network cue.  I have confirmed the patches are correct, I can control other aspects of the cues and console.  I assume I have a syntax error.  Does anyone happen to see how to correct it?


My OSC message cue:
/eos/set/patch/801/augment3d/position=25.0,25.0,0.0,0.0,0.0,0.0

Thanks,
Alexander

The Right-To-Know Law provides that most e-mail communications to or from School District employees regarding the business of the School District are government records available to the public upon request. Therefore, this e-mail communication may be subject to public disclosure.

Sam Kusnetz

unread,
Apr 29, 2022, 9:09:02 AM4/29/22
to ql...@googlegroups.com
Hi Alexander

I’ve never used Augment3d but I do know that the way ETC and Figure 53 express OSC messages is slightly different, because the OSC spec doesn’t say exactly how to write out messages so everyone makes different decisions.

Try sending the message typed out EXACTLY this way:

/eos/set/patch/801/augment3d/position 25.0 25.0 0.0 0.0 0.0 0.0

Does that work?

In QLab, we separate the address from the arguments, and the arguments from each other, using spaces. We also enclose strings in double quotation marks, and we do not display argument type tags.

Best
Sam
—
Sam Kusnetz (he/him) | Figure 53



--
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/04653C30-2DE0-49F7-BDFB-CFB35632B66A%40orcsd.org.

Alexander (Mailing List) Taylor

unread,
Apr 29, 2022, 9:14:38 AM4/29/22
to ql...@googlegroups.com
Hi Sam,

That didn’t work for me unfortunately.  Here’s a screenshot of the incoming message in the diagnostic window.


Thanks,
Alexander


On Apr 29, 2022, at 9:08 AM, Sam Kusnetz <s...@figure53.com> wrote:

Caution - This email is from outside ORCSD. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Sam Kusnetz

unread,
Apr 29, 2022, 9:41:25 AM4/29/22
to ql...@googlegroups.com
Hi Alexander

Well, that screen shot does indeed confirm that you are sending the address followed by six float arguments.

If it’s still not working, either the message is not correct or something is misconfigured on the EOS side, preventing the message from arriving or preventing it from having its intended effect.

Sam
—
Sam Kusnetz (he/him) | Figure 53



Alexander (Mailing List) Taylor

unread,
Apr 29, 2022, 9:44:25 AM4/29/22
to ql...@googlegroups.com
Hi Sam,

That’s my conclusion as well.  I’l try giving ETC support a call once their main office is on the clock, and I’ll share my findings.

Thanks again,
Alexander


On Apr 29, 2022, at 9:41 AM, Sam Kusnetz <s...@figure53.com> wrote:

Caution - This email is from outside ORCSD. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi Alexander

Well, that screen shot does indeed confirm that you are sending the address followed by six float arguments.

If it’s still not working, either the message is not correct or something is misconfigured on the EOS side, preventing the message from arriving or preventing it from having its intended effect.

Sam
—
Sam Kusnetz (he/him) | Figure 53



On Apr 29, 2022 at 9:14:30 AM, Alexander (Mailing List) Taylor <ataylo...@orcsd.org> wrote:
Hi Sam,

That didn’t work for me unfortunately.  Here’s a screenshot of the incoming message in the diagnostic window.

<Screen Shot 2022-04-29 at 9.12.45 AM.png>

Alexander (Mailing List) Taylor

unread,
Apr 29, 2022, 10:48:21 AM4/29/22
to ql...@googlegroups.com
Hello,

I got some good info, and have a solution!  Here’s what ended up working:

Scenic Object Movable (panX panY panZ)
/eos/chan/801/xyz 10.0 10.0 0.0 - Note the values are in meters.

The “Scenic Object Movable” can only be repositioned in Live, not via patch.  Orientation cannot be changed in the same command.  You can use a “Scenic Object” and move/rotate it via the patch command.  The advantage of changing patch, it doesn’t affect recorded cues.

Scenic Object (panX panY panZ rotX rotY rotZ)
/eos/set/patch/802/augment3d/position 1.0 1.0 0.0 0.0 0.0 0.0

Now I cam move my virtual actors and sets around my virtual stage so I can really program offline.  Now if only QLab could output a HUD display so I could record the current state over a camera feed to reference!

I hope this info helps someone in the future.

Thanks,
Alexander

micpool

unread,
Apr 29, 2022, 10:57:00 AM4/29/22
to QLab
.  Now if only QLab could output a HUD display so I could record the current state over a camera feed to reference!

There are many work arounds to combine display of QLab parameters with the image from a camera. What would you want a HUD to show, whats your camera source and what are you recording to?

Mic

Sam Kusnetz

unread,
Apr 29, 2022, 11:33:42 AM4/29/22
to ql...@googlegroups.com


On Apr 29, 2022 at 10:57:00 AM, micpool <m...@micpool.com> wrote:
Now I cam move my virtual actors and sets around my virtual stage so I can really program offline.  Now if only QLab could output a HUD display so I could record the current state over a camera feed to reference!

What do want displayed? Text cues, Network cues, and OSC Queries can get quite a lot done here!

Alexander (Mailing List) Taylor

unread,
Apr 29, 2022, 11:42:22 AM4/29/22
to ql...@googlegroups.com
I’d like any OSC output, input, cue triggers, audio/video playback timing, etc.  I could overlay it on a camera feed of the stage and record it.  That way it would save me tons of time syncing things up to cue a show offline.

Thanks,
Alexander

On Apr 29, 2022, at 11:33 AM, Sam Kusnetz <s...@figure53.com> wrote:

Caution - This email is from outside ORCSD. Do not click links or open attachments unless you recognize the sender and know the content is safe.
--
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.

Sam Kusnetz

unread,
Apr 29, 2022, 11:53:15 AM4/29/22
to ql...@googlegroups.com
Hi Alexander

Well, that’s quite a lot of data. Here’s a much simpler example of a workspace which shows the cue name and number of the cue that’s standing by and the most recent cue that was started.

This demo runs the cue “pre” at workspace open which displays the text on screen and starts a very long running Network cue which live-updates the “standing by” indicator by tracking the cue that the playhead is currently sitting on.

When you hit the space bar, instead of directly triggering a GO, it starts a Timeline group which updates the “latest” indicator using the cue that’s standing by, then sends a “/go” message to the workspace.

Most of the rest of what you want is doable, although I encourage you to bear in mind that different folks program shows differently, and for some (like me), having an on-screen display of all current cue timing would either have to be too small to be useful, or too space-consuming.

Best
Sam

—
Sam Kusnetz (he/him) | Figure 53

HUD demo.zip

Alexander (Mailing List) Taylor

unread,
Apr 29, 2022, 12:01:49 PM4/29/22
to ql...@googlegroups.com
Hi Sam,

Thanks for the workspace, that’s very cool!  Does there happen to be a way to get OSC output displayed in a similar way?  I’d like it most for tweaking pre-wait times for OSC cues triggering my gio.

Thanks again,
Alexander


On Apr 29, 2022, at 11:53 AM, Sam Kusnetz <s...@figure53.com> wrote:

Caution - This email is from outside ORCSD. Do not click links or open attachments unless you recognize the sender and know the content is safe.
--
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.

Sam Kusnetz

unread,
Apr 29, 2022, 12:11:15 PM4/29/22
to ql...@googlegroups.com
Hi Alexander

What do you mean by “OSC output”? Are you talking about the OSC messages output by specific Network cues, or by all Network cues?

If so, there is not really a way to live-capture the output of Network cues from within QLab I’m afraid.

Best
Sam

—
Sam Kusnetz (he/him) | Figure 53



micpool

unread,
Apr 29, 2022, 2:44:58 PM4/29/22
to QLab
The main problem  with any OSC monitoring program, whether a HUD or anything else, is that OSC operates on a client server model. So it's difficult to sniff in the same way as MIDI. It's sent to a port and if that port's in use on your actual device you can't use that port for your monitor.

You can get round this by setting up port forwarding in your monitor app to your actual device. 

I've knocked up a quick proof of concept. OSC is sent to port 3535 which drives the HUD, and sends it out as a Syphon Video feed to layer up with your camera. It also forwards what it receives to the actual device, in the demo I'm assuming that is on port 8787 (Shown as an instance of OSCulator on that port) . For the purposes of the demo I'm compositing the syphon feed from the HUD app  over a webcam  in QLab 

OSC HUD.png

Screen recording attached.

Obviously to design a  practical HUD OSC monitoring system with multiple OSC network addresses and ports plus other information from QLab is a fairly major undertaking, particularly to provide it with an interface to make it customisable for every potential use, but this gives some idea of how it might be done.

Mic



OSC HUD.mov

Alexander (Mailing List) Taylor

unread,
May 2, 2022, 12:31:06 PM5/2/22
to ql...@googlegroups.com
Hi Mic,

Thanks for the demo, I had a very similar thought.  I was thinking of using OSCRouter as the proxy, and it would let me rewrite the OSC to a Live Text cue, lessening the burden on QLab.  Do you think that would work?


And to answer your previous question, I’m using an ATEM to overlay the output of QLab onto a camera aimed at the stage, recording to a HyperDeck.

Thanks,
Alexander


On Apr 29, 2022, at 2:44 PM, micpool <m...@micpool.com> wrote:

Caution - This email is from outside ORCSD. Do not click links or open attachments unless you recognize the sender and know the content is safe.
The main problem  with any OSC monitoring program, whether a HUD or anything else, is that OSC operates on a client server model. So it's difficult to sniff in the same way as MIDI. It's sent to a port and if that port's in use on your actual device you can't use that port for your monitor.

You can get round this by setting up port forwarding in your monitor app to your actual device. 

I've knocked up a quick proof of concept. OSC is sent to port 3535 which drives the HUD, and sends it out as a Syphon Video feed to layer up with your camera. It also forwards what it receives to the actual device, in the demo I'm assuming that is on port 8787 (Shown as an instance of OSCulator on that port) . For the purposes of the demo I'm compositing the syphon feed from the HUD app  over a webcam  in QLab 

<OSC HUD.png><OSC HUD.mov>

micpool

unread,
May 2, 2022, 12:46:06 PM5/2/22
to QLab
Possibly, but where would you get your clock reference and cue  timestamps from?

Alexander (Mailing List) Taylor

unread,
May 3, 2022, 8:05:01 AM5/3/22
to ql...@googlegroups.com
Hi Mic,

I would have OSCRouter as a proxy between the QLab machine and the console.  Any OSC sent to the Gio would be remapped and sent back to QLab to be displayed on the camera HUD.  Then QLab would still maintain the reference and such.

Alexander


Reply all
Reply to author
Forward
0 new messages