Manual / How To
Move lights with ETC Eos
Live tracking from OpenFollow into ETC Eos: OpenFollow drives a Scenic Element Movable in Augment3D over OSC, and your moving lights follow it through a Track SEM focus palette.
Overview
Eos 3.3 introduced Augment3D Position over OSC, the only way to feed live tracking into an Eos console. OpenFollow ships with a built-in template that matches it. The tracked object lives in Augment3D as a Scenic Element Movable (SEM) – a channel you patch as scenery. OpenFollow’s OSC stream moves the SEM; moving lights aim at it through a focus palette set to Track SEM.
Prepare the console
On the Eos console, enable OSC RX:
- Go to Setup → System → Show Control → OSC.
- Set an OSC RX Port (e.g.
8000). - Turn OSC RX on.
- Note the console’s IP address.
One interface per subnet. Eos marks two network interfaces sharing a subnet as duplicates, and OSC arriving on a duplicate interface can be discarded silently, with no error and nothing in Diagnostics. If the console is listening but nothing reaches it, open Setup → Device → Network and disable the interfaces you are not using.
Set up the Scenic Element Movable
The tracked object lives in Augment3D as a Scenic Element Movable (SEM): a channel you patch as scenery, with your 3D object nested under it. Move the channel and everything nested under it follows.
- In Patch, create a channel and set its type to ETC Fixtures → Scenic Element → Scenic Element Movable. Pick a channel number you’ll remember – it is the marker ID OpenFollow addresses.
- Switch Augment3D to Edit mode and open the Hierarchy list.
- Drag your scenic object (a marker dot, a prop, whatever stands in for the performer or set piece) onto the SEM channel to nest it.
- The SEM’s position is now driven entirely from Eos – cue-to-cue, or live over OSC, which is what OpenFollow does next.
Create the destination and transmitter
In OpenFollow, go to Output → OSC Destinations → + New destination and set Host to the Eos console IP, Port to 8000 (or whatever you set on Eos), and Protocol to UDP. Click Save. See OSC Destinations.
Then go to Output → OSC Transmitters, pick ETC Eos in the Template dropdown, and click + New transmitter. Expand the new transmitter and set on the Basics tab:
- Name:
EOS Augment3D marker 0 - Default markers: the SEM channel number from the previous step
- Destination: the destination you just created.
The ETC Eos template
The template fills in the message; you can also type it yourself:
/eos/user/0/chan/[markerid]/xyz [x] [y] [z]
The [markerid] in the address must resolve to the SEM’s channel number – it selects which channel Eos moves. With a single SEM, set the transmitter’s Default markers to that channel. When your SEMs don’t start at 1, prepend a literal prefix instead: SEMs at 801, 802, 803 driven by markers 1, 2, 3 use 80[markerid], which renders 801, 802, 803.
Positions are metres on the same axes OpenFollow uses, and the template sends [x] [y] [z] unchanged. Height is the one value to check: [z] is measured from the OpenFollow origin and Augment3D measures from its own. If Camera & Grid → Grid → Offset Position sets a Z Offset, put the Augment3D origin at the same height or the object floats by that difference.
The message is addressed to Eos user 0, the background user ETC recommends for a continuous stream, so it stays off the operator’s command line. ETC Eos (User 99) is the same message under user 99 – pick it when user 0 is in use on the console.
Trigger
On the Trigger tab the template sets Trigger type = Stream, Rate (Hz) = 30 Hz, Send = Send always.
Stream rate cap: 30 Hz. Eos does not support Augment3D position updates faster than 30 Hz. Higher rates (60 Hz) get dropped by the console or trigger errors and packet loss. Keep the transmitter’s trigger at 30 Hz or below – Send only on change with a small Min change (m) threshold is also a good fit if your show doesn’t need the full 30 Hz.
Save and verify
Click Save and switch Transmitter on. Move the marker in OpenFollow; the SEM and everything nested under it should move in Eos’s Augment3D view. If not, open the transmitter’s Diagnostics tab: Live status → Recent events (see Diagnostics) lists the last sends with rendered addresses, plus skip reasons for unresolved placeholders.
One transmitter covers every marker: set Default markers to all and it sends one message per controlled marker, each addressed to its own channel. Add separate transmitters only when markers need different destinations or triggers.
Point your moving lights at it
A moving SEM only moves scenery – the movers don’t follow until you focus them on it. Eos does this with a focus palette set to Track SEM: any fixture using that palette re-aims at the SEM’s live position.
- Record a focus palette, or open one in Blind.
- Put the SEM’s channel number in the palette’s Track SEM column. A diamond in the palette label confirms it is tracking.
- Select your moving lights and apply the focus palette. They aim at the SEM and keep aiming as OpenFollow moves it.
- To light a face rather than feet, add an XYZ offset to the palette – the focus is taken relative to the SEM node.
For a one-off static aim instead, Shift-click the object in the Augment3D model (click-to-focus); it points the selected fixtures once but does not follow.
Troubleshooting
If positions arrive at Eos but the object sits at the wrong height, the Augment3D origin and the OpenFollow Z Offset (Camera & Grid → Grid) disagree. Set both to the same height.
- No position updates on Eos. Check OSC RX is on and the port matches. Confirm packets are reaching the console with a packet capture on its IP.
- SEM doesn’t move. The transmitter’s marker ID must equal the SEM’s patched channel number –
[markerid]addresses that channel. - SEM moves but movers don’t follow. The fixtures aren’t on a Track SEM focus palette, or the palette’s Track SEM channel is wrong.
- Errors / dropped packets at high rates. Drop to 30 Hz or lower.
- Object moves along the wrong axis or mirrored. The template sends X, Y, Z unchanged, so check the Augment3D orientation and origin against the OpenFollow grid rather than reordering placeholders.
Further reading
- ETC – Controlling a Scenic Object in Eos (patching and nesting an SEM).
- ETC – Palette Types (focus palettes and Track SEM).
- Video – Tracking Moving Objects with Scenic Element Moveables (Eos Augment3D).