What a rota has to decide
A rota with several presenters settles five things before anybody goes on air. Write the answers down once and every later problem gets shorter.
| Decision | What to settle | Why it matters |
|---|---|---|
| Who connects | One named login per presenter | You can see who is live and remove one person without touching the others |
| When | Start and end of each slot, day by day | A login limited to its slot cannot cut into the next show |
| Which clock | One station time zone for every entry | Presenters in other countries convert once, from one reference |
| What fills gaps | AutoDJ, a fallback playlist or a rerun | Silence between shows sends listeners away |
| What listeners see | A weekly line-up, now and next | People return for a show they can find |
Logins: one per presenter
Each DJ should connect with credentials that belong to them alone. Icecast itself is built around this idea: its configuration reference lets every mount point carry its own source username and password, and a source that cannot present them is refused. A single shared password works on day one and fails the day a presenter leaves, because the only way to lock them out is to change it for everybody.
On our SSL radio streaming plans the paid tiers handle this for you. Premium gives you up to 5 DJ accounts, while Platinum gives you 20, and each account is limited to its own hours, so a presenter who opens the encoder early or forgets to close it cannot take over someone else's slot. On the free plan you get a single live stream, fed by any encoder that speaks Icecast or SHOUTcast, which suits a single presenter rather than a rota.
Treat a DJ password like a door key. Send it privately, never in a group chat, and change or remove the account the week a presenter stops.
Building the week: slots, gaps and time zones
Pick one time zone for the station and enter every slot in it. Presenters abroad convert from that single reference; you never keep two versions of the grid. Governments change offsets and daylight saving rules from time to time, and the IANA time zone database is updated periodically to follow them, so check the grid against each presenter's local clock in the weeks around a daylight saving change on either side.
- Block out fixed shows first: the ones with a regular audience or a sponsor.
- Leave a few minutes between back-to-back shows for the hand-over. A slot that ends on the hour and another that starts on the same minute is where dead air comes from.
- Mark every empty hour with what plays instead: AutoDJ music, a recorded show, a rerun.
- Send each presenter their own slots, written in station time with their local time beside it.
- Review the grid monthly and remove slots nobody has used.
On Premium and Platinum, AutoDJ runs your uploaded tracks whenever nobody is live, and hour clocks let the automated hours change by daypart, weekday and season. Recorded and syndicated shows and reruns can sit in the grid as well, so a presenter on holiday can still be on air.
Hand-overs without dead air
A clean hand-over means listeners never hear the gap between one source leaving and the next one arriving. In plain Icecast this is done with a fallback: the configuration reference describes a fallback mount that listeners are moved to when the live source drops, and a fallback override setting that brings them back when a source connects again. It also notes that a source sending no data for the source timeout is removed from the server.
Our radio service does this switching for you on the paid plans. AutoDJ steps aside the moment a live DJ connects and takes the air back when they leave, with an emergency cut and dead-air alerts. Platinum adds a backup source, gapless DJ handoff and a standby slot. On Premium and Platinum a recording of each live show is saved to the library, ready to rerun.
- Outgoing DJ: back-announce the next show and let the last track run.
- Outgoing DJ: press Stop in the encoder at the end of the slot. BUTT, for example, retries a lost connection until somebody presses Stop.
- Incoming DJ: start the encoder only once the slot has begun.
- Both: confirm the change on the public player, not in your own headphones.
Encoder settings every DJ copies
Every presenter fills in the same fields; only the login changes. Take the server, port and mount from the control panel, never from an old message. On Platinum, the nearest-server encoder settings are in the control panel's Radio section.
| Field | BUTT | Mixxx | Notes |
|---|---|---|---|
| Server type | Icecast or SHOUTcast when adding a server | Type | Match the engine your station runs |
| Address | Server address | Host | Mixxx asks for a host name or IP, not a URL |
| Mount | Icecast mount point | Mount, starting with a slash | Icecast only |
| Login | Icecast user | Login | The presenter's own account |
| Password | Password | Password | Typed into the encoder, never shared |
| Show name | Song Name field | Custom metadata | Put the show and DJ name here |
Two BUTT options deserve a decision. Start streaming after launch connects as soon as the program opens, which surprises a presenter who opens it early to test levels. Stop if signal is absent for [...] seconds disconnects after silence, which helps when a DJ walks away without pressing Stop. Mixxx starts broadcasting from Options, then Enable Live Broadcasting, once the preferences are saved. Broadcasting straight from a browser tab is also possible on Premium and Platinum, which spares a guest the install.
A line-up listeners can follow
Publish the schedule where listeners already are. Every plan includes a weekly show line-up with on now and next, a public page for the station, and show reminders in the player. Keep show names identical in the grid, in the encoder title field and in your posts, so a listener searching for a show finds the same name everywhere.
- Write times in station time and name the zone beside them.
- Give each show one name and one presenter line, kept the same each week.
- Mark cancelled shows and what plays instead, so the line-up does not lie.
- Put the HTTPS listen link into a player on your website; if you need a site, our web hosting can carry it.
- On Premium and Platinum the station gets its own app; the app publishing guides walk through submitting it from your own store accounts.
On Premium, show-by-show audience figures are kept for 30 days, and Platinum keeps audience reports for 90 days. Use them to move a weak slot, not to rank presenters in public.
Checks before the first week goes out
- Each DJ connects once inside their own slot. Expect the live show on the public player once the encoder shows connected.
- Each DJ tries once outside their slot. Expect automation to stay on air.
- Run one deliberate hand-over. Expect no silence on the player between the two shows.
- Read the line-up page at the time of a show. Expect the right show under on now.
- On Premium and Platinum, check the audience figures after the first live show. Expect it listed as its own show.
When a show does not reach the air
- Show not on air when the slot starts: check that the presenter used their own login and that the slot has started in station time, not local time.
- Login refused: check the mount and username for typing errors, then the slot; each account is limited to its own hours.
- Previous presenter's encoder keeps reconnecting: ask them to press Stop; BUTT, for example, keeps retrying a lost connection until Stop is pressed.
- Silence after a DJ leaves: confirm automation is on and the fallback playlist has music in it.
- Wrong show name on the player: the encoder title field still carries the last presenter's text.
Support runs 24/7 by live chat, where an assistant can look at your account and hands you to a person on request, and by ticket.