Skip to content

v0.30.9: Recording starts and recovery

Choose a tag to compare

@silverstein silverstein released this 21 Oct 20:56

Minutes 0.30.9 fixes recording controls and recovery: Meeting audio selections survive background refreshes, an empty WAV left after an interrupted capture can no longer block the next recording, and unusable source tracks no longer block transcription of a usable main WAV.

What changed

  • Background status refreshes no longer overwrite an in-progress Meeting audio selection. The selected route must be saved successfully before Start Recording enables; a failed save can be retried. #1200
  • Minutes reuses verified empty WAV headers left behind by an interrupted capture. Existing audio, files held by an active recording, and file-permission checks remain protected. #1196
  • If neither separately saved source track can be used but the main meeting WAV contains usable audio, Minutes transcribes that WAV. The finished result is marked degraded, with a warning that coverage of both sides cannot be verified. The original recording and source files remain available. #1200
  • The frontmatter guide now documents the actual saved-artifact statuses, processing warnings and which fields depend on summarization or speaker attribution. #1199

Who should care

Anyone whose Meeting audio selection resets or leaves Start Recording disabled, whose next recording is blocked after an interrupted capture, or whose meeting WAV will not process despite usable audio in the main recording.

CLI / MCP / desktop impact

The fixes are in the shared local engine used by desktop recording and CLI processing. No public CLI commands or MCP tools are added. Agent integrations benefit when they use the updated local engine. Live transcription and dictation behavior are unchanged.

Breaking changes or migration notes

No configuration or stored-meeting migration is required. Existing transcripts are not automatically rewritten. The mixed-WAV recovery warning is saved in recording health and in the finished artifact’s processing warnings.

In Meeting mode, select Microphone + system audio for a computer call or Microphone only for an in-person meeting in the Meeting audio dropdown. Start Recording stays disabled until you make that choice; Minutes saves it for future meetings.

Known issues

Recordings classified as no-speech keep that status and retain the recovery warning. Mixed audio cannot establish whether both sides were captured, and source labels are unavailable on that recovery path. This cannot recover audio that was never recorded. Minutes still prefers usable separate source tracks. A decoder or model failure after independent recognition starts remains an error; it is not replaced by a mixed-audio success. MOV files retain their existing source-recovery requirements to avoid the dual-track duration bug. Failed source-header repair remains an error.

An app running code from before v0.30.8 can still show its old shutdown crash once after installing an update. Reopen Minutes to run the fixed version. If an older app cannot stay open, reinstall the current version; reinstalling preserves meetings, settings and downloaded models. Windows desktop remains experimental and unsigned.

Thank you to @erikcw for the empty-header fix and @monsterlag for the documentation correction.

Install or update

After updating the desktop app, reopen Recall so its terminal uses the matching bundled CLI.

  • macOS desktop: download the DMG below, or run brew update followed by brew upgrade --cask silverstein/tap/minutes.
  • Command line: cargo install minutes-cli --version 0.30.9, or brew upgrade silverstein/tap/minutes for an existing Homebrew install.
  • MCP server: npx minutes-mcp@0.30.9 with the updated local Minutes engine, or install the updated desktop extension below.

Minutes remains free and open source. Meeting capture and transcription run locally. Optional cloud AI and connected assistants receive the content you authorize under their settings; file sync and backups you configure are separate.