Radio stream fallback source: a chain that keeps your station on air

A radio stream fallback source is whatever your server plays the moment the live encoder disconnects: another mountpoint, an AutoDJ playlist or a looping file, so listeners hear programme instead of a dropped connection. This guide sets out each link in that chain, the Icecast settings behind it, the one failure a fallback cannot catch, and the checks that prove it works before a DJ ever loses their connection.

Steps
7
Reviewed
Runs on
Radio
Written by
Get Stream Hosting

By the Get Stream Hosting team

Every step was checked against the software's official documentation by independent reviewers before publishing. Last reviewed .

Pre-flight check

The fallback chain, layer by layer

A station that stays up has three layers stacked behind the main signal. Each one only plays when the layer above it is gone, and each one hands back when the layer above returns.

LayerWhat playsWhat hands it the air
1. Live sourceA DJ or studio encoder (BUTT, Mixxx, SAM Broadcaster, RadioBOSS)The DJ connects
2. AutomationAutoDJ playing your library and scheduleThe live source disconnects
3. Last resortA fallback playlist, or a looping file on a self-run serverAutomation has nothing to play

Without layer 3, a gap in automation still ends in listeners being dropped. Without layer 2, every encoder hiccup does. Most stations need all three.

Silence is not a dropout

A fallback only fires when the source connection ends. Icecast moves listeners to the fallback mount when the source shuts down or is not streaming; an encoder that stays connected while sending a muted channel still holds the mount, and your audience hears nothing.

Close that gap at the encoder. BUTT can disconnect itself when the input goes quiet: tick Stop if signal is absent for [...] seconds and enter a whole number above 0. Its signal detection levels default to -50.0 dB and are set separately for present and absent signal in the Audio tab. Once BUTT drops the connection, the server's fallback takes over.

Pick a stop time longer than any deliberate pause in your programme, such as a dramatic beat in a drama or a minute's silence on Remembrance Day. Too short and the automation will cut into a planned quiet moment.

Setting it up on a hosted station

On our SSL radio streaming plans, the fallback layers come with the plan rather than as config you write. On Premium and Platinum, AutoDJ runs your uploaded library day and night and yields as soon as a DJ comes on. Both plans also carry a fallback playlist for when nothing else is playing, handover from automation to the DJ and back again, an emergency cut, and alerts for dead air. Platinum goes further with a standby slot, a backup source and DJ changeovers without a gap.

  1. Upload enough music to the AutoDJ library to cover your longest unattended stretch, and build the schedule.
  2. Build the fallback playlist from tracks that suit any hour, with no time-specific station IDs or dated promos in it.
  3. Give each DJ their own account; on Premium each one is limited to their own slots.
  4. Set each DJ's encoder with the server details from the control panel. In BUTT, add the server under settings with its address, port and password. Turn on the silence stop described above.
  5. Point the dead-air alerts at an address you watch, so a silent air reaches you, not just your listeners. If you broadcast from the browser studio, its encoder also warns you when the air goes silent.

Confirm it: with a test listener playing, connect a DJ, then stop the encoder. The audio should switch to AutoDJ and the listener count should hold rather than fall to zero. Reconnect and the DJ should be back on air.

Settings to copy on a self-run Icecast server

If you run Icecast yourself, for example on one of our cloud servers, the chain lives in the mount blocks of icecast.xml. Each mount may name only one fallback, and it should be another mountpoint on the same server in the same streaming format. A fallback mount that is not streaming but has its own fallback passes listeners down the line, so mounts can cascade.

<mount type="normal">
    <mount-name>/live</mount-name>
    <fallback-mount>/autodj</fallback-mount>
    <fallback-override>1</fallback-override>
</mount>
<mount type="normal">
    <mount-name>/autodj</mount-name>
    <fallback-mount>/standby.mp3</fallback-mount>
    <fallback-override>1</fallback-override>
