Reference library for mixing & mastering engineers

Clients rarely send mastering notes in decibels. A brief usually arrives as “warm, punchy, and loud like the latest Toolroom or Afterlife release.” For a mixing or mastering engineer, the job is translating those adjectives into concrete numbers – integrated LUFS, true-peak headroom, crest factor, and spectral balance – and finding a key-matched lossless reference in seconds rather than hunting through Finder folders.

Organizing references for client briefs

When a client sends a 124 BPM melodic techno mix in G minor (6A), comparing it to a reference at 132 BPM in C major (8B) skews both the perceived groove density and the low-end spectrum analyzer (G1 sits at 49.0 Hz while C2 sits at 65.4 Hz).

ARADAR indexes your local folders of lossless AIFF, WAV, and FLAC masters (plus your own past client masters) without moving or copying the files on disk. Because the app reads embedded ID3 and Vorbis tags on import and stacks filters with AND logic, you can filter by Label + Note/Camelot + BPM + Year in one pass, or pull up custom engineer tags such as vocal-air-ref, tight-60hz, or acoustic-dynamic.

Metering on import: LUFS, LRA, true peak, and crest factor

Instead of loading five candidate files into a DAW session and running offline loudness scans one by one, ARADAR calculates full loudness and spectral metrics automatically on import:

• Integrated LUFS & Loudness Range (LRA). Measured per EBU R 128 / ITU-R BS.1770. You can see immediately whether a reference is a −6.5 LUFS club master with a tight 3.5 LU loudness range or a −12 LUFS dynamic indie record with an 8 LU range, and compare that against Spotify’s published −14 LUFS Normal playback target (−11 LUFS Loud).
• True Peak (dBTP). Inter-sample peak ceiling in dBTP – essential when checking whether a reference is clipped at +0.3 dBTP for club play or held below −1.0 dBTP (or −2.0 dBTP on loud masters) for clean lossy AAC/Opus transcoding.
• Crest factor & RMS. Peak-to-RMS ratio in decibels. Club masters typically sit around 6 to 9 dB of crest factor, whereas dynamic acoustic or film mixes often sit between 12 and 16 dB.
• 10-band frequency profile. Logarithmic octave bands from 20 Hz to 20 kHz with a +4.5 dB/octave visual tilt so a balanced pink-noise-like master reads near horizontal.

Auditioning with band solo, mono, side, and loudness matching

Before dragging a reference into Pro Tools, Sequoia, WaveLab, Logic, or Ableton, you can run your first listening pass right in ARADAR’s player bar.

Turn on Match loudness on playback (to −14, −16, or −18 LUFS) so a −7 LUFS commercial master is attenuated by −7.0 dB to sit at the same perceived loudness as an unmastered client mix. Use the 3×3 check matrix to solo any of six customizable frequency bands (with crossover boundaries editable from 20 to 20,000 Hz in Settings → Playback), fold the signal to MONO, isolate the SIDE channel to hear stereo reverb and widener artifacts, or engage the PHONE band-limit filter (300–4,000 Hz). Active checks stay latched as you click between rows in the library.

The median target and ±1σ custom corridors

Chasing a single reference track carries a classic mastering trap: the one song the client sent might be the brightest or most sub-heavy outlier on the entire label.

When a label has three or more tracks in your library – or when you group 10 to 20 trusted masters into a custom curve – ARADAR generates a median frequency profile with a shaded ±1σ (one standard deviation) corridor across all 10 bands. Overlaying the client’s unmastered mix against that corridor shows both you and the client whether a 4 dB buildup at 200–315 Hz is within normal range for the genre or needs corrective EQ before limiting.

Pulling it together as a studio utility

Keeping your reference archive, past client masters, loudness metering, player-bar checks, and median curves in one local macOS window removes the tedious setup phase at the start of every session. See the ARADAR page for mixing and mastering engineers for a full walkthrough of the engineer workflow.

For why matching the root note of a reference matters when reading an FFT overlay, see why key-matching reference tracks matters. For how AIFF, WAV, and FLAC compare on metadata retention and disk footprint, see audio formats for reference tracks.