Radio Automation Software

What radio automation software has to do

Radio automation software is the system that keeps a station on the air. At minimum it has to hold the log, play the right audio at the right time, fire imaging and events, handle breaks, join and leave network programming, and do all of it unattended overnight, at weekends, and through a holiday when nobody is in the building.

That baseline has been solved for twenty years. What separates automation platforms now is everything around the log: whether the stream is a first-class output or an afterthought, whether the library tags itself or eats a month of somebody’s life, whether a jock can voice track a shift from a hotel room, whether the system tells you it is about to break, and whether adding a station means another server, another license and another training week.

AirWaves was built from the audio engine up to answer those questions differently. The playout core is a proprietary real-time C++ engine — not a wrapper around someone else’s player and not assembled from public libraries — which is precisely why it can do things the rest of the category cannot.

Dual dynamic sequencers — air and stream, automated separately

Almost every automation system treats the stream as a copy of the air signal with a different encoder on the end. AirWaves runs two independent dynamic sequencers at the same time, so your broadcast and your stream are two separately automated chains with their own logs, their own ads and their own event triggers.

• Blackouts stop being a project. Schedule the game on air, tell the stream to run the regular log, and you are done — no second system, no operator babysitting a switch.
• Sell the stream separately. Different advertisers, different inventory, different rates on the web listen, tracked and billed through the same traffic system as the on-air spot.
• An exclusive event scheduler that does not care how long an event runs. Sports, remotes, specials and network windows air as intended instead of being force-fitted to a clock.
• One-step game-log send, plus built-in rain-delay and cancellation signalling — not the multi-step process the rest of the industry makes it.
• “Magic” smart events — rules like never letting two pieces of imaging air back to back, dynamic oversweeping, and automatic tagging of events and songs.

This is the capability broadcasters most often tell us they assumed was impossible, and it is available on day one.

Content intelligence — the library tags and cues itself

The unglamorous truth about automation is that most of the pain is in the library, not the log. AirWaves attacks that directly: as audio arrives, the engine analyses it and writes what it finds into the file.

Automation that warns you before it fails

Every broadcast engineer has the same story: a machine that died at three in the morning with nobody watching. Conventional automation is reactive — something breaks, an alarm fires, a phone rings, and by then you have already had dead air.

The AirWaves engine constantly self-monitors and runs forward-looking health checks. Instead of failing live, it can tell you that it is showing early signs of trouble and may fault later in the week, and recommend switching to auxiliary and rebooting the main now. AirMonitor watches the actual audio leaving the building for silence, low level and stuck audio; AirWatcher watches services, disk, database, engine health and network links underneath it. Alerts route by station, by role and by time of day, so an overnight problem reaches whoever is genuinely on call.

Behind all of it, AirVault keeps a protected off-machine copy of your content, and because AirWaves is engine-first you can place a second engine at the transmitter as a live hot backup — if the studio link drops, the transmitter-side engine keeps the station on air without skipping a beat.

Programming, sales and remote — built into the automation

• Custom UI per user. Operators, PDs, traffic and sales each build their own drag-and-drop control surface. PD lockdown protects critical functions, and every function is individually configurable per user and role.
• Remote voice tracking and production in the browser, with markers already set by the engine, per-user daypart restriction so talent can only track their own hours, fill attribution recording who did what, and a station coverage view showing every unfilled break.
• A world-class auto-scheduler fed by listener requests and tune-out tracking, generating balanced logs in-house with no third-party scheduler and no exporting and importing.
• Multiple traffic types with automatic network barter merge, and sales-to-air in minutes via dynamic ad insertion.
• AirLink multiparty live audio with automatic mix-minus, bringing remotes, guests, satellite studios and field reporters on air without a board op.
• Full live control from a tablet or phone — hear the live studio and go live yourself, not just watch a status screen.

Hybrid cloud radio automation: local speed, cloud scale

The industry has spent a decade arguing about on-premise versus cloud automation, and both camps are right about the other one’s weakness. Cloud automation is easy to manage and terrible when the internet hiccups. On-premise automation is fast and reliable and a nightmare to run across twelve markets.

AirWaves is deliberately both. The engine runs locally on one server per site — on-air response is pure local with no round trip between a fader move and the audio, and the site keeps running even if the network link goes down. The control plane is distributed — every site connects into one platform you operate from anywhere, giving a single pane of glass across a national network or a single station. You own the hardware and the data; you get cloud-style management without cloud-style latency.

What to look for in radio automation software

If you are comparing platforms, these are the questions that actually separate them — not the feature-list bingo everyone passes.

• Can it automate air and stream independently, at the same time? Most cannot. If the stream is just a mirror of the air signal, you cannot sell it separately or blackout cleanly.
• Does it write markers and metadata into your files automatically? If not, budget real staff time for library prep, forever.
• Does it need software installed on every studio machine? Per-seat clients mean per-seat updates, per-seat failures and per-seat licence costs.
• Whose audio engine is it? A vendor that licenses someone else’s playout core cannot fix what you find at the bottom of it.
• Does it warn you before it fails, or after? Reactive alarms are table stakes. Predictive health checks are not.
• Can one person run it from a phone? The test is whether you can go live from it, not whether you can look at it.
• What happens when you add a second station? If the answer involves a new licence negotiation and another training week, the architecture is wrong.
• Will its parts work with what you already own? A platform confident in its modules will let you buy one.

AirWaves answers yes to every one of these. That is not an accident of features; it follows from having built the engine, the DSP and the scheduling algorithms in-house rather than assembling a platform out of other people’s parts.

Radio automation software, answered

Explore the rest of the platform

Every AirWaves module shares one engine, one database and one login — and every one of them also runs standalone against the automation system you already own.