Why a station carries a high and a low feed
One bitrate is always a compromise. Set it high and a listener on a train or a thin mobile plan hears buffering and burns data. Set it low and the listener at home on good speakers hears a flat, smeared mix. Two or three feeds of the same programme remove the compromise: the audience picks the version their connection can hold.
- A full feed for desktop players, smart speakers and home hi-fi, where bandwidth is rarely the limit.
- A standard feed for most phones and car apps on a decent signal.
- A light feed for weak coverage, metered data and talk segments where voice clarity matters more than detail.
The cost sits in two places: each extra feed needs its own encode somewhere, and each listener consumes the bitrate of the feed they opened, nothing more.
How a listener lands on one stream
On Icecast, every stream lives at its own mountpoint, a name on the server such as /radio.mp3 or /radio.aac, and a listener is connected to one mountpoint at a time. Each mount carries what its own source client sends it. Three things decide which feed a person hears:
- The link they were given. A directory entry, an app or a share button points at one mount. Label your links plainly, for example "high quality" and "mobile".
- Your player. A web or app player can offer a quality choice, or open the lighter address on a phone. The player on our radio plans has a data saver for mobile listeners.
- Fallback, when a source drops. Icecast's
fallback-mountsetting moves listeners to another mount if the source on theirs shuts down, andfallback-overridelets them move back when it returns.
SHOUTcast DNAS 2 works the same way with numbers instead of names: each stream on the server has a stream ID, listeners reach stream 1 at the root path and stream 2 at /stream/2/ (and so on) unless you give them a custom path, and a per-stream listener cap sits inside the server-wide one.
Automatic switching mid-play is a feature of HLS, where a master playlist lists each variant with a required BANDWIDTH attribute and the client changes variant as conditions change. An Icecast or SHOUTcast listener stays on the feed they opened until they reconnect. If you also run live video, that is where HLS applies.
A bitrate ladder to start from
Start from what your format needs, not from the highest number. These are starting points; audition each on the devices your listeners use and keep the lowest rate you accept.
| Feed | Bitrate | Good for |
|---|---|---|
| Full | 320 kbps, the most a stream on our plans carries | Music on home speakers and desktop players |
| Standard | 128 kbps, which sounds good for music on any device | Most phones, car apps, smart speakers |
| Light | 32 kbps suits talk; for music, audition rates between the light and standard rows | Weak signal, metered data, spoken word |
Delivery is plain multiplication. Two hundred listeners on the standard feed take 200 × 128 = 25,600 kbps, about 25.6 Mbps. Moving half of them to a 32 kbps feed cuts that half from 12,800 to 3,200 kbps.
Your studio upload is the other sum. If one computer encodes all three feeds above, it sends 320 + 128 + 32 = 480 kbps continuously, and it needs headroom on top of that so a busy home network does not starve the stream.
What each radio plan carries
Multiple feeds are a Platinum feature on our HTTPS radio streaming plans. The free plan and Premium each carry one stream; Platinum carries three, so phones get a lighter bitrate while the main feed runs at up to 320 kbps.
| Plan | Streams | Highest bitrate |
|---|---|---|
| Free | 1 | A talk-grade rate |
| Premium | 1 | 128 kbps |
| Platinum | 3 | 320 kbps |
- Every stream is served over HTTPS, so the player embeds on secure websites without mixed-content warnings, and a plain-http copy is kept for old players.
- On Platinum, listeners and your encoder connect to whichever of five delivery cities is nearest, three in the United States and two in Europe.
- Premium and Platinum include a browser-based studio encoder that sends up to 256 kbps, with audio processing and an alert when the feed goes silent.
Setting up the extra streams
- In your control panel's Radio section, find the listen link for each stream and the encoder settings for your station. On Platinum, the extra streams give phones a lighter bitrate; ask in live chat or a ticket whether any of them needs a source connection from you before you set up extra encoders.
- Your encoder's bitrate must not exceed the highest one your plan carries (a talk-grade rate on Free, 128 kbps on Premium, up to 320 kbps on Platinum).
- On an Icecast or SHOUTcast server you manage yourself, every extra mount needs its own encode: either run one encoder instance per feed (each with its own server profile), or use playout software that sends one source to several outputs.
- Start your main feed and play its listen link on a desktop browser; then play each lighter stream's link on a phone.
On a self-managed server, Liquidsoap is one playout tool that does the second option natively: its documentation states that a single source can feed as many outputs as you want, encoded separately for each output while the source itself is computed once. This is the documentation's own example, trimmed to two of its three outputs:
radio = mksafe(playlist("~/music"))
output.icecast(
%mp3(bitrate = 128),
host="icecast.example.org",
password="hackme",
mount="/radio.mp3",
radio
)
output.icecast(
%fdkaac(bitrate = 64),
host="icecast.example.org",
password="hackme",
mount="/radio.aac",
radio
)
Replace the host, password and mount values with your own server's, and keep the script readable only by your own user (chmod 600), since it holds your source password. For an encrypted connection the same documentation adds transport=http.transport.ssl() and the TLS port to each output. If your Liquidsoap build reports the AAC encoder as unavailable, use a second %mp3 output at a lower bitrate.
Checks before you announce the new feeds
- Each encoder shows it is connected, to its own mount or stream ID, at the bitrate you set rather than a default.
- Each listen link plays both in a desktop browser and on a handset away from Wi-Fi, carrying the same programme in step.
- Song titles update on every feed, not only the main one.
- Your listener statistics show people arriving once you share the new links.
- Your studio upload stays steady with all encoders running; watch it for ten minutes during a busy part of the day.
When a feed misbehaves
| Symptom | Likely cause | What to do |
|---|---|---|
| The light feed connects, the full feed is refused | Wrong host, mount, stream ID or password on that profile | Copy the settings again from the control panel, field by field |
| Every feed drops at once | The studio upload is saturated by the sum of all encodes | Run fewer local encodes, or move encoding to a machine with more upload |
| One feed is silent while the others play | That encoder instance lost its input device | Check the input selection in that instance, not the others |
| Phone listeners still pull the full feed | Your links or player point every device at one address | Publish a clearly labelled mobile link and use the player's data saver |