AirWaves  /  Music Scheduling Software
Music Scheduling

Music Scheduling Software

AirWaves is music scheduling software with everything a serious scheduler needs — format clocks, category rotations, a full rule tree, multi-pass optimisation and turnover analysis — plus one thing no other scheduler has: an energy arc that lets you program the feel of the day, not just the order of the songs.

It is built into the same platform as the automation, so there is no exporting and importing logs. And if you would rather keep the automation you already run, the scheduler works standalone and exports logs straight into it.

What music scheduling software actually decides

Music scheduling software determines what plays in every position of every hour. It holds your library split into categories, applies format clocks that define the shape of each hour, and enforces the rules that keep a station sounding balanced — artist and title separation, tempo and mood flow, dayparting, sound codes, era balance. What comes out is a music log your automation plays.

Every scheduler on the market does that. The difference between them is what happens at the edges: what the engine does when a category runs dry at 3 p.m. on a Thursday, whether you can see a category burning before the ratings tell you, whether a request can air without sounding like an interruption, and whether the whole thing lives behind an export step that quietly desynchronises from your library.

Shape of the Day — schedule the energy, not just the songs

This is the part no other music scheduler has. Instead of only defining which categories land in which positions, you draw a 24-hour energy arc — a draggable curve describing how the station should feel across the day. Flow Sequencing then builds each hour toward the energy you set.

Mellow overnights that lift into morning drive. A midday plateau. An afternoon build that peaks at five and comes back down through evenings. You draw the shape; the scheduler picks songs that get there while every one of your existing rules still holds.

  • Exclusive Flow Control — ride the natural ebbs and swells of a broadcast day instead of fighting them with brute-force clock edits.
  • Per-day or weekday/weekend curves — a Saturday does not have to feel like a Tuesday.
  • Quick-shape presets for common format arcs, then drag from there.
  • Absolute control — nothing airs in a shape you did not draw.

Programmers describe it as the first time the tool matched how they actually think about a radio station. You have always programmed the feel of the day in your head; this is the first scheduler that lets you say it out loud.

Clocks, music scheduling categories and rotations

Underneath the energy layer is a complete, conventional, extremely capable scheduler — the one you already know how to drive.

Format clocks

Full clock construction with quick-shape presets, per-day and weekday/weekend variants, and inheritance so a format change does not mean rebuilding 168 hours by hand.

Category rotations

Power, Current split A/B/C, Recurrent and Gold, each with independent rotation behaviour, rest requirements and daypart availability.

The rule tree

Artist and title separation, dayparting, sound codes, tempo and mood, era balance — each rule marked breakable or unbreakable.

Multi-pass engine

Custom algorithms weigh every rule, rest and rotation on every single pick, then re-pass to resolve conflicts rather than accepting the first legal answer.

Optimum goals & fallback

When a category runs dry the scheduler steps down gracefully to the next best option instead of failing the slot and leaving a hole.

Multi-day auto-build

Build a week at a time, straight into the automation engine — or straight out to a third-party automation as an exported log.

What a music scheduling category actually holds

A category is the unit a music scheduler thinks in. Everything else — the clock, the rule tree, the rotation report — is downstream of how well the categories were drawn. In AirWaves a category is not just a bucket with a name on it; each one carries its own behaviour, and that is what stops a format needing forty categories to express six ideas.

  • Its own rotation mode. Normal rotation for music, or sequential-daily for the categories that should walk in order — playing in cart-code order from a chosen starting point each day and resetting the next, which is how liner and legal-ID sets are supposed to behave and almost never do.
  • Its own search depth. How far down the category the scheduler may reach before it gives up on a slot. Shallow keeps the power tight; deep keeps a thin gold category from failing.
  • Its own fallback. Name the categories to step to when this one is dry, and a slot degrades to the next best song instead of leaving a hole for somebody to notice at 3 a.m.
  • Rejoin protection. Mark the categories that must not be cut into by a network rejoin, and the scheduler and the automation both respect it.
  • Tempo matching and daypart availability, so a category can be right for mid-mornings and wrong for drive without being split into two.
  • A fixed on-air identity, optionally. Every cart in a category can report one artist and title on air — so commercials and jingles show the station, not an internal cart name, without editing a single file.
  • Its own row colours. A background and a font colour that follow that category everywhere it appears — the log, the playlist, the clock editor — so an operator reads the hour by shape before they read a word of it.

