Tahoe fixed real bugs.
It didn't fix the gap.

macOS 26 Tahoe was the release where Apple's version numbering jumped to match the year, and where a lot of the interface got rebuilt. For anyone who cares about per-application audio, the interesting parts were quieter than the headline features — and mixed.

Here is the accounting: what Tahoe broke, what it repaired, and what it left exactly where it was.

What didn't change: there is still no mixer

Tahoe did not add per-application volume control. System Settings → Sound still gives you one output volume, a separate alert volume, and device selection. If two apps are at the wrong level relative to each other, macOS offers nothing.

Nor did Apple change the Core Audio process tap API in any way that alters what third-party tools can do. Process taps — public since macOS 14.2, matured by 14.4 — remain the mechanism behind every driverless per-app mixer, still gated behind the one-time System Audio Recording permission. If you were hoping Tahoe would make the whole category unnecessary, it did not. The longer answer to that question is a separate piece.

What broke in 26.0

This is the part worth knowing, because it is a clean illustration of the risk of building on a young API. Rogue Amoeba — who have been shipping audio capture software on the Mac for two decades and document this territory more carefully than anyone — published an accounting of what Tahoe got wrong and then right. The notable regressions in 26.0:

• FaceTime and the new Phone app could not be captured in many setups. For anyone recording calls, that is not a rough edge, it is the feature gone.
• Captures failed when a secondary output device ran at a different sample rate from the system default — an extremely common situation the moment you own an audio interface as well as built-in speakers.

Both were fixed in macOS 26.1, along with a break in retrieving Apple Music track titles.

What Tahoe actually repaired

Against those regressions, Tahoe fixed a set of genuinely long-standing problems — several of which had annoyed people for years:

• The system's low-pass filter on captured audio. macOS was applying a strong low-pass filter to all audio captures, quietly dulling anything recorded this way. Tahoe applies it far less aggressively. For podcasters and anyone recording system audio, this is the most consequential item on the list.
• Safari clicking at 44.1 kHz. Audio played by Safari could skip or click when captured at that sample rate. Resolved.
• Siri while capturing. The system could fail to recognise spoken requests while an audio capture was running. Improved.
• Low sample rate captures. A regression introduced back in macOS 15 Sequoia, where captures failed when audio played at low sample rates, was finally restored.
• Stream group devices. Interfaces from MOTU and Apogee that use stream groups could capture the wrong audio, or silence audio that should have been inaudible. Fixed.

The separate Tahoe audio story: crackling and dropouts

Alongside the capture-specific issues, Tahoe generated a broad wave of reports about crackling, popping and dropouts unrelated to per-app audio — generally traced to coreaudiod getting into a bad state, sample rate mismatches between the Mac and an output device, or Bluetooth behaviour after the update.

If that is what you are experiencing, it is a system-level problem and not something a per-app mixer causes or cures. The usual first moves are to check that your output device's sample rate in Audio MIDI Setup matches what you are playing, to restart the Core Audio daemon, and to make sure you are on the latest point release rather than 26.0.

What this means practically

• If you are on 26.1 or later, the picture is good. Better than Sequoia was, on the specific question of capture quality.
• If you depend on this for work, do not rush an x.0. Tahoe 26.0 is a textbook case. The API is young and Apple's documentation of it is thin; major releases will keep surfacing issues faster than they would on a settled API.
• Nothing here is a reason to go back to virtual audio drivers. The driverless approach still means no admin password, no restart, no changed default output device and nothing left behind when you uninstall.

MixPill requires macOS 15 Sequoia or later, which includes Tahoe. We would rather state the shared risk plainly than pretend a two-year-old API is as settled as one from 2004 — the same caveat applies to every app in this category. If you want to see how the options differ elsewhere, there is a comparison.

Common questions