What is radio automation? What happens when the live show ends?
An evening presenter says goodbye. A jingle follows, then a previously selected music programme begins. Someone in the studio may not need to start every file manually: some of those transitions can be planned using radio automation.
Radio automation uses software and workflows to play prepared material in a sequence or schedule. It can execute a plan, while the team remains responsible for content selection, rights and what happens when something fails.
How is a broadcast day prepared?
Depending on the system, music, jingles and recorded shows can be stored in a library and placed on a schedule or playlist. LibreTime, for example, describes itself as a radio broadcast and automation platform. Other products have different features and setups.
Imagine a station scheduling a recorded announcement, a live conversation and an approved music selection afterwards. The team checks the correct file, programme time and music permissions.
Is automation the same as a streaming server?
Automation may manage what plays and when. A streaming server distributes the incoming audio to listeners. A product can combine these functions, but the distinction helps when investigating a fault: seeing the correct file on a schedule does not by itself prove that the audience hears it.
RadioTEDU describes a similar division on its technology page: OnAir shapes the programme, while RTSAS delivers the stream to listeners. The project description makes the two jobs tangible, but it does not establish how a particular transition is configured or prove that a listener is receiving it successfully.
Similarly, a live source marked “connected” may not be sending the intended sound. Listening to an authorised test stream on a separate device reveals what the transition sounds like at the listener end. Buffering can make it arrive at different times on different devices.
Listen while exploring this story
Tune into campus radio with non-stop independent music and culture.
What plays when the presenter finishes?
Live-source priority and the return to scheduled material depend on the system and settings. The LibreTime 3.x documentation describes source types and settings in that product; another version or service should not be assumed to behave identically.
In the example described by LibreTime, a show source can be overridden by a master source. The documentation describes separate options for switching when a live input connects and when it disconnects. If the first is enabled but the second is not, a station may enter the live segment automatically yet still need an operator to switch away afterwards. Confirm the priority and return behaviour in the version and configuration you actually use.
A disconnected source and a connected source sending silence are different situations. If the connection remains open, check how your own setup handles silence; the disconnect setting alone does not establish what will happen.
A team can rehearse the connection and return to automation in an authorised test environment. Agreeing on a reviewed recording or another fallback if the presenter cannot connect also makes a live decision easier.
A schedule does not make an editorial decision
An announcement with the wrong date can play at the right time. Checking file content, time zone and usage rights still matters. Clear responsibility for administrative access and changes helps a team understand what happened.
Automation can support a station's flow between live and recorded material while leaving people in control of what the audience hears and why.
