How to Normalize Audiobook and Podcast Audio to a Consistent Volume

Chapter three is whisper-quiet, chapter four blows your earbuds out; last week’s episode needs the volume up, this week’s needs it down. Spoken audio has the same disease as music libraries, but it answers to two different rulebooks: audiobooks inherited an 89 dB tradition from the ReplayGain world, while podcasts standardized on LUFS. MP3Gain genuinely fits one of those jobs and only half of the other. Here is the honest map, and the workflow for each.

Audiobooks: the 89 dB tradition is MP3Gain’s home turf

The world’s largest volunteer audiobook project, LibriVox, has asked narrators for the same thing for years: an overall volume of around 89 dB — its wiki gives an acceptable band of roughly 87–91 dB, ideally 89 — so that consecutive chapters and different narrators sit at one level. LibriVox even ships a small program, Checker, that measures an MP3’s volume and technical specifications so contributors can verify a file before submitting it. That 89 dB figure is ReplayGain thinking: the same reference MP3Gain uses as its default target. Which means the tool already on this site speaks the audiobook world’s language natively, no translation layer required.

The chapter workflow. Collect the finished chapter MP3s in one folder. Add the folder to MP3Gain and run Track Analysis: the per-file values immediately expose the outlier chapters. Apply Track Gain at the default 89.0 dB target with the clipping guard on. Spot-check the loudest and quietest chapters by ear, then run the files through Checker (for LibriVox submissions) or simply play chapter boundaries back-to-back. The whole pass is lossless and reversible — if a narrator re-records one chapter, re-run just that file to the same target and the set matches again. For libraries of hundreds of files, the backup-first routine in batch normalizing a large MP3 library applies unchanged.

The boundary: gain cannot fix dynamics inside a chapter

MP3Gain applies one gain value per file (or one shared value per album). That fixes file-to-file consistency perfectly — and does nothing about a chapter that whispers its dialogue and shouts its narration, because that unevenness lives inside the file. Evening out within-file dynamics is compression’s job, done in an audio editor before the leveling pass, and no normalizer of any brand changes that division of labour; LibriVox’s own guidance makes the same point, reaching for compression when plain amplification is not enough. Likewise, MP3Gain will not remove hiss, repair clipping, or rescue a bad recording — it preserves the file faithfully at a better level. Sequence your fixes honestly: edit and compress first, level last.

Podcasts: a different rulebook, measured in LUFS

Podcasting standardized on the broadcast measurement instead. The industry convention — the target Apple Podcasts has long published — is about −16 LUFS integrated for stereo episodes and −19 LUFS for mono, with true peaks kept around −1 dBTP. Those are BS.1770 loudness numbers (the full ReplayGain-versus-LUFS comparison is in ReplayGain vs LUFS), and they are measured with a loudness meter, typically at the final master in your editor. That is the step that makes episodes match each other and sit correctly next to every other show in a listener’s app — some platforms also normalize playback, but delivering at the conventional target is what keeps your show consistent everywhere, including the apps that do not.

Where MP3Gain fits podcasting — and where it stops. For a finished stereo master that must hit −16 LUFS, MP3Gain is the wrong instrument: it neither measures LUFS nor touches true peak, so it cannot certify the number a platform expects. Its legitimate podcast role is narrower and practical: a back catalog of MP3 episodes that are uniformly out of line with each other — an early season mastered timidly, a later one mastered hot. A Track Gain pass at one shared reference makes old episodes consistent with each other in one reversible batch, which is a real improvement for binge listeners; then verify a sample episode with a LUFS meter and, if it must meet the −16 LUFS convention exactly, finish the job in an editor’s loudness normalization. Use each tool for the measurement it actually makes.

For narrators and hosts: leveling is the last step, not the first