</mount>
  • fallback-override set to 1 lets a returning source on that mount pull listeners back from the fallback. Without it they stay on the fallback.
  • A fallback can be a file in webroot, here /standby.mp3. It repeats until the listener leaves or a stream comes back and takes them back. Encode it in the same format as the stream, or playback may break.
  • A file fallback is not timed. It is fine on a relay's slave streams, but do not use one on a master stream that relays read from: the relay consumes it too fast and its listeners are eventually dropped.
  • fallback-when-full set to 1 sends new listeners to the fallback once the mount reaches its max-listeners count.
  • source-timeout, in the limits section, is how many seconds a connected source may send no data at all before Icecast removes it. The reference example uses 10.

Copy icecast.xml aside before editing; Icecast's own documentation asks for a backup of a working config first. Run xmllint icecast.xml to catch XML mistakes, and read the Icecast error.log if it refuses to start. Most mount settings apply when the config is re-read, but some only take effect when a stream starts or ends.

Checks before you go live

  • Pull the encoder's network cable mid-song. The listener should hear AutoDJ, not silence and not a dropped player.
  • Mute the encoder's input instead. After your silence-stop time the encoder should disconnect and automation should follow.
  • Stop AutoDJ, or on a self-run server stop the /autodj source. The fallback playlist or file should play.
  • Reconnect the DJ. Listeners should return to the live show without pressing play again.
  • Check that alerts arrive: an off-air email or a dead-air alert should reach the address you watch at night.

When it goes wrong

  • Dead air, encoder still shows connected. The source is sending silence. Fix the input, then enable the silence stop so it cannot happen unnoticed again.
  • Listeners dropped instead of moved. On self-run Icecast, the fallback mount was missing or not streaming, and had no fallback of its own.
  • Fallback plays, but the DJ never comes back on air. fallback-override is off for the live mount.
  • Garbled or stalling audio on the fallback. The file or mount is in a different format from the main stream.
  • AutoDJ plays a dated promo at 3 a.m. Rebuild the fallback playlist with timeless material.

Still stuck on a hosted station? Open a ticket or a live chat. Chat runs around the clock; its AI assistant can look into your account, and you can ask for a person whenever you like.

Where each plan stops

Free is a live-only plan: one stream from your own encoder, with neither AutoDJ nor a fallback playlist, so when your encoder stops there is nothing scheduled to take its place. Off-air email alerts come with every plan, Free included, so an outage still reaches your inbox. If your station must stay up overnight or between shows, you need a paid plan.

Fallback covers the source, not delivery. Platinum spreads listeners and your encoder across five cities, picking the closest. A health check runs on every server each 10 seconds; two failures running sends fresh listeners on to the next-closest city. Free and Premium stations are served, and receive their encoder, from the single server that hosts them.

Questions people ask

Does AutoDJ take over automatically when my DJ's connection drops?

On Premium and Platinum, yes. Automation fills any hour with no one live, gives way when a DJ logs on, and picks the air back up once the DJ leaves. Test it once by stopping the encoder while you listen.

Why did my station go quiet without switching to the backup?

Because the encoder never disconnected. A fallback starts when the source connection ends, and an encoder sending silence still holds the mount. Set your encoder to stop when the signal is absent, as BUTT can, and keep an eye on dead-air alerts.

Can an Icecast mount have more than one fallback?

Each mount names only one fallback, but that fallback can name its own. If the first fallback is not streaming, listeners cascade to the next, which is how a live, automation and file chain is built.

What is the difference between the fallback playlist and the Platinum backup source?

The fallback playlist, on Premium and Platinum, keeps music playing when nothing else is on air. Platinum also lists a backup source, gapless DJ handoff and a standby slot. The full feature table on the radio page shows which plan carries each.

Will listeners have to press play again when the live show returns?

Not if the return is handled on the server. On self-run Icecast, fallback-override on the live mount moves listeners back when the source reconnects. On a hosted paid plan, automation gives way on the station's own stream as the DJ connects, so listeners keep the same listen link.

Radio

Put your stream on air with a fallback behind it

Choose a radio plan with AutoDJ and a fallback playlist, connect your encoder, and run the checks above before your first show.