If you're here, you've probably spent time getting Tally Arbiter working — configuring Node.js, setting up the server, troubleshooting why the display devices can't connect, keeping the server machine awake during shoots. It works, eventually. But it's a lot of infrastructure to maintain for what should be a simple problem: tell the presenter when they're live.
This guide covers exactly what changes when you switch to Cue Light, what you give up, and how to be running in under 2 minutes.
What you're trading
| Step | Tally Arbiter | Cue Light |
|---|---|---|
| Installation | Install Node.js, npm, dependencies | None — open a URL |
| Server | Local machine must stay awake all shoot | Cloud — no server to manage |
| Networking | All devices must be on same LAN | Works on any internet — WiFi or cellular |
| Remote guests | Requires VPN or ngrok tunnel | Share a link — works instantly |
| Switcher integration | Automatic from vMix / OBS / ATEM | Manual tap per camera cut |
| Setup time | 30–90 minutes first time | 30 seconds |
| Maintenance | Node updates, config management | Zero — browser-hosted |
The honest trade-off: Tally Arbiter gives you automatic switcher integration — when you cut to Camera 2 in vMix, Camera 2's tally updates without anyone tapping a button. Cue Light is manual — the director taps when they switch. For most productions this is fine. For high-speed broadcast cutting, Tally Arbiter's automatic mode is genuinely better.
Who should switch
- You're running at different venues every week — venue WiFi is unreliable and you can't always run a server machine
- Your server machine sleeps or crashes — Tally Arbiter dies when the computer sleeps; Cue Light runs on Cloudflare's edge
- You have remote guests on Zoom — Tally Arbiter can't signal them without a tunnel; Cue Light works natively over the internet
- Your crew is non-technical — new volunteers or rotating camera ops can't be expected to configure network connections
- You switch cameras slowly — if you're not doing fast multi-camera cuts, manual tapping is zero overhead
Who should stay on Tally Arbiter
- Permanent studio where the server can always stay on
- Fast live switching where automatic tally from the switcher is essential
- You've already built and maintained the infrastructure and it's working
The 2-minute switch
If you're ready to try Cue Light, here's the full setup:
Open cuelight.io/app
Any browser — Chrome, Safari, Firefox, Edge. A room code generates instantly. No login, no install, no Node.js.
Share the QR code with your display devices
Tap "Show QR Code." Each camera operator or talent member scans with their phone. Their browser opens fullscreen display mode automatically. Wake Lock keeps the screen on for the entire shoot.
For remote guests — copy the display link
Tap "Copy Display Link" and paste it in Zoom or Teams chat. Remote guests open it in a browser tab. No install, no plugin — it just works.
Tap alongside your switcher
When you cut to a camera, tap Live (or press 1 on your keyboard). When you load the next camera in preview, tap Preview (or press 2). Standby is 3, Off is 0. Faster than it sounds after 5 minutes of muscle memory.
Running both during the transition
You don't have to choose on day one. Run Cue Light alongside Tally Arbiter for a shoot or two. Keep your existing setup as backup, and use Cue Light for any devices that are off your local network — remote guests, talent on cellular, or a second room. Once you're comfortable with the manual tap workflow, you can retire the local server entirely.
What Cue Light doesn't have (yet)
⚠️ Honest limitations
No automatic switcher integration — vMix, OBS, and ATEM tally states don't feed into Cue Light automatically. The director drives it manually. Multi-room management (monitoring multiple rooms from one dashboard) is on the roadmap but not live yet. If these are blockers for your workflow, Tally Arbiter remains the better choice.
Ready to make the switch?
Open Cue Light alongside your next shoot. 2 minutes to running, zero infrastructure to maintain.
Start free — no signup