Categories are also the seam where most migrations go wrong. A library imported from another system arrives with somebody else’s category structure baked into the cart numbering, and the honest answer is that you will redraw some of it. AirWaves lets a category be edited, renamed, reordered or deleted with its carts reassigned in one action, rather than making the first week’s decisions permanent.

No rotation clunk, no pile-ups — and the numbers to prove it

Every programmer knows the failure modes: the same artist three times in ninety minutes, a gold category that has quietly turned into eleven songs on repeat, a rotation that clunks every time it wraps. These are not exotic problems; they are what happens when a scheduling engine takes the first legal pick instead of the best one.

AirWaves resolves separation across a multi-pass engine, so artist and title separation hold even under pressure — when the library is thin, when a daypart is tight, when three rules collide on the same slot. And the diagnostics are built in rather than bolted on:

  • Turnover analysis — how long a category takes to cycle, and whether that matches what you intended.
  • Spins and search depth — how hard the engine had to work to fill each position, which is the earliest warning that a category is too thin.
  • Category health at a glance — see a category burning or going stale before it costs you listeners.

You find out a category is thin while you can still fix it, not when the book comes out.

Requests and tune-out feed the scheduler

Most stations treat requests as a separate toy: a web form, a spreadsheet, and a jock who plays something off-format at 7 p.m. AirWaves wires them into scheduling as data.

Every request is a vote and every tune-out is a signal, and both flow back into rotation so your clocks reflect what is actually working with your audience. Requests respect your format — listener picks only flow into the clock positions you open, through a managed queue with cooldowns, duplicate protection, recently-played protection and a hard-filtered public library. On air a request sounds exactly like a scheduled spin, because it is one. Audience Insights ranks the hottest tracks by day, week and month and surfaces request momentum, so you can see a song breaking before the trades tell you.

One library, one seat, every station

Scheduling for a group usually means one scheduling machine, one licence dongle, one person who knows where everything is, and a lot of copying files around. AirWaves runs on a centralised library with centralised control: every station and studio schedules from one seat and one set of carts, in a browser, from anywhere.

Because the scheduler shares the platform’s library, the markers, metadata and loudness measurements the engine wrote on import are the same ones the scheduler reasons about. There is no second copy of the truth to drift, and no import step to go stale. Traffic placement and reconciliation happen in the same pass, so programming, automation and air are one continuous system.

What to look for in music scheduling software

  • Can it schedule how the station feels, or only what it plays? Category logic alone cannot express an energy arc across a day.
  • Does separation hold when the library is thin? Single-pass engines take the first legal pick. Ask what happens at 3 a.m. on a small gold category.
  • What does it do when a category runs dry? Failing the slot and leaving a hole for a human is a design choice, not a law of nature.
  • Is turnover analysis built in? If you have to export to a spreadsheet to see search depth, you will not look often enough.
  • Is there an import step between the scheduler and the automation? Every export/import boundary is a place for two versions of your library to drift apart.
  • Can you schedule from anywhere? A scheduler tied to one machine ties your programmer to one chair.
  • Will it work with the automation you have now? If a scheduler cannot export to your playout, you are buying two decisions at once.

AirWaves was designed against exactly this list — and it is worth saying plainly that you can adopt it as a scheduler alone, keep the automation you already run, and judge it on the only thing that matters: whether your station sounds better.

No rip-and-replace

Music scheduling software that runs on your existing automation

You do not have to change your air chain to change your scheduler. AirWaves music scheduling runs standalone and exports logs your current automation reads — so you can put the Shape of the Day energy arc, the rule tree and the turnover analysis to work over RCS, WideOrbit, Zetta, Simian, ENCO, Rivendell, StationPlaylist or NexGen without touching a single studio machine. If you later move the automation across too, the scheduler stops exporting and starts feeding the engine directly, and nothing about your clocks or rules changes.

