How to record your microphone and your Mac’s system audio at the same time
Two devices in Audio MIDI Setup do two different jobs, and most tutorials describe one and then blame you when the recording comes out wrong. Here is the whole signal path, the caveats, and what the mixing costs your transcript.
- It takes two devices, not one. A Multi-Output Device makes your Mac play to your headphones and to a virtual device at once. An Aggregate Device combines that virtual device with your microphone so a recorder can see both.
- An aggregate device does not mix. BlackHole’s maintainer, answering a user whose aggregate had five channels: “You need to record all channels as an aggregate does not mix them.” GarageBand, in that thread, could take only two of the five.
- Apple’s own requirement: “All devices in the aggregate device need to have the same sample rate.” Drift correction is Apple’s word for resampling, “to compensate for drift in the data between devices”.
- macOS will not let you change the volume of a Multi-Output Device. BlackHole’s wiki: “Unfortunately macOS does not support changing the volume of a Multi-Output device”.
- A single mixed track cannot tell your voice from theirs. Narada records the microphone and the system output as two separate files, with echo cancellation on the mic track, and needs no virtual driver.
You need two devices in Audio MIDI Setup, not one: a Multi-Output Device so the sound your Mac plays goes to your headphones and to a virtual audio driver at the same time, and an Aggregate Device so a recorder can see that driver and your microphone as one input. Miss the first and you record the call but hear nothing; miss the second and you record one of the two sources and find out afterwards.
Or you skip the whole arrangement, which is the last section.
The signal path, written out
Read it in two hops.
Playback hop. Every app’s output → Multi-Output Device → your headphones + BlackHole (or Loopback, or whatever virtual device you installed).
Capture hop. BlackHole + your microphone → Aggregate Device → your recording app.
Apple describes each half in one sentence. For the Multi-Output Device: audio sent to the primary device “also plays through any other device in the stack.” For the aggregate: “When you create an Aggregate Device, multiple devices appear as a single device in an app.”
| Multi-Output Device | Aggregate Device | |
|---|---|---|
| Direction | Output | Input (and output) |
| What it’s for | Hearing the call while something else also receives it | Letting one app read two sources at once |
| Where you select it | System Settings → Sound → Output | Inside your recorder, as its input device |
| Mixes? | It duplicates the same signal to each member | No — it presents each member’s channels separately |
| Volume keys | Do not work | Not applicable |
Step 1 — build the Multi-Output Device
- Open Audio MIDI Setup (it’s in
/Applications/Utilities, or ⌘Space it). - Click + at the bottom of the sidebar → Create Multi-Output Device.
- Tick Use for your real output first — the built-in speakers or your headphones — and then for BlackHole. Order matters. BlackHole’s own wiki is blunt about why: “Due to issues with macOS the Built-in Output (sometimes called MacBook Pro Speakers or similar) or another 2 channel audio device must be enabled and listed as the top device / primary device / clock device in the Multi-Output.” If BlackHole ended up on top, untick and retick to reorder.
- Enable Drift Correction for every device except the clock source, which is the top one. That is the wiki’s recommendation and it matches Apple’s: drift correction is “also known as resampling, to compensate for drift in the data between devices.”
- Set your Mac’s sound output to this new device.
You will now hear audio normally and BlackHole will be receiving a copy. If you only wanted the call’s audio, you can stop here, point a recorder at BlackHole as its input, and you’re done — that’s the route in recording system audio on a Mac.
Step 2 — build the Aggregate Device
Your microphone is still not in the picture. BlackHole carries output, and your recorder can only choose one input, so the two have to be presented as a single device.
- In Audio MIDI Setup, click + → Create Aggregate Device.
- Tick Use for BlackHole and for your microphone. The order you tick decides the channel order your recorder sees.
- Set the Clock Source to your microphone — the physical device with the real crystal, not the virtual one.
- Enable Drift Correction on the other member.
- Check that both are at the same sample rate. Apple states this as a requirement rather than a suggestion: “All devices in the aggregate device need to have the same sample rate.”
- In your recorder, choose the Aggregate Device as the input.
That last check is where a lot of chipmunk recordings come from. BlackHole’s rate is whatever Audio MIDI Setup says it is, and a 2020 issue on the project reports it “doesn’t seem to set the sample rate based on the actual stream as requested by an application.” Mismatch the two members and the arithmetic of playback goes wrong — see why a Mac recording plays at the wrong speed.
The part the tutorials skip
You have an aggregate device with, say, five channels. Your recorder wants two.
An aggregate does not mix its members, and almost nothing written about this setup says so. BlackHole’s maintainer, answering a user trying exactly this combination of system audio plus a Yeti microphone: “You need to record all channels as an aggregate does not mix them,” and “Garage band only is able to record 2 channels. Your aggregate has 5.”
So a naive setup fails in one of two shapes, and both look like a bug:
- Only one source is in the file. A two-channel recorder grabbed channels 1–2, which belonged to whichever device you ticked first. Your voice or theirs, never both.
- One side is silent, or sits entirely in the left channel. The channels arrived, got interpreted as ordinary stereo, and the layout was never what your recorder assumed.
The fix is a recorder that takes every channel of the aggregate and mixes down deliberately — a DAW, Audacity with the right input configuration, Loopback’s own patchbay, OBS with per-source tracks. QuickTime is not that recorder. If your recording came out silent instead, the causes are enumerable and different: diagnosing a silent Mac recording.
What this arrangement costs you, honestly
The routing works. Living with it is the problem.
You lose keyboard volume control. Not a bug you can fix: “Unfortunately macOS does not support changing the volume of a Multi-Output device but you can set the volume of individual devices in Audio MIDI Setup.” Mid-call, that means opening a utility to turn someone down.
Two clocks drift. Drift correction resamples to compensate, which is why Apple ships the checkbox, and on a long recording the compensation is the difference between usable and slowly-sliding audio.
There is a ritual. Switch output before the call, switch back after. Forget the second half and your music plays through a device that no longer has a virtual sink attached, or your next Zoom call hears nothing.
The result is one track. Even done perfectly and mixed down properly, you end up with a single waveform containing several people. That matters less if you want the audio and more if you want a transcript, which is the next section.
Why two tracks beat one mixed track
Say you want notes rather than a recording. A mixed track gives a transcriber one stream of overlapping voices, and everything about attribution becomes inference: who spoke, where one person stops and the next begins, which lines were yours.
Two independent streams change the shape of the problem. Your microphone is, by definition, you — so those lines can be attributed with certainty rather than clustered and guessed at. The call’s audio is everyone else, and speaker separation runs on that track alone, where the voices are the ones that need separating.
This is how Narada records. It holds macOS’s System Audio Recording permission and reads the output stream where it already is, so there is no Multi-Output Device, no Aggregate Device, no driver to install and nothing to set back afterwards. The microphone and the system output are written as separate .m4a files and transcribed separately, on the Mac, using Parakeet TDT v3 through Core ML. Speaker labels on the call’s side are Speaker 1, Speaker 2 and so on — the model separates voices, it does not know names, and the app doesn’t pretend to. Your own lines carry your name only because your microphone was its own file.
Two limits worth knowing. Changing audio devices mid-recording — pulling out AirPods, plugging in a dock — ends one part and starts another, with a two-to-five-second gap at the seam; the parts present as one meeting, but the seam is real. And macOS audio can fail underneath any app. Narada checks each finished recording against what the capture actually submitted and marks it Incomplete, with a reason, when audio went missing. It cannot get that audio back. Nothing can. The useful part is being told, rather than finding out three weeks later that a 90-minute meeting is six minutes long.
The recorder half is free — capture, transcription, speaker separation, plain files on disk. Summaries and follow-ups are the paid part, or free on-device on an Apple Silicon Mac after a one-time model download of about 3 GB or 7 GB depending on your RAM. It needs macOS 15.6 or later.
Which route to take
| You want | Route |
|---|---|
| A one-off capture of a video’s audio plus your commentary | Multi-Output + Aggregate, and a recorder that takes all channels |
| Multi-source routing with per-app control, for editing | Loopback’s patchbay |
| Both sides of every call, transcribed, with your lines attributed | An app that opens mic and system output separately |
| Only the other side, no microphone | Multi-Output + BlackHole as your recorder’s input |
One thing no software settles for you: if the audio you are capturing contains another person, tell them. Rules differ by country and by state, and some places require everyone’s consent rather than only yours. Narada keeps a reminder on screen for the length of the recording, and that is the extent of what an app can do about it — it doesn’t notify anyone on your behalf and it can’t make a recording lawful.
Sources
- Apple Support, Combine audio devices into a single aggregate device in Audio MIDI Setup on Mac — the definition and the creation steps.
- Apple Support, Set aggregate device settings in Audio MIDI Setup on Mac — drift correction “also known as resampling"; the same-sample-rate requirement.
- Apple Support, Play audio through multiple devices at once in Audio MIDI Setup on Mac — the primary device and the stack.
- Apple Support, Create an Aggregate Device to combine multiple audio devices — “multiple devices appear as a single device in an app”.
- Apple Support, Record audio in QuickTime Player on Mac — the single input control, “Choose a microphone (if you have more than one available)" — https://support.apple.com/guide/quicktime-player/record-audio-qtp3a7cbdc0d/mac
- Apple Support, Take a screenshot or screen recording on Mac — “Below Microphone, select the microphone you want to use”, with no system-audio option — https://support.apple.com/guide/mac-help/take-a-screenshot-or-screen-recording-mh26782/mac
- BlackHole wiki, Multi Output Device — primary-device ordering, drift-correction advice, and the volume limitation.
- ExistentialAudio/BlackHole, Discussion #716 — https://github.com/ExistentialAudio/BlackHole/discussions/716 — “an aggregate does not mix them”; “You need to record all channels”.
- ExistentialAudio/BlackHole, Issue #41, Sample rate not set by application? (January 2020, closed) — https://github.com/ExistentialAudio/BlackHole/issues/41 — BlackHole’s sample rate not following the source stream.
- Existential Audio, BlackHole product page — free, donation-based, “Compatible with macOS Mavericks (10.10) and newer”, Intel and Apple Silicon.
Every one of these was fetched and checked on 4 August 2026.
Questions people ask about this
What is the difference between a Multi-Output Device and an Aggregate Device?
A Multi-Output Device is for playback — Apple’s documentation says audio sent to the primary device “also plays through any other device in the stack”, which is how you hear the call while a virtual device also receives it. An Aggregate Device is for capture: it combines several devices so that, in Apple’s words, “multiple devices appear as a single device in an app”. You need the first to keep hearing, the second to record your microphone alongside the call.
Why does my aggregate device recording only have one side of the call?
Because an aggregate hands the recorder a stack of channels and does not mix them. A recorder that only reads two channels takes the first two it finds, which is either your microphone or the virtual device, not both. Either use software that can record every channel of the aggregate, or use an app that opens the microphone and the system output independently.
Do I need BlackHole to record my mic and system audio together?
Only if your recorder cannot capture system audio itself. The virtual-driver route exists because most recorders can only read inputs, and macOS presents your Mac’s output to nothing by default. An app holding the System Audio Recording permission reads the output stream where it already is, so there is no Multi-Output Device, no Aggregate Device and nothing to set back afterwards.
Why is there an echo in my recording?
Because you recorded the call through your speakers and your microphone at the same time. The other side’s voice arrives once in the system track and again, a few milliseconds later and coloured by the room, in your mic track. Headphones remove the echo and reintroduce a different problem: nothing else in the room is captured. Narada runs echo cancellation on the mic track so the two copies do not fight.
Can I record my microphone and system audio as separate tracks?
Not with a Multi-Output Device — everything downstream of it is one stream. You need software that opens the two sources independently. Narada writes them as separate .m4a files and transcribes them separately, which is what lets it attribute your lines to you rather than guess.
Try it on your next call
Narada records your Mac's audio and your microphone, transcribes on-device, and hands you the decisions and follow-ups. Free to use, no account, no bot in the meeting.