The two servers, line by line
Read the table as a run sheet. Each row is a question you will meet when you set up an encoder, a player or a directory listing.
| Question | Icecast | SHOUTcast DNAS |
|---|---|---|
| Licence | Open source, GPL v2 | Free from the vendor (formerly called DNAS) |
| Audio formats the project names | Ogg Vorbis, Opus, WebM, MP3 | MP3, AAC |
| Several streams on one server | Mountpoints, each a path such as /live | Stream IDs, whole numbers starting at 1 |
| Now-playing titles | Carried in the stream; non-Ogg titles read as Latin1 unless a charset is set | Accepts 2.x XML metadata or 1.x plain titles |
| Directory | Any YP directory you configure, for example the Xiph one | SHOUTcast Directory, which needs an authhash and version 2.5 or newer |
| Default port in the documentation | 8000 | 8000, and the next port up for 1.x sources |
| Old SHOUTcast 1.x encoders | Accepted on a dedicated port pair if the server enables it | Accepted for any configured stream since 2.4.7 |
Neither server makes the audio sound better. If you also broadcast video, live video streaming takes RTMP from your encoder and plays it as HLS in any browser. Quality is set by the encoder: its codec, bitrate and sample rate. The server only copies what it receives.
Licence and who controls the software
The Xiph project licenses Icecast as GPL v2 software. You can read the code, build it yourself and change it. If you run it yourself and want HTTPS, the Icecast documentation enables it per listening socket with a tls setting, provided the binary was compiled against OpenSSL.
SHOUTcast's server software, formerly known as DNAS, is free to run on your own machine, according to the vendor's pricing page. The vendor also runs an advertising programme, Targetspot, which injects locally targeted audio ads into streams on the server side. On a hosted station you never touch that decision. Get Stream Hosting puts no advertising into any station's stream, whatever the plan.
How the song title reaches the listener
Titles travel inside the stream on both servers, and that is where most "wrong song showing" complaints start. The encoder or playout software sends the artist and title; the server passes them to every player that asks.
- Icecast: for MP3 and other non-Ogg streams, Icecast's documentation says the title often has no declared character set, so it assumes Latin1 unless the mount sets another one. Accented names turning into odd symbols usually point here.
- Icecast: any program holding the admin or mount credentials can push a new title through the
/admin/metadatafunction; the documentation names source clients and external programs as the callers. - SHOUTcast DNAS 2: its title update accepts the richer 2.x XML metadata or a plain 1.x title. The interval of in-stream titles only applies to 1.x-style listeners that ask for it.
- Both: if the title never changes, check what the encoder or playout software is sending before you look at the server.
Several streams from one station
Running a full-quality stream beside a lighter one for phones is the common reason to need more than one feed. The two servers name them differently, and your encoder settings follow that naming.
- Icecast mountpoints. Each stream is a named path on the same address. A listener joins one mount at a time. A
fallback-mountcan move listeners to another mount when its source drops, andmax-listenerscaps a single mount. - SHOUTcast stream IDs. Each stream gets a number. A 2.x encoder has a Stream ID field. An old 1.x encoder has none, so the DNAS documentation has you add it to the password as
password:#2for stream 2, which is why a colon cannot appear inside a password. - On our radio plans. Free and Premium carry one stream. Platinum carries three, letting mobile listeners pick a smaller feed. The plan table on the SSL radio streaming page has the listener and bitrate figures for each.
Getting found in a directory
Directory listing is the clearest practical split between the two. Each engine reports to its own family of directories, and each needs the stream marked public.
- Icecast: the server needs a directory block with the directory's address (the documentation's example is the Xiph directory) and must be built with directory support. The encoder sends a public flag on connect, and the mount can override it.
- SHOUTcast: the DNAS registers with the SHOUTcast Directory using an authhash, a key that keeps your listing tied to the same station even if the server address changes. According to the vendor, a server older than 2.5 loses its listing.
- Confirm it worked: with the encoder connected and the public flag on, search the directory for your station name. If it is missing, check the flag before anything else.
Whatever the plan, Free included, your station also has its own public page, an entry in our radio guide and help with directory submissions.
Settings to copy into your encoder
BUTT, Mixxx, SAM Broadcaster, RadioBOSS and OBS in audio mode all connect to a hosted station. BUTT and Mixxx, for example, offer both server types, so you change the server type and a few fields, not the software. Take every value from your control panel, never from an old screenshot.
| Field | On Icecast | On SHOUTcast |
|---|---|---|
| Server type | Icecast | SHOUTcast |
| Address and port | As shown in the control panel | As shown in the control panel |
| Where the stream goes | Mountpoint name | Stream ID number |
| Login | Source password | Stream password |
| Public listing | On if you want a directory listing | On if you want the SHOUTcast Directory |
Your control panel lists every one of these values for your station. Confirm it worked: the encoder reports connected, and the HTTPS listen link plays your audio with the current title.
Switching engines on a hosted station
On our HTTPS radio streaming service a new station begins on Icecast. A single toggle in the control panel changes it to SHOUTcast DNAS 2.6, and that move also lists it in the SHOUTcast Directory. Listen links are HTTPS on all plans, and a non-encrypted http address remains for legacy players.
- Pick a quiet hour and tell your DJs, so nobody is mid-show if the source drops.
- Flip the engine switch in the control panel.
- Open the encoder settings the control panel now shows and compare them field by field with each DJ's encoder: server type, port, mount or stream ID, password.
- Reconnect one encoder and listen through the public listen link, not through the encoder's own monitor.
- Check that the now-playing title changes on the next track, then let the other DJs reconnect.
Stuck on a field at an odd hour? Open a ticket or a chat and quote the server type your encoder shows.
When it goes wrong
- Encoder refuses the login after a switch: the server type is still set to the old engine. Icecast wants a mount and source password; SHOUTcast wants a stream ID and its password.
- Old encoder connects to the wrong stream: a 1.x source lands on stream 1 unless the password carries the stream number.
- Garbled accented titles on Icecast MP3: the title is arriving in a different character set from the one the mount expects. Make the encoder and the mount agree on one character set; support can tell you which one the mount expects.
- Stream plays on your laptop but not on your website: the page is HTTPS and the player points at a plain-http address. Use the HTTPS listen link.
- Station missing from the SHOUTcast Directory: the station is still on Icecast, or no source is connected, or the listing flag is off in the encoder.
If you need to edit the server configuration yourself, such as custom mounts, relays or a character set per mount, a hosted station is the wrong fit. A cloud server with root access lets you run either engine and own its configuration.