Prepping Tracks for an Automated Station: A Practical Checklist

Most of the work that decides whether a track survives an automated station happens before anyone touches a limiter. I ran a station for years, and the failures that actually dented the listening experience were never about plugin choice. They were about files: mismatched levels, missing metadata, tag fields that garble on the player, sudden 6 dB jumps between hour one and hour three. The chain does not fix any of that. Prep does.

Here is the checklist I’d hand someone building a playlist for an unattended stream, in the order it saves you time.

First, decide what the station actually needs to deliver

An automated station is a sequencing job with a delivery spec bolted on. Before touching audio, name the target. If it’s streaming, −14 LUFS integrated with a −1 dBTP true-peak ceiling is a fair working default, and hitting that is arithmetic: a machine does arithmetic perfectly, every time, at three in the morning, as the engineers at Major Mixing put it. If it’s a broadcast feed, the ceiling and the loudness window are different and you should ask the transmission side directly rather than guess.

The point: set the target once, write it down, apply it to everything. A station’s biggest enemy is variance, not absolute loudness.

Sort your files before you process a single one

This is the boring part that pays. Mastering, properly understood, includes assembly and sequencing, the specifying of gaps between tracks, level adjustment and fading, all handled before the material is rendered as a finished master. For a playlist that runs unattended, those same operations matter at the directory level, not just the track level.

• One folder, one pile. Move every source file into a working directory. No streaming services, no random desktop copies, no “final_final” versions.
• Number the filenames. Zero-padded prefix (001_, 002_) so the player and your own eyes both see the intended order.
• Kill the duplicates. You will have three copies of one track. Find which is the cleanest source and delete the rest. This sounds trivial. It is the reason half of automated station bugs exist.
• Confirm the length. A 7-minute track that is actually a 7-minute spoken intro skip will eat your programming block. Check durations against what you expect.

Set levels relative to the room, not to each other

Every track should arrive at the station already at its delivery-level target. Do not rely on the player to normalise. Level-matching a dozen tracks so no song jumps out is mechanical, tedious work, and automation is genuinely better at it than a tired human, which is exactly why you should do it at prep time with a tool you trust and then lock it down.

If you’re using an automated mastering tool for the level pass, use it for what it does well: hitting loudness and true-peak targets, broad tonal matching against a reference, and consistency across a whole set. That is a legitimate use of the tool. What it cannot do is decide that one track feels brighter than another for a reason, and that the reason matters.

Once it’s set, do not re-adjust per show. If a single track needs a gentle nudge later, that’s an editorial call, not a level pass.

Use gentle compression, then leave it alone

I’ve argued this case at length before, so here’s the short version. The point of compression at prep time is to keep quiet intros and loud choruses in the same neighbourhood without squashing the dynamics that make a set breathe. Pushing a limiter too hard kills dynamics and makes tracks fatiguing over a long mix; a few decibels of gain reduction with true-peak limiting is usually enough. A clean 3-4 dB of reduction on the limiter, with true-peak limiting on, keeps inter-sample peaks from clipping on playback systems without turning everything into paste.

Then stop. The temptation to chase the loudest version of each track is how you end up with a station that sounds like a playlist assembled from three different decades of loudness war casualties.

Trim and fade, every time

Silence at the head and tail of a file is the single most common cause of dead air on an automated station. A player announcing the next track while three seconds of room noise plays underneath is the fast route to sounding amateur.

Trim head silence to a short uniform value (half a second is plenty for most material). Apply a fade-out of a few seconds at the tail so the track ends, rather than simply stopping. This is the unglamorous version of the fading and gap-specifying that mastering properly does, and it’s the step most people skip.

Fix metadata before it becomes the player’s problem

Every file needs correct embedded tags: artist, title, album, year, and (if the station surfaces them) genre and ISRC. The player will read these verbatim. It will not guess. The wrong tag on a track means the wrong artist name flashes across the listen page, and no one notices until a listener complains.

If your station surfaces genre or mood for filtering or recommendations, be consistent about the vocabulary. Pick one spelling of “Drum & Bass” and stick with it. The player’s database is only as clean as your worst file.

Sequence, then listen to the sequence

Track order is a mastering operation, and it matters more on an automated station than on an album, because nobody is choosing to skip. Sit through a full block on a decent set of speakers. Listen for the jump between tracks: does the loudness drop 4 dB when track 3 hits track 4? Does the tonal balance shift so far that it feels like a different station? The ear notices where the maths says it’s fine.

Fix the outliers at the source, then re-render. Do not paper over a bad track with a louder one downstream.

Render to the delivery spec, not to taste

Whatever the destination, master to the spec that destination expects. For file delivery, that means a stable format the player can read (WAV or high-bitrate AAC, not something experimental), correct loudness and ceiling, embedded tags, and a filename convention your library tooling expects. If the destination is a broadcast or syndication feed, ask what it wants and deliver exactly that. General rules of thumb apply less than you’d like, because the format drives the requirements.

Render once. Do not keep tweaking the same track, re-uploading, and wondering why the station sounds inconsistent. The version that hits spec is the version.

Log what you did

A last step that saves you twice as much time next month: a simple spreadsheet or text log with filename, source, loudness target, limiter setting, fade length, and date. When a track sounds off in six weeks you’ll know whether to blame the source or your prep. Without the log, you’ll just re-do the work.

Five steps, then. Level, trim, tag, sequence, deliver. None of it is glamorous, and none of it needs a plugin chain that looks impressive on a screenshot. It just has to be consistent, because on an automated station, consistency is the sound.