Reference‑track mixing tips
@AjaccioBasket posted pro reference‑track techniques this week — practical steps for using reference mixes to tighten balance and translation across speakers and headphones. The thread includes workflow tips useful for game audio and streaming mixes. (x.com)
AjaccioBasket’s thread mirrors the industry-standard practice of loudness matching during A/B tests — engineers commonly target integrated LUFS levels for fair comparison, with Spotify normalizing to about −14 LUFS and Apple Music around −16 LUFS. (support.spotify.com) Pro workflows recommend using uncompressed reference files (WAV/FLAC) and routing reference audio so it bypasses the mix/master bus to avoid coloration during comparisons. (haolingsheng.com) Experienced mixers typically work with 2–5 genre‑matched reference tracks, toggle quickly between mix and refs, and use spectral and stereo‑width meters to compare tonal balance and imaging. (mixmasterpro.io) Several A/B tools are built for that rapid workflow — commercial plugins like Mastering The Mix’s REFERENCE and free/low‑cost tools such as Mannix Squared’s AB Reference Tool speed looped comparisons and level‑matching. (masteringthemix.com) Game‑audio specialists add engine‑level checks to the reference routine, testing mixes inside FMOD/Wwise builds and on target hardware because middleware, compression and platform pipelines change perceived balance. (gameaudiolearning.com) For live‑stream and streamer mixes the accepted practice is to verify references on typical listener devices — closed and open headphones, phone/Bluetooth speakers — and to assemble a short 6–8 track check list that’s already been validated on those devices. (sonarworks.com)