Everything above assumes finished files. If you are the person recording them, the cheapest loudness fix happens before any software runs: record every chapter or episode at the same input level, in the same room position, with the same microphone distance. A narrator who sits in the same place and watches the same meter range produces chapters that barely need leveling; a host who records one episode at a desk and the next in a car produces files no normalizer can fully reconcile, because the room tone and dynamics changed along with the volume. Treat recording consistency as the foundation, editing and compression as the shaping, and the final gain pass — MP3Gain for audiobook-style targets, a LUFS meter for podcast masters — as the inspection stamp at the end. Skipping to the stamp is how volumes end up technically matched and obviously different.

“Can I just run my podcast through MP3Gain and call it −16 LUFS?” No — and the reason is worth keeping straight, because the two numbers are answers to different measurements. MP3Gain will make your episodes consistent with each other at a ReplayGain reference; −16 LUFS is a BS.1770 integrated loudness value with a true-peak condition attached. Episodes leveled by MP3Gain will often land in a plausible neighbourhood, but “plausible neighbourhood” is not the deliverable a platform’s spec describes, and the honest final step for a podcast master is a loudness measurement in a tool that reports LUFS and true peak directly. Consistency first, certification second, each with its own instrument.

One-page summary

Spoken word rewards consistency more than music does — a listener in a car, on a run, or falling asleep to a chapter cannot keep reaching for the volume, and will blame the book or the show, never their own playback chain. Match the rulebook to the job, and both jobs are an afternoon’s work. One practical closing note for both crafts: keep an unleveled archive copy of every finished file. Leveling with MP3Gain is reversible from its own tag data, and a LUFS master can always be re-exported — but an untouched archive makes every future standard change a fresh start instead of an archaeology project, and standards in spoken audio have changed before.

LUFS for DJs: What Loudness Should Club Tracks Be?

Streaming taught every DJ a number — usually −14 LUFS — and the number is real, but it answers a question a club never asks. A streaming platform normalizes playback, so a target exists. A PA system does not: it plays your file at whatever level the file carries, through whatever the last DJ left on the mixer. For live DJ files, consistency across your crate matters far more than any absolute LUFS figure. Here is how the numbers actually fit together, and what to do with them.

LUFS in sixty seconds

LUFS (Loudness Units Full Scale) measures perceived loudness across a whole track using the BS.1770 method: frequency weighting that mimics human hearing, plus gating that ignores silence and quiet tails. “Integrated LUFS” is the single whole-track number everyone quotes. It is an excellent measurement — the deep comparison with the older ReplayGain system that MP3Gain uses is in ReplayGain vs LUFS. What matters here is the difference in purpose: LUFS targets were designed for broadcasters and platforms that adjust playback volume centrally. A club rig adjusts nothing.

Where −14 and −12 come from

−14 LUFS is the normalization target used by Spotify and roughly shared by YouTube and other streaming services: upload louder and the platform turns you down; the number exists so that consecutive songs on a playlist sit at one level. −12, −11, even −8 LUFS figures circulate in DJ and mastering forums as targets for club tracks — these describe how hot many commercial club masters actually measure, not a standard anyone enforces. A track mastered to −8 LUFS integrated is not “wrong” in a club; it is simply loud and heavily limited, and it will sit happily next to a −13 LUFS track only if someone or something evens out the difference at playback. On a streaming upload, the platform is that something. Live, the something is you — or your files, prepared in advance.

Can you “set” a DJ file to −14 LUFS with MP3Gain?

No — and any tool or tutorial claiming a clean conversion is rounding aggressively. MP3Gain does not measure LUFS at all; it applies ReplayGain toward its 89.0 dB reference. The two systems are cousins, not twins: different frequency weighting, and ReplayGain has no BS.1770-style gating. There is therefore no exact conversion between an MP3Gain target and a LUFS value. As a deliberately rough orientation only: material leveled to MP3Gain’s 89 dB default commonly measures somewhere in the mid-to-high teens below full scale when you check it with a LUFS meter — near the streaming neighbourhood, typically a little quieter, and varying by genre and master. Treat that as a sanity range, never as an equals sign. If a deliverable genuinely specifies a LUFS number — a recorded set going to a platform, a release, a promo — measure and set it with a BS.1770 tool; waveAlign is the DJ-focused example we compare against MP3Gain, precisely because LUFS is its native language.

