Does Your AI Notetaker Stop Recording When the Meeting Ends?

Why this is a problem for notetakers with no bot

A bot notetaker joins the call as a participant. When the host ends the meeting, the bot is removed along with everyone else, so the recording has a natural end. A notetaker that runs on your Mac has no seat in the call. It hears your microphone and your computer's audio, and nothing tells it the meeting is over. It has to infer that.

Getting the inference wrong fails in two directions. Stop too late and the recording keeps going after you hang up: the colleague who walks over, the phone call you take at your desk, the next conversation in the room, all transcribed into the notes of a meeting they had nothing to do with. Stop too early and a call that dropped for ten seconds, or a long stretch where one person presents, ends the record halfway through.

The late stop is the worse failure. It records people who never agreed to be recorded and puts their words into a summary that may later be shared.

The three signals a desktop notetaker can use

A notetaker on your Mac has three ways to tell that a meeting is over, and every botless tool combines them differently.

• The call app lets go of the microphone. Zoom, Teams or a browser tab running Google Meet holds the microphone while the call is live and releases it when you leave. macOS reports which apps are using audio input, so a notetaker can watch for that release.
• A long stretch passes with nothing to transcribe. If no words have come through for a while, the meeting is probably over or the recording was forgotten.
• The calendar says the meeting has ended. Useful for scheduled meetings, and no help for a call that was never on the calendar.

Each signal breaks in a predictable place

The microphone signal fails when the call app keeps the microphone open between calls, which some apps do when you go straight from one meeting into the next. The silence signal fails when people keep talking after the call, which is exactly the case you care about. The calendar signal fails when a meeting overruns, ends early, or was never scheduled.

So the useful question for any tool is which signal it trusts, what it does when that signal is missing, and whether it tells you before it stops.

What Granola and Wispr Flow document

Granola's documentation lists three automatic stops. It stops when it detects the call has ended, using the length of the transcript, whether you are still using the call software and, for calendar meetings, the scheduled end time. It stops when 15 minutes pass without new audio to transcribe. And it stops when you put the computer to sleep.

The same page is open about the gaps. For ad hoc calls with no calendar event, auto stop relies on the call app releasing the microphone, and if you keep talking after hanging up, the 15 minute timeout does not trigger and Granola may keep transcribing. It recommends clicking stop by hand, especially for ad hoc meetings. On macOS versions below 14.2, non admin users may not get the call ended signal at all.

It also names the back to back case. If you go straight from one call to another and the meeting app keeps the microphone active in between, Granola cannot tell that the first meeting ended, and both may be merged into a single transcript.

Wispr Flow's settings page shows a different design. Stop Notetaker when a call ends is on by default, and there is a maximum recording length that defaults to two hours, with choices of 30 minutes, one, two or three hours. A cap is a blunt and reliable backstop, since a forgotten recording cannot run all afternoon. The cost runs the other way: a three hour planning session on the default setting ends at the two hour mark unless someone changed it beforehand.

What Driffle does when a call ends

Driffle watches which app holds the microphone. The list covers Zoom, Microsoft Teams, FaceTime, WhatsApp, Slack huddles, Discord, Webex and the main browsers, because a browser on the microphone is how a Google Meet or Whereby call looks from outside. Only the call that was live when you started recording, or one that then ran for at least a minute, can stop it. A short voice note or a mic check in another app does not end an in person recording.

When that app lets go of the microphone, Driffle waits four seconds to make sure the release is real, then holds another eight seconds in case the call dropped and you are rejoining. Then it shows a notification, Meeting ended, Driffle will stop recording in 60 seconds, with a Keep recording button, and the same countdown appears in the note. If you rejoin during the countdown, it cancels and recording carries on. If you do nothing, it stops and writes your notes. The countdown runs from any screen, even with the Driffle window hidden.

The countdown exists because the late stop happened. An earlier build kept recording after a call ended and went on to transcribe whoever was talking in the room. The fix shipped in Driffle 1.0.22, and 1.0.24 made it work with meeting detection turned off in Settings.

The backstop for everything the microphone signal cannot see is time. If no speech has been transcribed for 15 minutes, Driffle stops and tells you: No speech was transcribed for 15 minutes, so Driffle stopped recording. Open Driffle to resume. Resume continues in the same meeting. The clock measures transcribed words, so a quiet stretch where one person presents and is still being transcribed does not trip it. There is no maximum length, so a long workshop is never cut at an arbitrary hour.

Where Driffle still needs you to press stop

Back to back calls in the same app. Driffle reads the same microphone signal Granola does, so if Zoom keeps the microphone open as you move straight into the next call, Driffle sees one long call and both meetings land in one note. Stop by hand between them.

In person meetings. There is no call app to release the microphone, so only the 15 minute rule applies, and it fires only once nobody near the Mac is talking. If the room keeps chatting after the meeting, Driffle keeps transcribing. Stop it when you stand up.

A call shorter than a minute that started after the recording began does not stop it, on purpose, so a stray voice note cannot end a real recording. There is no setting to turn the call ended stop off; Keep recording is the override for a single call. Driffle runs on Macs with Apple Silicon, and transcription runs in the cloud.

Five things to test before you rely on one

Do this once with a colleague who has agreed to be recorded.

• Hang up a call and keep talking. Does the tool stop, warn you, or keep transcribing the room?
• Drop off a call and rejoin within ten seconds. Do you get one note or two, and is anything missing?
• Go straight from one call into the next without closing the meeting app. Do you get two notes?
• Record a short in person chat, then walk away and talk to someone else. How long until it stops?
• Leave a recording running with nobody talking. When does it end, and does it tell you?

Read the last minute of every transcript

After each test, read the end of the transcript. You are looking for words that belong to a different conversation, because those are the lines that end up in a summary someone forwards. A tool that tells you before it stops, and lets you keep going, makes the end of a meeting something you see happen rather than something you discover later.

If you want a Mac notetaker with no bot that stops when the call does and warns you first, Driffle is at driffle.ai/download.