Preview feature. Redundancy is in preview. It works, but the workflow and details may still change, and your feedback is very welcome. Please test it before relying on it in a live show.
What redundancy does
Redundancy lets you run two machines in parallel — a primary and a backup — so that if the primary fails, the backup is already loaded with the same project and already processing audio, ready to take over.
The primary is your main machine. It runs the show as normal and, in the background, mirrors its project state to the backup.
The backup loads whatever the primary sends and processes audio in parallel, staying in lock‑step with the primary.
If the primary goes down, you switch your audio path to the backup externally (for example, with an audio matrix/router switch). Because the backup is already in the right state and already processing, there is no reload or wait — the sound is already there.
Redundancy runs as a low‑priority background task. It is designed to stay out of the way: enabling it, pairing, and syncing do not change how the primary machine behaves or sounds.
Takeover is external
LiveProfessor does not switch your audio for you. When the primary fails, the app on the backup simply changes its status to "taken over" — it does not mute, unmute, or reroute any audio on its own. Promotion is a status change only. The physical/matrix switch that moves the live audio path from the primary to the backup will have to be made externaly, for example with a macro or snapshot in the audio mixer.