What club DJs should actually optimize

Consistency across the crate. A library where every track sits within a decibel or two of its neighbours lets you mix with trims near centre and your ears on the music. This is the entire job of the pre-gig MP3Gain workflow, and it works regardless of what the shared level happens to be. Peak headroom. Whatever the loudness, files driven to the last fraction of a decibel leave the mixer and any downstream processing nothing to work with; MP3Gain’s 89 dB default plus its clipping guard keeps peaks honest, which is worth more on a big rig than two extra decibels of loudness. Knowing which destination normalizes. The same track may need no target at all for the club, −14 LUFS awareness for a streamed set, and nothing but consistency for a USB handed to the next DJ. Decide per destination instead of worshipping one number.

A practical loudness routine for working DJs

You do not need a metering lab; you need a reference and a habit. First, learn your own library’s landscape. Take ten tracks you trust — professionally mastered, recent, the ones that never surprise you — and measure their integrated LUFS with any BS.1770 meter (most DAWs and several DJ-adjacent tools include one). That range, whatever it turns out to be, is your scene’s real-world loudness: it tells you far more than a forum’s favourite number, because it describes the music you actually play. Second, level for the room, measure for the upload. Run the library through the shared-reference pass described in MP3Gain for DJs so live playback is consistent, and reserve actual LUFS targeting for artifacts that leave the booth: recorded sets, streams, promos. Two different deliverables, two different standards, no contradiction. Third, re-check after big intake. A hundred new promos can drag a leveled library’s balance sideways; a fresh analysis pass on the new folder, against the same target as the old one, restores the equilibrium in minutes.

And keep the limiter question straight: a club track that was mastered hot already had its peaks managed by the mastering engineer. Nothing in a leveling pass adds limiting, and your job is not to re-master the catalogue — it is to make the catalogue behave like one collection. Loudness wars are fought at mastering. Consistency is won at the library desk, which is where you are sitting.

The two questions DJs actually ask

“Should I normalize all my DJ tracks to −14 LUFS?” Only the copies destined for a normalizing platform. For the live library, leveling tracks to each other beats leveling them to a streaming figure — and if you do produce a −14 LUFS version of a recorded set, keep it as a separate export, never as a replacement for your working files. “My tracks measure all over the place — is that a problem?” For playback in one set, yes, and it is the fixable kind: mixed integrated readings mostly reflect different mastering eras, and a ReplayGain pass at a shared reference removes the practical problem (audible jumps) even though the files’ LUFS readings will still differ slightly afterwards, because the two systems weigh loudness differently. Close and consistent beats theoretically perfect and untouched.

One last confusion: loudness is not volume

It is worth separating two ideas the numbers blur together. Loudness, in every system on this page, is a property measured from the file — how intense the programme material is, weighted for human hearing. Volume is what the room does with it: the master fader, the limiter on the rack, the size of the PA. A DJ does not control the second and should not try to encode it into the first by mastering files ever hotter “for big systems” — big systems have amplification precisely so files do not have to. Keep files consistent and honest; let amplifiers be amplifiers.

Does MP3Gain Mess Up Cue Points and Beatgrids? (rekordbox & Serato)

Short answer: no — and the reason is mechanical, not a matter of trust. Cue points and beatgrids are positions in time. MP3Gain never re-encodes your file, never touches its timing, and never changes its length, so there is nothing for a time position to drift away from. The fear is understandable, because other “normalizers” genuinely can shift your audio. This page explains the difference, what MP3Gain does change, and the one housekeeping step worth doing afterwards.

Why cue points are time, and time is untouched

When you set a hot cue at 1:32.400 or a beatgrid anchored to the first downbeat, your DJ software stores a position measured against the track’s timeline. Anything that preserves the timeline preserves every marker on it. MP3Gain’s entire design is timeline preservation: instead of decoding the MP3 to audio, changing the volume and encoding a new file, it adjusts the gain value stored inside each existing MP3 frame — the digital equivalent of writing a different number on the volume knob of every frame, in place. The audio data, the frame sequence, the duration and the timing are exactly what they were. A cue at 1:32.400 points at the same kick drum before and after, because the kick drum never moved.

