Broadcast to RadioHost Studio with RadioBOSS

RadioBOSS is Windows radio automation with its own scheduler, playlist rotation and encoder. If you already run it, the question is not really "how do I connect it" — it is which of the two systems owns the schedule.

Both answers are legitimate, and the setup is the same either way.

Two ways to use it

As a live source. Studio owns the schedule and the unattended hours. RadioBOSS is what a presenter opens for their show, connects, presents, and disconnects. This is the arrangement most stations want, because it means nothing has to stay running on a Windows machine overnight for the station to stay on air.

As the whole station. RadioBOSS runs continuously on a machine you keep awake, and Studio is the delivery layer. This works, and people do it, but you are then maintaining a PC that must never sleep, never update at the wrong moment and never lose its internet connection — and Studio's own automation, clocks and back-timing sit idle while you do.

The rest of this page assumes the first arrangement.

What you need first

An External DJ credential from Live → External DJs in Studio, plus the server, port and mount shown on that page.

Encoder settings

In RadioBOSS, open Settings → Broadcasting and add an encoder.

RadioBOSS pre-fills the username as source. Replace it with your DJ username — a correct password against source still fails.

Metadata

Leave send metadata enabled. RadioBOSS knows what it is playing and passes artist and title up with the stream, which is what keeps now-playing displays honest during a live show instead of showing whatever automation last played.

Going live

Connect the encoder from the broadcasting panel. Studio detects the source, ducks automation and shows the live banner with the DJ name attached to the credential.

Disconnect at the end of the show and automation resumes from the current schedule position — the show that should be on air at that minute, not the one that was interrupted.

Do not levelling twice

RadioBOSS has its own normalisation and processing, and so does Studio: every file uploaded to Studio is measured on import and played back at a consistent loudness.

Running both is not twice as good. The audio arriving from RadioBOSS is a live source and is treated as one — Studio does not re-measure a stream in flight, so RadioBOSS's own levelling is what listeners hear during your show. Set it so the live output sits at roughly the same loudness as the station's automated hours, then leave it alone. A live source that is visibly louder than the rest of the schedule is the most common complaint on stations that run both systems.

Frequently asked questions

Can RadioBOSS and Studio both hold the schedule?

They can, and you will regret it. Two schedulers means two sources of truth about what should be on air at 14:00, and the one that wins is whichever happens to be connected. Pick one to own the schedule.

Does RadioBOSS reconnect automatically if the internet drops?

Yes, its encoder retries. What matters more is what listeners hear during the gap, and that is Studio's answer rather than RadioBOSS's: the moment the source disconnects, automation takes over from the current schedule position, so the station keeps playing while RadioBOSS is reconnecting.

Can I use RadioBOSS Cloud instead?

RadioBOSS Cloud is a hosted product with its own streaming, so it is an alternative to Studio rather than a source for it. The desktop application is what connects as a live source.

Which bitrate should the encoder use?

Match your plan cap — 128 kbps on a trial, up to 192 on a station subscription. Connecting above the cap is refused rather than downgraded.