Show automation for live production
Do this when that happens.
LiveLogix watches your console, your wireless and your playback — and makes them respond to each other. You write the rule once, in plain language, and it holds for every show after that. No scripting, no scene-by-scene babysitting.
Native macOS app. Built by people who mix shows.
Currently −38.2 dB — above the threshold
Use cases
The jobs nobody should be doing by hand at 1am.
Every one of these is a rule you build once and stop thinking about. They run the same way at rehearsal, at doors, and on the night when everything else has gone wrong.
Mics that get out of each other's way
The lectern stays open all night, so it opens up the room every time the presenter walks away from it. Let the handheld tell it to sit down.
When Handheld 4 unmutes
Then Lectern fades −12 dB
Back Lectern returns when it mutes
Cues that hit on time, every time
Timecode runs the video, so let it run the desk too. LiveLogix reads incoming LTC and fires on the frame instead of on a stage manager's cue light.
When Timecode reaches 01:14:30:00
Then Recall Scene 12, fire the QLab cue
RF trouble you hear about early
A battery that dies in the keynote was flashing a warning twenty minutes earlier. Put that warning somewhere you'll actually see it.
When Any pack drops below 30 minutes
Then Light the Companion button red, flash the screen
Rules that listen to the audio itself
Not just what's muted — what's actually there. LiveLogix reads the desk's real metering, so a rule can respond to signal instead of to a guess.
When Aux 1 is above −20 dB for 2 seconds
Then Duck the walk-in music
One key, the whole rig
A softkey on the surface, a Companion button, or a cue in QLab — any of them can be the trigger, and any of them can be the result. The room moves together.
When Softkey 9 is pressed
Then Recall a scene, press a Companion button, start a cue
Tempo that reaches the desk
Not just a number on screen — LiveLogix reads a live click off any audio input and keeps the console's own tap tempo in step with it, continuously.
When The click track is running
Then Set dLive tap tempo to match
What it talks to
It speaks to the gear already in your rack.
Rules cross between them freely — a wireless mic can move a console fader, and a console softkey can start a cue. One rule, several boxes.
Allen & Heath dLive
Faders, mutes, sends, pan, scenes, DCAs, softkeys — and live metering, so rules can follow the audio and not just the switches.
ConsolesShure wireless
Axient Digital, ULX-D, QLX-D and SLX-D. Battery, RF, audio level and mute state, watched continuously across every channel.
RFBitfocus Companion
Press any button on your Stream Deck layout from a rule, so the automation shows up where your operators already look.
ControlQLab
Start, stop and follow cues, so sound playback and console state stay in step without a human keeping them there.
PlaybackDante
Subscription health, clock role and drift, watched per device — so a rule can catch a network audio path going quiet before an operator hears it happen.
Network audioMIDI
Any class-compliant device can trigger a rule or receive one — notes, CC, program change — wired into the same engine as the console and the wireless.
ControlClear-Com Arcadia
Intercom talk, listen and key state reads into rules the same way a console channel does, so the panel and the desk can react to each other.
IntercomTimecode
Reads LTC or MTC straight off an audio input. Rules fire on a frame, and the incoming time is on screen the whole time.
SyncBuild it before you load in
Import a show file, or set up a virtual console, and write the whole rule set at your desk — against the buses the rig will actually have.
OfflineTimeline
Record the moves. Keep them forever.
Arm a track and do the thing on the desk — fader rides, mutes, scene recalls, all with their real timing. Play it back on its own, or let a rule start it.
Always there, never a ritual
The timeline is up the moment you open a session. Arm a track and the next move you make on the desk is on it — no separate "start recording" step.
Overdub instead of redoing the take
Layer a fix on top of a good recording rather than re-performing the parts that were already right.
Knows a scene fade from a live move
A scene recall's own crossfade isn't captured as if you'd ridden the fader by hand — playback matches what you actually did, not what the desk did on its own.
A rule can start the take
Timecode, a softkey, a Companion button — anything that can trigger a rule can kick off a timeline, the same as any other action.
Redundancy
The show doesn't stop because a laptop did.
Run a second machine as a backup. It mirrors the whole show, watches the same desk, and takes over on its own if the first one goes quiet.
Takeover in under a second
The backup promotes itself the moment the primary stops answering — and instantly, not after a timeout, when you hand over deliberately.
It tells you if it isn't ready
A backup that can't reach the desk, or hasn't caught up on config, says so before it's needed rather than at the moment it matters.
No accidental second driver
Close the main machine and it asks what the backups should do. Reopen it after a failover and it asks whether it's taking the show back.
You always know which is which
Every machine says its role in a bar you can read across a dark room. Nobody edits the show on the box that isn't driving it.
How it works
Five plain steps. No scripting.
Two real ones, built the way you would build them — no scripting, no node graph. Pick a rule, then scroll: each step fills itself in, and the whole thing runs live, right here.
When this happens
Talkback input rises above −60 dB
Currently −38.2 dB — above the threshold
Only if…
OptionalThe talkback input is unmuted
Then do this
Flash the screen
On the way back
OptionalStop flashing when talkback drops away
Re-fire only after…
OptionalThe talkback closes again
Write the rule once. Trust it every night.
LiveLogix is in active development, shaped by real shows and built by people who mix them.