When something is wrong

No text at all, or only your own voice

This is almost always the system-audio permission. Open System Settings → Privacy & Security → Screen & System Audio Recording, switch Subtl on, and restart the app — macOS does not apply that one to a running process.

If your voice appears but the other side does not, check the output device on the start screen: Subtl listens to the device the call is actually playing through.

“The system audio stream dropped — capture restarted”

macOS occasionally drops the capture stream, usually when audio devices change — headphones connected, a call app switching device. Subtl restarts it by itself and the notice disappears after a few seconds. Nothing is lost except the moment it took to reconnect.

If it repeats every few minutes, it is usually a device that keeps re-announcing itself: a Bluetooth headset going in and out of range, or a virtual audio device from another program.

Text arrives late or in long blocks

Lines are cut at sentence ends, so a speaker who does not pause produces longer lines. If everything is late rather than long, the latency figure on the Live panel says where the time is going.

On local recognition, lag behind a fast speaker is expected on 8 GB machines; the cloud option is faster.

Minutes ran out mid-call

A warning appears before the limit and the session stops at it. Your call is not affected — Subtl is not in the audio path — and the transcript up to that point is kept.

Sending us something useful

Subtl writes a log to `~/Library/Logs/Subtl/subtl.log`. It contains what the app did and the errors it showed you; it does not contain the text of your calls. Attaching it to an email to hello@subtl.me turns a guess into a fix.