New — Phoenix Pro option
Automatic switch to the backup PC

On-Air Failover
If the on-air PC goes down, the station stays on air

A second Phoenix workstation stands by next to the on-air PC. If the on-air PC stops — no more heartbeat, no more sound — the backup PC takes over on its own, right where the station was: the playlist, on time, with the stream. Only one workstation plays at a time, and every switch is logged.

On-Air Failover screen of the backup PC: this workstation has been on air since 15:07:32, the Studio PC is waiting, the database is the local read-only copy, and the switch log
The backup PC is on air. The on-air PC shut down at 3:07 pm: twenty seconds without a heartbeat, a silent off-air feed, and the backup PC took over on its copy of the database. The Studio PC, restarted, is waiting to take the air back.

For stations that cannot go silent

Any on-air PC can fail one day. What matters is how long the station stays silent.

🌙

Nights and weekends

Nobody in the studio: a PC that shuts down or a Phoenix that stops, and the station used to stay silent until someone arrived. The backup PC takes over on its own, with about 25 seconds of dead air at the default settings.

📋

Technical management

Every switch is recorded with its reason and time, on both workstations and in the Phoenix alert centre. Afterwards, you know exactly what happened.

🔧

Maintenance days

Updating or replacing the on-air PC: the air moves to the backup PC at the end of the current item, then comes back the same way, with 1 to 3 seconds of dead air.

An outage, from start to finish

The failover screen of each workstation, in the On-Air menu, shows who holds the air, since when and why, what the other workstation is doing and what the off-air feed hears.

Backup PC on standby: the Studio PC holds the air, last heartbeat 0 s ago, off-air feed with sound, main database
On standby. The backup PC does not play: it receives the Studio heartbeat every second and listens to the air. In its log, a network cable unplugged for two minutes: no switch, the air had sound.
Studio PC waiting: the backup PC has held the air since 15:07:32, button to take the air at the end of the current item
The Studio comes back, waiting. Once restarted, the on-air PC hears that the backup holds the air: it does not play, writes nothing, and offers to take the air back at the end of the current item.
Backup PC handing over: the other workstation requests the air, it will be handed back at the end of the current item
The handover. The request was confirmed in the studio. The backup PC finishes the current song, then hands the air back instead of playing the next one.
Studio PC back on air after the handover, backup PC on standby, full log of the switch
Back to normal. The Studio took the air back at 3:54 pm and the backup is on standby again. The whole sequence is in the log, to the second.

Screenshots of the actual Phoenix screen (French interface), on a demonstration scenario: two workstations, “Studio” and “Secours”, for the Chlonéo station.

Four steps, from the outage to the return

The two workstations watch each other; the air is monitored along a path that does not go through the network.

  1. Stand by

    The two workstations exchange a signed heartbeat every second over the studio network. The backup PC also listens to the air: a sound card input fed by the desk's programme output, or the station's stream.

  2. Detect the outage

    No heartbeat for 20 seconds and a silent off-air feed for 10 seconds: the on-air PC is down. A workstation that reports itself frozen and silent counts too. Both delays can be adjusted.

  3. Take over the air

    The backup PC takes over and writes it to its disk before playing. It resumes the playlist on time (GAP 0), on the studio database if it answers, otherwise on its local copy, starts the stream and raises the alert.

  4. Hand the air back

    The on-air PC, once back, waits. One confirmed action in the studio, and the backup hands the air back at the end of the current item; the Studio resumes on time.

One workstation on air, never a blind switch

A false switch would be worse than an outage: two workstations on air, or one cutting off the other. The rules are designed to prevent it.

🎧

No proof, no switch

A broken network looks like an outage. As long as the off-air feed hears sound, the backup does not play: it raises an alert. Without an off-air feed set up, it only switches if the on-air PC reports itself frozen and silent.

🔢

The most recent wins

Every takeover carries a number that only ever increases, written to disk before playing. A workstation that hears a more recent number than its own goes silent at once.

⏳

A restart is not a takeover

At startup, Phoenix listens for the other workstation for six seconds before playing. After a power cut, the backup PC gives the on-air PC 90 seconds to restart before any switch.

✋

Confirmed actions

Requesting the air must be confirmed; forcing it, only possible when the other workstation no longer answers, must be confirmed twice. None of these buttons has a keyboard shortcut.

🔐

A signed link

Messages between the two workstations are signed. A badly signed message, or one coming from an address other than the configured one, is rejected and reported.

📝

Everything is logged

Switch, handover, link lost or restored, silent off-air feed: every event is time-stamped in the workstation log and in the Phoenix alert centre.

The database and the media already on the backup PC

If the on-air PC shuts down, its database and disks go with it. The backup PC has kept what it needs to play what comes next.

🗄️

The database copied to the second

The station database is copied continuously to the backup PC, read-only. If the studio database no longer answers, the backup plays on this copy.

🧠

Even with no database

If neither the studio database nor its copy answers, the backup resumes from the playlist it already holds in memory: about 26 hours loaded in advance.

🧾

No play lost

What is played during the switch (playlist, royalty reports, proof of broadcast for commercials) waits on the backup PC's disk, then is replayed into the studio database at its real time.

💾

Six hours of media ahead

If the media library sits on the on-air PC, it goes down with it. The backup PC copies in advance what the playlist will play over the next six hours.

📡

The stream and the website follow

The stream, the now-playing title sent to the website and the royalty reports follow the workstation that holds the air: the backup starts its encoder when it takes the air and stops it when it hands it back.

🔌

Restart with nobody around

The Phoenix checker verifies, on each workstation, Windows automatic sign-in and the watchdog launched at startup, and reminds you of the BIOS setting that powers the PC back on after a power cut.

What the studio needs

On-Air Failover is set up once, on both workstations, in the Phoenix settings.

  • A second PC running Phoenix Pro, on the studio network
  • Its sound output on a second desk input, or on a silence-detecting backup switcher
  • The off-air feed: the desk's programme output into a sound card input of the backup PC, or the stream
  • A UPS for each workstation
  • Commissioning with Chloneo: settings, wiring, real switch tests
Failover settings: workstation role, station, address of the other workstation, heartbeat and silence delays, off-air feed from the sound card input, silence threshold

A Phoenix Pro option, quoted on request

On-Air Failover is added to Phoenix Pro, per station. It requires a second Phoenix workstation, which becomes the backup PC.

Request a Quote