Why the fear exists: re-encoding tools are a different story

Many volume tools — and every general audio editor used carelessly — work by decoding and re-encoding. Encoding an MP3 introduces encoder delay and padding at the start of the file, and a decode–edit–encode round trip can shift the audio by small amounts, rebuild the file’s structure, and rewrite its tags from scratch. Small shifts are exactly what break tight beatgrids and loops. MP3Gain was written in 2001 specifically to avoid this: no decode, no encode, no generation loss, no shift. If a tool cannot describe its method as “adjusting the gain field in each frame,” it is not doing what MP3Gain does.

What MP3Gain does change — honestly

Three things, none of them timing. First, loudness itself: that is the point of the tool. Second, tags: MP3Gain writes its analysis and undo information into the file’s tags (APEv2, or ID3v2 depending on settings), which is how its changes stay reversible years later. Tag-writing is a metadata operation; it does not move audio. Some older players have quirks reading APE tags — if you ever meet one, the symptom is tag display oddities, not broken cues, and our troubleshooting hub covers the tag-related fixes. Third, your DJ software’s stored picture of the track: analysis data such as auto-gain values and overviews were computed from the old loudness. They are not wrong about where things are; they are stale about how loud things are.

The one step to run afterwards: re-analyze

After a leveling pass, let rekordbox or Serato re-analyze the changed files. Re-analysis refreshes the loudness-derived data — auto-gain values and waveform overviews — so the software’s model matches the files’ new levels. Where your software keeps its analysis in its own database, that database is untouched by MP3Gain and simply gets its loudness entries updated on re-analysis; where data is kept with the track, the same refresh applies. Either way, the division of labour is clean: MP3Gain changes how loud the file is; re-analysis teaches your software the new fact. Cues and grids, being time data rather than loudness data, come through the whole process unchanged — but do the five-minute verification below anyway, because trust in a library is earned per workflow, not per article.

“My waveforms look different afterwards — did something break?”

Probably not, and the picture is worth understanding. The waveform overview your software draws is a loudness picture: it renders how much energy the track has over time. Level a quiet track up by 5 dB and its overview will be redrawn — after re-analysis — visibly taller, because the track genuinely is louder now. That redraw frightens people into checking their grids, which is healthy, but the thing to check is position, not height: the peaks and silences in the new picture sit at the same times as in the old one, because they are the same audio. Height is loudness; position is time; MP3Gain changed the first and cannot change the second. If an overview ever does appear shifted — a drop landing visibly earlier or later than your cue — that is the signature of a file that was re-encoded or replaced somewhere in its history, not of a gain adjustment, and the cure is to go back to the unleveled backup copy you made in step one of the protocol below and compare the two files directly.

One more reassurance for the export-minded: DJs who prepare USBs worry about the copy on the stick rather than the copy in the library. Leveling happens to the library files themselves, so any export made after the pass carries the leveled audio — the export contains the same files, with the same timing, at the new level. Export first and level afterwards, and you would simply export again; nothing about the workflow locks you in.

The safe first-run protocol

1. Copy one crate folder — twenty or thirty tracks you know intimately — and level the copy with the workflow in MP3Gain for DJs. 2. Load three of those tracks in your DJ software and jump through every hot cue: each should land exactly where your muscle memory expects. 3. Check one tight loop and one track where you set the grid manually. 4. Only then run the full library, using the backup-and-batch routine in how to batch normalize a large MP3 library. If anything ever looks off, MP3Gain’s undo restores the original gain from its tag data — the experiment is reversible by design.

And loops, memory cues and saved markers?

