A macOS menu-bar app that routes individual apps' audio to different output devices — send Spotify/Music to your USB speakers while Slack, Zoom, and everything else stay on the built-in output or your AirPods. Built on Core Audio process taps (macOS 14.2+), no kernel extension or virtual driver required. Inspired by Rogue Amoeba SoundSource.
It also lets you hold a key and use the keyboard volume keys to control a specific output device — e.g. hold Right Option and the volume keys raise/lower your USB speakers instead of the system default.
- macOS 14.2 or later (Apple Silicon). Some features (pre-configuring routes for apps that aren't running yet) need macOS 26+.
- To build from source: Swift 6.3 toolchain (Xcode or Command Line Tools). Not needed if you install a release build.
- Download
audio-router-<version>.zipfrom the latest release. - Unzip and move
audio-router.appto/Applications, then open it. Builds are Developer ID–signed and notarized, so macOS opens them normally. - The app appears in the menu bar. A first-run setup guide walks you through the two permissions it needs:
- Screen & System Audio Recording — required to capture and re-route app audio. After granting, quit and reopen the app (macOS only applies this grant to a freshly launched process — the app offers a "Quit & Reopen" button).
- Accessibility (optional) — only needed for the hold-a-key volume hotkeys.
- Optional: Discord auto-pause (pause/duck your music when a second person joins your voice channel) — see docs/discord-setup.md.
The app checks GitHub daily for new releases and shows a banner in Settings when one is available.
# Build the proper app bundle (recommended — gives clean permission prompts)
swift run audio-router bundle
# Then launch it from Finder once so macOS attaches permissions to "audio-router":
open audio-router.app # or move it to /Applications firstThe app lives in the menu bar (🔊). Open the main window from the menu to:
- Routes — add an app, pick its output device (or a second one for multi-output), set its volume, mute, balance, 3-band EQ, record to CAF, and watch a live meter.
- Volume Hotkeys — bind modifiers to devices (default: Right Option → your non-built-in device). Hold the key and tap the keyboard volume keys to control that device. Release it and the keys work normally again.
- Permissions — grant the two permissions below.
- Screen & System Audio Recording — required to capture and re-route app audio. Prompted on first capture.
- Accessibility — required for the volume-key hotkeys (the app has to intercept the hardware volume keys, which needs a consuming event tap).
Grant both in System Settings → Privacy & Security. Launch the app from Finder (or /Applications), not from a terminal — otherwise macOS grants the permissions to your terminal app instead of audio-router.
First capture right after clicking "Allow" sometimes fails with OSStatus
1852797029('nope') — the grant isn't effective for the running process yet. The app retries automatically; if it persists, quit and relaunch once.
Running with any argument uses the CLI instead of the menu-bar app:
swift run audio-router devices # list output devices (UID + current hardware volume)
swift run audio-router processes # list apps currently producing audio
swift run audio-router meter --app Music
swift run audio-router route --app Music --to <device-uid> --volume 0.8
swift run audio-router permissions # explicitly request the capture permission
swift run audio-router bundle # build audio-router.approute accepts multiple --app/--to/--volume triples and drops into an interactive prompt (status, volume <app> <0-4>, add <app> <device> [vol], remove <app>, quit).
Each route is a single private Core Audio aggregate device that combines the app's process tap with your chosen output device, driven by one IOProc that re-renders the tapped audio (with gain) to the device. CATapMutedWhenTapped removes the app from the normal output path so there's no double audio. See CLAUDE.md for the full architecture and Sources/audio-router/Audio/RouteEngine.swift for the engine.
audio-router applies no EQ, compression, or effects, and at 100% volume the signal passes through untouched — the whole path is 32-bit float (higher precision than Spotify's 16/24-bit source), and unity gain is bit-transparent. The app does not degrade your audio on its own.
What it can't guarantee is strict bit-perfect lossless — but neither does normal macOS playback. A process tap captures audio after the system mixer, which runs at the current output device's sample rate, so:
- If that rate doesn't match the source (Spotify Lossless is 44.1 kHz), macOS resamples — with or without this app.
- Routing to a device running at a different rate can add one more (drift-compensated) resample.
To stay as close to the original as possible:
- Match sample rates — set your output device to 44.1 kHz in Audio MIDI Setup to match Spotify Lossless and minimize resampling.
- Keep routed volume at ≤ 100% — lowering it is clean digital attenuation; boosting above 100% can clip already-loud tracks.
For anything short of critical listening the difference is inaudible — you keep essentially full fidelity.
Audio routing can't be verified without real devices and granted permissions, so please sanity-check it on your Mac:
swift run audio-router devices— confirm your USB speakers / AirPods appear with the right UIDs and a sensible volume. (Works without any permission.)swift run audio-router processes— play something and confirm the app shows up.swift run audio-router bundle && open audio-router.app, grant both permissions, relaunch from Finder.- In Routes, add a playing app → your USB speakers at ~80%. Confirm: audio moves to those speakers, the meter moves, and other apps still play on the built-in output.
- Adjust the route's slider — volume should change live.
- In Volume Hotkeys, confirm Right Option → your speakers. Hold Right Option and press the keyboard volume keys — the HUD should show that device's level changing, and the system volume should not change. Release and confirm the keys control the system again.
- Quit from the menu and confirm audio returns to normal.
Notes / known limitations:
- Stereo→multichannel devices map to the front channels (no upmix).
- Bluetooth devices can renegotiate format on switch; if a route goes silent after switching devices, remove and re-add it.
- The
bundlecommand signs with your Developer ID if one is installed (ad-hoc otherwise). With a Developer ID, permission grants persist across rebuilds; with ad-hoc, you may need to re-grant after a rebuild. - After enabling Screen & System Audio Recording, quit and reopen the app — macOS only applies that grant to a freshly launched process (there's a "Quit & Reopen" button in the Permissions pane).
The new Listening Assistant adds device roles, intent-based profiles, local music/speech classification, microphone-use metadata for call detection, scoped suggestions, remembered output choices, and opt-in automatic matching. It starts disabled. See setup, behavior, and verification. Run audio-router assistant-preview for the isolated native UI or audio-router assistant-diagnose for read-only app activity metadata.
Audio classifiers and decision providers can be selected independently. Local d1, Joey, and Clef decision advice initially runs in shadow mode. See local provider setup and the completed local benchmark comparison. Apple + built-in rules remain the defaults.
For continuing development on another machine, start with the adaptive audio handoff.
The development Mac now runs the signed and notarized 1.2.0 production build, with existing settings preserved.
A Bluetooth-format watchdog (silent-renegotiation detection without a device-list change), smarter Discord occupancy counting (exclude AFK/self-deafened users), and Shortcuts discovery for the App Intents surface (blocked on SwiftPM's missing metadata extractor).