Your existing automation ←→ AirWaves Music Scheduling On air, unchanged

Music scheduling software and categories, answered

Music scheduling categories are the groups a station’s library is divided into so a clock can ask for a KIND of song rather than a specific one — power currents, secondary currents, recurrents, gold by era, plus the non-music categories for imaging, jingles and commercials. A clock position says “play a power current here”, and the scheduler picks the best legal song from that category. In AirWaves each category also carries its own rotation mode, search depth, fallback categories, rejoin protection, tempo matching and daypart availability, so behaviour lives on the category rather than being re-expressed in every clock that uses it.

Fewer than most stations end up with. The common failure is creating a category to express a rule — a separate bucket for “gold that only plays at weekends” — when the rule belongs on the rule tree or on the category’s own daypart availability. A mainstream music format is usually well served by six to twelve music categories plus its imaging and spot categories. If a category has fewer songs than its rotation needs, it will either repeat audibly or fall through to fallback; if two categories always schedule identically, they are one category with a rule attached.

Yes. A category can be set to sequential-daily rotation, which plays its carts in cart-code order from a chosen start point, walks up through the day and resets the next — with an option to ignore leading characters in the numbering. It is the right behaviour for liner sets, legal IDs, serialised features and anything else where “next one” means next, not random.

Music scheduling software decides which song plays in which position in every hour of the broadcast day. It holds your library split into categories, applies format clocks that define the shape of each hour, and enforces rules — artist separation, title separation, tempo and mood flow, dayparting, sound codes — so the station sounds balanced and nothing repeats badly. The output is a music log the automation system plays. Good scheduling is the difference between a station that sounds programmed and one that sounds like a shuffled playlist.

Two things. First, Shape of the Day: you draw a 24-hour energy arc and Flow Sequencing builds each hour toward the energy you set, so you are programming how the station feels through the day rather than only which categories land where. No other music scheduler does this. Second, it is not a separate product bolted to automation with an import step — it feeds the playout engine directly, using the same library, the same carts and the same markers, so there is no exporting, importing, or reconciling two versions of the truth.

Yes. The scheduler runs standalone and exports logs in formats third-party automation systems read, so you can schedule in AirWaves and play out on RCS, WideOrbit, Zetta, Simian, ENCO, Rivendell, StationPlaylist, NexGen or anything else that imports a music log. Nothing in your studio has to change. This is the usual first step for stations that want better scheduling now and a platform decision later.

A full rule tree: artist separation, title separation, dayparting, sound codes, tempo and mood flow, era and category balance, and per-day or weekday/weekend curves. Rules are marked breakable or unbreakable and resolved across a multi-pass engine, so soft preferences bend under pressure while hard rules hold. When a category runs dry, optimum goals with category fallback let the scheduler step down gracefully instead of failing the slot and leaving a hole for someone to fix by hand.

Categories run as Power, Current (A/B/C), Recurrent and Gold with quick-shape presets, and a custom mathematical engine weighs every rule, rest and rotation on every single pick. Turnover analysis is built in, showing spins, search depth and category health at a glance, so you can see a category burning or going thin before your audience does — not three books later.

They can, on your terms. Requests and tune-out tracking feed directly back into the scheduler: every request is a vote and every tune-out is a signal, and both inform rotation. Requests respect your format — listener picks only flow into the clock positions you open, through a managed queue with cooldowns and recently-played protection — so on air a request sounds exactly like a scheduled spin, because it is one.

Music people are building good-sounding days in an afternoon rather than a training week. The concepts are the ones you already know — clocks, categories, rules, rotations — and the interface is browser-based, so you can schedule from anywhere instead of being chained to one desk with a dongle in it.

See AirWaves Music Scheduling running your station

Book a walkthrough with an engineer who has actually run a radio station, or call 1-877-224-1656. No bots, no phone tree.