Hearing the other side of the call,without a bot joining it

Why there is no bot

Most meeting tools join your call as a participant, because that is the easy way to get both sides of the audio: the meeting platform hands it to them. Everyone on the call sees the bot arrive, and on plenty of calls that changes the conversation.

HuddleOwl takes the audio from your own machine instead. Your microphone is one track, and what your speakers are playing is the other. Nothing joins, nothing appears in the participant list, and it works identically on Zoom, Meet, Teams, Slack huddles, a phone on speaker, or a conversation in a room.

Attribution is a fact, not a guess

Because the two tracks are captured separately, who said what is decided by which device the audio came from rather than by a model comparing voices. The microphone is always you. The loopback is always the other side, which the app labels Guest during the call.

That is why the live transcript says Guest rather than a person's name: naming a voice mid-call would be a guess, and this part of the app does not guess.

macOS: three tiers, and which one you get

Tier 2, the native tap

On macOS 14.4 and later, HuddleOwl uses Apple's own process tap. No picker, no prompt, nothing to approve. If your Mac is current, this is what you are using and you will never see this page.

Tier 1, screen capture with audio

On macOS 13 and earlier 14 builds, system audio arrives through the screen-capture API. That needs Screen and System Audio Recording permission, because Apple puts the two behind one switch. HuddleOwl does not record your screen; it takes the audio track and stops the video track immediately.

Tier 0

Below macOS 13 there is no supported route, and the app says so rather than failing quietly. Your own microphone still works.

The failure worth knowing about

macOS has granted the permission and is not applying it. This is the one that wastes an afternoon. The checkbox in System Settings is ticked, and capture still fails, because the grant is bound to a running process and the app has been running since before it was granted.

The fix is to quit HuddleOwl completely, Cmd Q rather than closing the window, and open it again. HuddleOwl detects this state and says so in the error rather than telling you to grant a permission you have already granted.

A related trap: in a development build the permission belongs to the binary that is asking, which is Electron rather than HuddleOwl, so the row you need to tick may not have the name you expect. A packaged build from the download page asks as HuddleOwl.

Windows

Loopback audio, which needs no permission and no picker. It is on by default and there is nothing to configure.

Headphones, echo, and why it matters

On speakers, your microphone re-captures the other person's voice coming out of them, so the same sentence arrives twice: once correctly as Guest, and once as an echo labelled as you. HuddleOwl cancels this live and suppresses the duplicate, keeping the clean copy and hiding rather than deleting the other one, because a filter that is sometimes wrong must not be able to destroy the record.

Headphones still produce a better transcript, as they do for every tool of this kind.