You bought an Audio Unit plugin, or you already own one bundled with a DAW you like, and it does something useful: a specific saturation, a de-esser that actually works, a tape emulation you trust. Then you go to watch a movie or listen to a podcast and none of it is there, because AU plugins only run inside a host that loads them, and a media player is not that host.
That gap is not a bug in the plugin. It is where Audio Units were designed to live.
Why AU plugins are stuck inside DAWs
An Audio Unit is a plugin format, not a standalone program. It has no way to receive audio on its own, no output device of its own, and no window unless something hosts it. A DAW hosts it by routing a track’s audio through the plugin’s process callback and back into the session.
That hosting relationship is what is missing for system-wide use. QuickTime, Music, Safari, Zoom, none of them are AU hosts. They play audio directly to the output device, with nothing in between. The plugin format is fine; there is simply no host sitting in the path.
This is also why the fix is not “a better media player.” No app that just plays files is going to add a full AU hosting engine for one feature. The host needs to sit below every app, not inside one of them.
The options, roughly in order of effort
Print the effect once, in the DAW you already have. If you love how a plugin colors a specific recording, run that file through your DAW, bounce it with the plugin printed, and play the bounced file normally. This costs nothing extra and is the right call for a one-off render. It does nothing for live playback, calls, or anything you did not bounce in advance.
Use a dedicated AU host app. A handful of small apps exist purely to load one AU plugin and pass one input into it, often built for guitarists monitoring an amp-sim plugin. They work, but you route only one source through them, and they do not touch the rest of your system audio.
Use a system-wide virtual audio driver with a built-in AU host. This is the only approach that covers everything at once: browser audio, calls, games, background music. It requires a driver-level component because that is the only place in macOS that sees all system audio before it reaches the speakers. Software that stays at the application level, by design, only sees its own output.
Doing it with ZonaReq
ZonaReq’s driver sits below every app and feeds system audio through a processing chain before it reaches your output device. Because that chain already exists for the EQ and reverb, it can host third-party Audio Units on the same signal.
- Install ZonaReq and confirm audio is routing through it: pick your real output device in the main panel and confirm sound plays normally.
- Open the plugin host section and add an Audio Unit from the list of AU effects already installed on your Mac.
- Adjust the plugin’s own interface, which opens as usual, since ZonaReq is just supplying it with a continuous stream of system audio instead of a DAW track.
- Reorder it relative to the EQ and reverb if the effect is sensitive to what comes before it, a compressor after a boost behaves differently than one before it.
- Leave it running. It applies to everything played through the device from that point on: browser, calls, games, whatever is loudest at the moment.
What this does not fix
Not every AU plugin is meant for a continuous, unpredictable signal. Plugins built around fixed sample buffers, offline analysis, or a specific sample rate negotiated once at project load can behave oddly when fed a live stream that changes source constantly. Instrument plugins do not apply here at all, they need MIDI input, not audio, and have nothing to process from system playback.
Latency is also a real constraint. Adding a plugin to the chain adds its own processing time on top of the driver’s own overhead, and a heavy plugin can push total latency past what feels comfortable for video calls, where lip sync matters. If a plugin was designed for tracking rather than mixing, it likely was not tuned to be fast enough for that use.