Taperlark / Submix

Submix notes.

macOS ships with exactly one volume control that matters system wide, and it moves every app's audio at once. Turning down a notification sound also turns down the call you are on, muting a browser tab means digging through that browser's own settings if it has any, and routing one app's audio to a different output device usually means changing the whole system's output first. For anyone running more than a couple of audio sources at once, that single slider is a constant source of small, avoidable interruptions.

Submix gives every running app its own volume, mute, and output routing, so a notification does not have to compete with a meeting and a game does not have to share an output device with the calendar reminders. These notes track how that per-app audio graph is built on top of Apple's own audio session model, the tradeoffs behind specific controls, and what changes as new macOS releases adjust how apps are allowed to expose their audio streams.

How Submix actually controls one app's volume at a time

Submix gives every running app its own volume, mute, and live meter through a Core Audio process tap, with no driver and no admin password. Here is the mechanism behind the mixer, what it does not do yet, and who it will not fit.

All Taperlark notes