Someone installs a “system equalizer” expecting it to reshape everything they hear at once: a podcast in the browser, a call in a meeting app, a game running in the background. Some tools genuinely do that. A lot of them quietly don’t — they turn out to be the equalizer built into one music player, dressed up to sound bigger. That gap between what people expect and what most audio software actually reaches isn’t a bug. It’s a direct consequence of how macOS moves sound from an app to a speaker.
To see why, it helps to follow a sound from the moment an app decides to make it to the moment it leaves the speaker.
Where your audio actually goes
An app doesn’t write directly to your speakers. It renders audio into buffers through Core Audio, macOS’s audio framework, and hands those buffers to whatever output device is currently selected. If only one app is playing sound, that’s the whole story. But your Mac routinely has several apps producing audio at once — a browser tab, a notification sound, a call — all aimed at the same device. Something has to combine those separate streams into the single signal that actually reaches the hardware.
That combining step happens in one place: the audio system that manages the chosen output device. Every app’s contribution funnels through it before anything is played.
The one door that’s shared
Everything before that mixing step is private to each app. Everything at it and after it is shared. That split matters if you want to build something that changes “everything,” because there are only two ways to get there. One is to convince every app you care about to add a hook for your effect — unrealistic when the apps in question are closed-source and not interested in adding one for you. The other is to place yourself exactly at the shared step, so whatever arrives there passes through you first.
Placing yourself there means presenting your software to macOS as an output device. Not a plugin that lives inside one player, but something the operating system treats the same way it treats a speaker or an interface: a destination that apps write to and that macOS is willing to send the combined mix through. That’s what a Core Audio driver is — a small piece of software, loaded by the system’s audio process rather than run as an ordinary app, that shows up in the output list and gets first look at the mix before it’s handed to real hardware.
This is also why a system equalizer can do per-application volume: the driver is the one place that still knows which chunk of the mix came from which app, right before it blends them. Downstream of that point, it’s just one signal.
Why it needs a password and a restart
A driver isn’t a file you drop into your Applications folder. macOS looks for audio drivers in a system-owned location, one that a regular app has no permission to write to. Copying a new driver bundle there needs administrator rights, which is the password prompt. That’s not a formality the developer added for effect — it’s the same protection that keeps any process from quietly inserting itself into every app’s audio without you noticing.
The restart requirement follows from how the audio system finds drivers in the first place: it looks for them when it starts up, not continuously while running. Installing or removing one takes effect only after that process is restarted. Every app that had an open audio connection loses it in the process, which is why they need to be reopened or refreshed afterward — not because the driver broke something, but because their session with the old audio process no longer exists.
Capture is not control
macOS does have a lighter-weight way to get at system audio: recent versions let an app request a copy of what’s playing, without installing anything. Screen recorders and meeting transcribers use this. It’s a fine solution for what it does, and it doesn’t deserve an admin password, because it isn’t one.
The distinction is that a copy arrives after the fact. It lets an app listen in and record what’s about to reach your speakers; it doesn’t let that app change what actually reaches them. An equalizer has to modify the signal before it becomes sound, not describe it afterward. That difference — hearing a copy versus shaping the original — is exactly the line between “needs a tap” and “needs a driver.”
Where this leaves a tool like ZonaReq
ZonaReq is built at the position this piece has been describing: a Core Audio driver, written in plain C because the sandbox the driver process runs in doesn’t support Swift, sitting at the shared mixing step. It receives the combined signal from whatever apps are playing, applies equalization, reverb, or other processing, and passes the result on to your actual output device. Per-app volume and mute work the same way, from inside that same driver. None of this is unique to ZonaReq — any tool, free or paid, that reaches every app on your Mac at once is built the same way, with the same driver folder, the same admin prompt, and the same restart.
That’s also honest grounds for skipping it. If the only sound you want to shape lives inside one player — the Music app, a browser tab, one streaming service — its own built-in equalizer, if it has one, does the job with no driver, no password, and no restart. It just won’t follow you to the next app you open.
What actually changes for you
If a “system equalizer” never asked for an administrator password, it isn’t touching the whole system, regardless of what the name implies — it’s shaping one app’s output and calling it universal. And if installing one does ask for a password and briefly interrupts your other apps’ sound, that’s not a malfunction to work around. It’s the one moment the operating system lets something new stand at the point where all your audio already meets.