The same logic covers every marker type, because every marker type is a position. A loop is two positions; a memory cue is a position with a label; a grid is one anchor position plus arithmetic. None of them is stored as “the loud part about two-thirds in” — all are times or beat counts measured from the start of a file whose start, length and internal timing MP3Gain leaves exactly as found. This is also why the verification protocol is so short: you are not checking six features, you are checking one property — timing — through whichever feature you know best. If your most-loved cue lands where it always lands, every positional feature on that track is home.

So, the whole answer in one paragraph

MP3Gain cannot move your cue points or beatgrids, because it never re-encodes and never alters timing — it edits a gain value inside each frame and writes undo data to the tags. What it changes is loudness, which is why your DJ software deserves a re-analysis pass afterwards to refresh its loudness-derived data. Keep a backup, test on one crate, verify three tracks by hand, then level the library with confidence. If the remaining question is whether to rely on the software’s own leveling instead, that argument is laid out in rekordbox Auto Gain vs MP3Gain.

rekordbox Auto Gain vs MP3Gain: Trust the Software or Fix the Files?

Every major DJ application now levels your tracks for you — and every one of them does it differently, keeps the result in a different place, and forgets it the moment you step outside that app. MP3Gain takes the opposite bet: change the file once, losslessly, and the leveling travels with the music forever. Neither approach is magic. This page explains what each auto-gain system actually does, so you can decide which layer deserves your trust.

What rekordbox Auto Gain actually does

When rekordbox analyzes a track, it calculates an auto-gain value (shown as A.GAIN) intended to bring the track to a consistent playback level, and stores that value with the track in the rekordbox collection. With the Auto Gain preference switched on, the value is applied as you play, and you can fine-tune it per track in the grid editor. Two limits matter. First, the value lives in rekordbox’s world, not in the audio — play the same file in another application or a media player and it is exactly as uneven as the day you downloaded it. Second, Pioneer’s own support forum states plainly that auto-gain data is not stored in exports: prepare a USB for standalone club gear and the leveling work you did inside rekordbox does not ride along. The file is the only thing the CDJ ever sees.

The other three, briefly

Serato DJ. Serato’s manual describes its Use Auto Gain option this way: during the overview-building (analysis) process it calculates an auto-gain value for each track — the adjustment needed to match the track’s perceived loudness to a reference level you choose, from 89 dB (quieter) to 98 dB (louder), with 92 dB the recommended default. The value is applied each time the track loads, by setting the track gain knob. Note what that means: Serato’s reference is its own, its default is 92 dB rather than anyone else’s number, and the result is a playback setting inside Serato’s ecosystem.

Traktor. Native Instruments’ manuals describe Autogain as relying on gain values extracted when a track is analyzed on import; a “Set Autogain When Loading Track” preference applies that stored value as the track loads, and the auto-gain value is kept separately from the channel gain you set by hand. Same pattern: analysis inside the app, value inside the app’s data, silence everywhere else.

VirtualDJ. VirtualDJ’s Auto Gain normalizes a track toward a 0 dB level for playback, and its default “Auto+Remember” mode additionally remembers gain tweaks you make by hand. A 0 dB target is a peak-style goal — a different philosophy from the perceptual loudness matching above, and one more reason the four apps do not agree with each other about how loud a track “should” be.

The disagreement, tabulated

“But doesn’t the software write something into the file?”

Sometimes, yes — and it changes nothing about the argument. Serato’s manual, for example, notes that a track gain adjustment made in the software is saved to the file and retained for the next load. What is saved is Serato’s own gain value, in Serato’s own terms: a playback instruction that Serato reads. rekordbox does not apply it, your media player does not apply it, a CDJ reading the bare file does not apply it — and crucially, it is not a change to the audio itself, so the file’s actual loudness, the thing every other playback chain responds to, is exactly what it was. A note in one app’s handwriting, stored in the file’s pocket, is not the same as the file being level. MP3Gain’s adjustment is the opposite arrangement: no app-specific instruction at all, just an audio file that is measurably at the shared level for anything that plays it.

