BeamBridge carries your console's universes to remote DMX nodes over any mobile or public network. Plug in a beam node on site, route universes from the browser, and watch the whole rig from one place — forests, trucks, stages, rooftops, wherever the show ends up living.
| GMA2 · sACN | beam-03online | beam-05online | beam-04offline |
|---|---|---|---|
| U1 p100 | →sACN p80 |
→sACN p80 |
|
| U2 p100 | →sACN p80 |
||
| U3 p100 | →sACN p80 |
||
| U4 p100 | →sACN p80 |
||
| U7 p100 | →sACN p80 |
Your console stays on its clean local network. A beam node on the far end turns whatever connectivity the location has into real sACN or Art-Net output, and the relay in between keeps every site in sync.
A source node next to the console uploads the universes you pick, once, through a single encrypted stream. The relay fans them out to every remote site. No VPN, no multicast tunnelling, no port forwarding at the venue.
A beam node with a 4G modem inside brings sACN and Art-Net to places with no wired network at all: forests, rooftops, trucks, moving practicals. Data usage is tracked per SIM in the dashboard, so you know what a show costs before it ends.
Where 5G is available, the same node gets lower latency and more headroom for larger rigs. Nothing changes in the workflow: the node uses the best uplink it has — Ethernet, WiFi, 5G or LTE — and fails over automatically when one drops.
sACN and Art-Net were built for local networks — multicast does not cross the public internet cleanly, and tunnelling it is fragile and wasteful. BeamBridge takes a different path: a source node listens on the console's network, captures the universes you choose and uploads them once. The relay distributes. Remote nodes re-emit a clean local stream on site — and a node on set can send a universe back upstream, into the console.
sACN is UDP multicast. The desk keeps multicasting on its own LAN exactly as it always does; the beam simply subscribes to the universes you route and uploads them on its own uplink. Nothing is installed on the console, and if the desk network must stay off the internet, it does — the beam's 4G is the only way out.
Where there is no mobile coverage at all, the node uplinks through a Starlink terminal on site. Same workflow, same dashboard; the relay does not care what the last mile is.
If the console network already has fast wired internet, the beam can use that as its uplink instead of the modem, for the lowest possible latency. It picks the best link it sees and falls back to 4G if the wire goes away.
These are real screens from nodes on live productions — telemetry, signal routing, and per-node config, watched from one place over the network.
BeamBridge has been running on live productions for months and has proven very reliable. With normal mobile coverage the experience is practically the same as controlling fixtures locally over CRMX: the desk operator does not notice the WAN, and neither do the lights. And because every node sees its own network, the dashboard doubles as remote eyes on the rig: RDM, Stardust, LAN scan, sACN monitor.
We use BeamBridge on our own shoots, so every feature has been through a real call sheet. We are flexible about setups — protocol, universe numbering, uplink, where the nodes sit — and we keep simplifying and optimising the workflow with every production, because it is our workflow too.
The same node carries more than DMX. OSC output is live — sACN channels mapped to faders on a local console or a Blackout iPad — and a Zigbee bridge drives practicals such as smart bulbs straight from a universe. Both are in production use and still growing. Zigbee notes · OSC notes
On one shoot a small desk next to the DoP sent sACN upstream to the main console. The console digested it and handed the faders the operator had selected to the DoP and the gaffer, on the fly, from the DIT tent. Remote control that goes both ways.
A compact console of our own with motorised faders that sits on a beam node and sends ready-to-use data straight to the main desk — or over OSC to a Blackout iPad. Designed for the person standing next to the camera, not the one at the desk.
Want to try it on your next production? Tell us about the job and we bring the nodes.
— get in touch · [email protected] · all field notesStart with the protocols you already run on real productions. A source node listens locally and forwards the universe ranges you pick.
The source uploads a single stream. The relay fans it out, so uplink bandwidth at the desk does not multiply with each output node.
Each output subscribes only to the universes it needs — 1–4, 1–10, or whatever the rig calls for. Click a cell to route, click again to drop.
The protocol on the sending side does not have to match the receiving side. If the desk only streams sACN but a node or device on the far end only speaks Art-Net, the core translates and the remote beam emits Art-Net — or vice versa. Your hands are not tied by what either end happens to support.
Universe numbers can be changed on the way through. What goes up as U18 at the desk can come out as U69, or U1, or whatever the rig on the far end is configured for — per node, per output, from the same routing matrix.
Stream activity, node health, and universe-level diagnostics, surfaced live — so the field stays visible from wherever you are.
Full RDM (E1.20) handling on every node's DMX port and through drivers for RDM-capable network nodes (Netron, Swisson, Showtec NET-2). Discover fixtures, set DMX address, personality, label and curve, and edit every manufacturer parameter — over the internet, from the dashboard. More is coming on this line.
A Stardust driver is built in: if a Stardust is on the segment it shows up on the dashboard by itself, more than one if there are more, with its ports and settings editable and the CRMX fixtures it knows listed on its card.
One click sweeps the node's local network and lists every device on it — DHCP or static, even hosts that hide behind a firewall — with a per-device port check. Know what is plugged into the set network without walking there.
Every beam watches the full sACN range around it and shows the sources it sees, live. Open a universe and read the value of every channel — the fastest way to check what a console is actually sending, from anywhere.
Not on its own. sACN is multicast UDP designed for a local network, and routers on the public internet drop it. BeamBridge captures the universes you choose at the source, carries them over a single encrypted stream, and re-emits real sACN on the remote network. Your console and your fixtures never know a WAN was involved.
Yes. A beam node ingests Art-Net or sACN locally and uplinks it through its built-in 4G/LTE modem, or over 5G, WiFi or Ethernet when those are available. It picks the best uplink it has and fails over automatically. The output node emits sACN or Art-Net again on site.
No. OSC output and a Zigbee bridge are implemented and in use on productions. Full RDM runs on the node's DMX port and through drivers for RDM-capable network nodes, so fixtures can be addressed and configured from the dashboard; an Astera Stardust on the segment is detected and configurable; a LAN scan lists every device on the set network and a live sACN monitor shows sources and per-channel values. The same link works upstream too: a small desk on set can feed sACN back into the main console. See the field notes.
Yes, both. The core translates between sACN and Art-Net in either direction, so a desk that only sends sACN can drive a node that only understands Art-Net, and vice versa. Universe numbers can be remapped per output as well: universe 18 at the desk can come out as universe 69, or 1, or whatever the far end needs. We are flexible and will set it up around your rig, not the other way round.
It depends on frame rate and on how many universes you route, so BeamBridge tracks it for you: the dashboard shows live data usage per SIM and per billing cycle. Only the universes you actually route leave the source, so a few universes fit comfortably in a normal mobile data plan.
On LTE, end-to-end latency is typically well under a tenth of a second; on 5G or a wired internet uplink it is lower. With normal coverage it feels the same as controlling fixtures locally over CRMX. For a tightly timed pixel show keep that part of the rig on the local network and use BeamBridge for everything that is out of reach.
Beam nodes for the production (DMX out, 4G inside, ready to plug in), the relay core, the web dashboard with routing and monitoring, and people who watch the fleet with you during the show. Pricing is per production. Tell us about the job and we will quote it.
BeamBridge runs on real productions today. If your show keeps ending up somewhere the network doesn't reach — or you simply want to try it — tell us about the job and we'll quote it.
Live events, film, broadcast — sACN and Art-Net over LTE, 5G and the internet, watched from one place. Want to try it? Say hello.
[email protected]