Simulation plugins are genuinely useful. You can correct your headphone's frequency response, approximate how a laptop speaker rolls off the bass, and catch obvious problems before you export. What they can't do is put a real phone speaker in front of you while your mix is still playing.

That gap matters more than it sounds. A frequency response curve is a snapshot. A phone speaker in a real room, at your actual listening level, running through your listener's actual earphones, is a living system. The two are not the same thing.

What Simulation Plugins Actually Do

Sonarworks SoundID Reference is the industry standard for a reason. It measures your specific headphones against a neutral target curve and corrects the deviation in real time. The result is a flatter, more accurate monitoring environment than most headphones provide out of the box. The Translation Check feature adds simulations for phones, laptops, and car speakers on top of that correction layer. It's a well-built tool that solves a real problem.

Waves Abbey Road Studio 3 takes a different angle: it uses binaural processing and head-related transfer functions to simulate the acoustic experience of sitting in a real room with real speakers, all through headphones. Useful for spatial judgments that headphones normally obscure.

Audified MixChecker Ultra goes furthest on the simulation side, offering 90+ device models and claiming non-linear distortion modeling -- meaning it attempts to simulate not just the frequency response of a phone speaker but some of its clipping behavior at high levels. That's an ambitious approach.

All three tools are built on the same foundation: measurements taken in controlled lab conditions, turned into static models. They simulate what a device measured like when Audified or Sonarworks captured it. That's valuable data. It's also a fixed snapshot of one device, in one room, at one moment in time.

What Real-Device Playback Reveals That Simulation Misses

When you stream your mix directly to a real phone and listen through whatever the listener in front of you actually owns, several things happen that no plugin model fully captures:

  • Bass rolloff under dynamic load. Most phone speakers roll off below 200-300Hz. But the way that rolloff behaves when your kick drum hits hard is different from a static frequency response curve. At higher playback levels, small drivers distort asymmetrically. A model measured at one SPL doesn't predict behavior at another.
  • Mono collapse. The majority of phone speakers are mono. Your carefully panned guitars, the width in your reverb tails, the stereo field you spent an hour on -- it folds to mono the moment someone picks up their phone. Panning relationships that worked in stereo become masking problems in mono. A simulation can apply mono, but hearing it live on actual hardware makes the problem feel different.
  • Bluetooth lossy codec compression. SBC, AAC, aptX -- every Bluetooth codec applies its own compression algorithm, with its own artifacts and its own effect on dynamic range. AAC on Android is particularly variable in quality. A tightly compressed mix going through a lossy codec can expose pumping artifacts, smeared transients, or a muddy low-mid buildup that no static model predicts, because the interaction depends on your specific audio content.
  • Earphone DSP that changes per listener. AirPods apply Adaptive EQ that adjusts the frequency response dynamically based on your ear canal shape -- independently of any source device EQ. Samsung Galaxy Buds apply their own processing. Bose headphones have their own curve. No profile library can capture these variations because they're device-specific, firmware-version-specific, and in some cases ear-specific. The user on the other end of your mix is not wearing a calibrated headphone. They're wearing whatever they bought at the airport.
  • Your actual listening level. Frequency masking, bass perception, and dynamic behavior all change with playback volume. A simulation at your desk doesn't tell you how the mix holds together when someone is listening at 70% volume while making dinner.

The Test Simulation Plugins Can't Run

The real question is not "what will this sound like on a phone." It's "what does this actually sound like on a phone, right now, while I can still change it."

Here's the test: you're mid-session. You're not happy with how the low end is translating. Instead of exporting, converting, AirDropping, and switching apps -- you pick up your phone, open Auxfeed, and walk away from the desk. The mix is still playing. You're hearing your headphones, your room, your actual phone. The bass question you had answers itself in about fifteen seconds.

You go back to your desk. You adjust. You walk away again. The feedback loop is immediate because there's no file in the middle of it.

That's the test. No plugin runs it because the plugin is a model. Auxfeed streams the actual audio, in real time, over Wi-Fi, to a real device.

Both Tools Have a Place

This is not an argument against Sonarworks SoundID Reference. Headphone frequency response correction is genuinely useful, and Translation Check gives you a fast sanity check without breaking your session. Use it. The point is not that simulation is wrong -- it's that simulation is incomplete.

A corrected headphone is a better monitoring environment. A real phone is a real-world check. Those are different things, and a complete workflow has both.

For a complete guide to using your phone as a reference monitor while mixing, see Phone as Studio Monitor — The Engineer's Guide.

How to Add Real-Device Checking to Your Workflow

The barrier is low:

  1. Download the Auxfeed plugin (free, AU/VST3/AAX) and install it.
  2. Insert it on your master bus.
  3. Open the Auxfeed app on your phone. Both devices need to be on the same Wi-Fi network.
  4. Press play in your DAW. The app connects automatically and starts streaming.

That's the whole setup. From that point on, checking your phone is a 10-second interruption, not a workflow break. Walk away, listen, come back, adjust.

Auxfeed is free at auxfeed.com -- no account, no subscription for Wi-Fi monitoring. Install it once, check your phone any time you mix.