The same distinction explains a common confusion: a track can carry a pocketful of metadata — one app’s gain tag, another’s analysis markers — and still blast or whisper the moment it is played somewhere that reads only the audio. When DJs say leveling “didn’t stick,” it is almost always because the leveling they did lived in that metadata layer. File-level gain is the layer that cannot fall off.

When the software’s auto gain is genuinely enough

If you play on one laptop, in one application, and never export to standalone gear, auto gain is convenient and mostly effective: the app re-levels on load and you touch nothing. It is also the only option for formats MP3Gain cannot touch. For a single-app, single-machine DJ, this page is not an argument to change your life — it is an explanation of the boundary you are inside.

When file-level leveling wins outright

The moment any of these is true, the file is the only common denominator: you export USBs for CDJs or XDJs; you keep a backup laptop with different software; you share tracks with a B2B partner; you play the same files in a media player, a car, or a warm-up stream; or you simply want the leveling decision to outlive whichever app you happen to use this year. Software comes and goes — DJs have already buried several industry-standard applications. The MP3 file, leveled once, does not care.

There is also a quieter asymmetry worth noticing: auto gain is computed when a track is analyzed, from the file as it exists at that moment. Add a track in a hurry before a gig and, depending on the application and your settings, it may be played with provisional or missing analysis — the one situation where you most need the help is the one where the database has not caught up. A leveled file needs no catching up: its level is a property of the audio itself, true on first load, on any machine, including machines that have never heard of your library. Reliability that depends on a database staying in sync with a folder of files is a different, weaker kind of reliability than a file that is simply right.

The sensible combination

These are layers, not enemies. Level the files with MP3Gain first (the full workflow is MP3Gain for DJs), then let your DJ software re-analyze: its auto gain now starts from files that are already close, so it only ever applies small corrections instead of heroic ones. Two cautions. Do not chase loudness twice — if a track still feels quiet after both layers, the honest answer is that it was mastered quiet, and the trim knob exists for the last decibel or two. And re-analyze after leveling rather than trusting stale analysis values; your cue points are safe through all of this, for the reasons in the cue point explainer. If your real requirement is loudness measured to the modern LUFS standard across several formats, that is a different tool class entirely — see MP3Gain vs waveAlign and LUFS for DJs.

MP3Gain for DJs: Level Every Track in Your Library Before the Gig

Every DJ library drifts. Tracks arrive from download stores, promo pools, old CD rips and friends’ USB sticks, each mastered in a different year to a different loudness. The result is a set where you ride the trim knob on every single transition. MP3Gain fixes that at the file level — once, before the gig, for every player and every piece of software you will ever load the track into. This page is the full pre-gig workflow, in checklist order.

Why DJ files need leveling more than most

A home listener’s library grows from a handful of sources. A working DJ’s library is an archaeological dig: 2009 blog-house rips next to 2024 Beatport masters, vinyl transfers next to radio edits. Loudness differences of 6–10 dB between neighbouring tracks are normal, and no mixer trim habit fully hides them — the quiet track also gets less presence from the channel EQ and effects, because everything downstream receives a weaker signal. Leveling the files themselves is the only fix that survives changing software, changing laptops and standalone players.

The pre-gig checklist

1. Back up the folder you are about to touch. MP3Gain’s changes are reversible — it stores undo information in the file’s tags — but a plain copy of the crate folder on another drive is the safety net that covers every accident, including the ones that are your fault. Work on the backup’s twin, never on your only copy. Our batch normalization guide covers the large-library safety routine in detail.

2. Start with one crate, not the whole archive. Level this week’s working playlists first. A 60-track test batch teaches you the workflow, proves the result in your software, and keeps any mistake small. Scale up to the full archive once the loop below feels routine.

3. Choose Track Gain or Album Gain deliberately. For club singles and a crate of unrelated tracks, use Track Gain: every file independently brought to the same target. For full EPs or albums you genuinely play in sequence, Album Gain preserves the intended loud-to-quiet arc between tracks. The full decision logic — including compilations and random play — is in Track Gain vs Album Gain.

