AutoDJ vs automation vs live: what actually runs a radio station

Three terms get used as if they were the same product, and the confusion costs money — people buy an AutoDJ expecting automation, or run automation on a laptop expecting it to behave like hosting.

They are different layers. Most stations need all three.

AutoDJ

An AutoDJ plays files from a list when nothing else is connected. That is the whole feature.

It came out of shared streaming hosting, where the server needed *something* to send when the DJ was offline. Upload files, they play in order or shuffled, and when a live source connects the AutoDJ steps aside.

What it does not have: dayparts, rotation rules, artist separation, jingles placed structurally, news on the hour, presenter links, back-timing, or any concept of a show. It is a music player with an internet connection.

That is enough for a genuine set of cases — a genre stream with no presentation, background music for a venue, a holding stream for a station that is mostly live — and for those it is the right amount of complexity. It is not enough to sound like a radio station, and no amount of shuffling makes it so.

Radio automation

Automation is what makes unattended hours sound produced.

It holds the structure of an hour as a clockwheel — music, sweeper, two songs, talk break, news at the top — and fills it from the library according to rules: least recently played first, never the same track within a couple of hours, never the same artist within the hour. It places jingles because the structure calls for a jingle, not because one happened to be next in a list.

It also understands the calendar. A show occupies a slot in a schedule; it has a clock, a presenter, a set of playlists it draws from, and it can carry pre-recorded presenter links that are placed at the right moments. It knows that news is at :00 and can choose short enough songs beforehand to arrive there cleanly.

And it knows what to do when things go wrong: an unreachable feed is stepped over, a hole in the schedule falls through to a fallback rotation, a live source that disconnects hands back to whatever should be on air *now*.

The difference between AutoDJ and automation is the difference between a playlist and a station. A listener cannot name it, and can hear it immediately.

Live broadcasting

Live is a person, in real time. A presenter connects a source — an encoder on a laptop, a browser-based studio, a DJ application — and takes over the station.

The mechanics are the same everywhere: the source authenticates, the platform sees it, automation ducks out, and the presenter is on air. When they disconnect, automation returns.

What varies, and what matters:

Where automation resumes. From the current schedule position, not from where it was interrupted. A station that resumes at the interruption point spends the rest of the day playing the wrong daypart.

Whether the handover is clean. A live source appearing mid-song should not chop it in half.

What happens if the presenter vanishes. A crashed application can leave a connection open that is delivering nothing. Someone needs to be able to end that session without waiting for a timeout.

Who is allowed to do it. Each presenter with their own credential, so live sessions are attributable, and one revocation does not lock out the whole station.

Which does a station actually need?

A music stream with no presentation: AutoDJ is sufficient.

A station: automation for the structure, live for the hours where being present is the point, and voice tracking to make the rest sound hosted without anyone being awake.

Where it should run

One more distinction, and it is the expensive one.

Desktop automation — the traditional Windows applications — runs on a machine you own. That machine must stay awake, stay connected, not install updates at 3am, not run out of disk, and survive its own power supply. It works, and thousands of stations do it, and every one of them has a story about the day it did not.

Hosted automation runs on infrastructure that is somebody's job. The trade is control: you configure rather than install, and you work within the platform's model instead of building your own.

For a station where being off air matters more than being infinitely configurable, hosted is the easier argument. For a station with an engineer, a rack and specific requirements, desktop still wins.

Frequently asked questions

Is AutoDJ the same as radio automation?

No. AutoDJ plays a file list when no live source is connected. Automation schedules shows, enforces rotation and separation rules, structures hours with clockwheels, places jingles and presenter links, and handles failure. AutoDJ is one small part of what automation does.

Can I run a radio station with just an AutoDJ?

You can run a music stream. Whether it sounds like a radio station depends on whether anyone expects structure — a station identity, news, presenters, dayparts. If nobody does, an AutoDJ is genuinely enough.

Does automation replace presenters?

It replaces the requirement for a presenter to be physically present at the time of broadcast. Voice tracking means the same presenters make the same editorial choices, recorded earlier — which is what lets a small station sound hosted around the clock.

What happens to automation when a live show starts?

Automation ducks out when the live source connects and resumes when it disconnects — from the current schedule position, so the station returns to whatever should be on air at that moment rather than to the show that was interrupted.

Do I need automation if all my shows are live?

Yes, for everything that is not a show. Unless presenters cover all 168 hours in a week, something has to run the rest — and that something is also your safety net when a live source drops.