4. Keep the 89.0 dB target, and tick the clipping guard. MP3Gain’s default target of 89.0 dB leaves headroom, which is exactly what a mixer wants to see. In the options, enable “Don’t clip when doing Track Gain” so a track that cannot reach the target without clipping is left slightly quieter instead of distorted. What the red clipping column is telling you is covered in MP3Gain’s clipping warnings, explained.

5. Analyze first, then gain, in one pass. Add the folder, run Track Analysis, scan the results for outliers — a track needing +12 dB is usually a bad rip, not a leveling candidate — then apply Track Gain. The analysis values stay visible afterwards, so you can audit exactly what changed on every file.

6. Fix wrong formats before you level. MP3Gain only works on MP3 files; it will simply ignore the WAV, AIFF or M4A files in the folder. If your players expect a specific format, convert the odd files to that CDJ-friendly format before leveling, so every file in the crate goes through the same single pass. A batch converter such as Wondershare UniConverter handles that conversion step; do the converting first and the MP3Gain pass last, so nothing gets processed twice.

7. Re-analyze inside your DJ software. Back in rekordbox, Serato or your software of choice, let it re-analyze the changed files so its stored auto-gain and overview data reflect the new levels. Your cue points and beatgrids are not at risk — MP3Gain never re-encodes, so nothing about the timing moves; the dedicated explainer is Does MP3Gain mess up cue points and beatgrids? What re-analysis updates is only the software’s picture of how loud each file now is.

8. Sound-check with the trims at twelve o’clock. Load five tracks from different eras of the crate, trims centred, and mix. If you are no longer reaching for the gain knob on every transition, the library is done. Small per-track trim is still normal musicianship — you have removed the big jumps, not the craft.

Three mistakes that quietly undo the workflow

Leveling before you finish converting. Every file that changes format after the MP3Gain pass — a WAV you convert to MP3 next week, a re-download at a different bitrate — arrives unleveled, and one loud outlier in a crate is all it takes to bring back the trim-diving. The order in the checklist is deliberate: settle the crate’s contents and formats first, level last, and treat any later addition as a mini-pass of its own: analyze the newcomer against the same 89.0 dB target before it joins the folder.

Chasing the last decibel with the target slider. Raising the target to 92 or 95 dB because 89 “looks quiet” misunderstands what the number does. The target sets the shared level, not the excitement; push it up and the clipping guard simply leaves more tracks below target, recreating the unevenness you came to remove — now with the loudest tracks pinned and the quiet ones still quiet. If the whole set feels low on a particular rig, that is what the mixer’s master and channel trims are for. Keep the library at the reference and let the room decide the rest.

Skipping the re-analysis because the cues look fine. They will look fine — cues are time positions and nothing moved them. The stale data is quieter about its staleness: your software’s auto-gain values were computed from the old loudness, so with auto gain engaged it may now correct in the wrong direction on some tracks, trimming files that are already level. Re-analysis takes minutes for a crate and is the step that makes the two leveling layers cooperate instead of argue. Do it once, right after the pass, not during soundcheck.

What this workflow deliberately leaves out

MP3Gain does not measure in LUFS, does not touch non-MP3 formats, and does not repair tracks that were clipped at mastering — it preserves damaged files faithfully at a consistent volume. Those are three different jobs. For loudness measured to the modern broadcast standard, see LUFS for DJs and the waveAlign comparison. For files that need actual repair rather than leveling, that is the territory of Platinum Notes. And if your software’s built-in leveling tempts you to skip all of this, read rekordbox Auto Gain vs MP3Gain first — the short version is that auto-gain values live inside each app, while your leveled files are level everywhere.

Playing your own remixes, too?

Everything above is about playing other people’s music well. If some of the tracks in the crate are your own edits and remixes, the step after leveling is distribution — getting them onto the streaming platforms your audience already uses. That is a separate job handled by music distribution services; the two names DJs most often end up comparing are LANDR and DistroKid. Level the files first either way: a remix that leaves your library at a consistent volume is a better master candidate than one that has only ever been judged against your trim knob.