v0.6.0-beta18
One bug fix, but a big one: switching audio output mid-recording could quietly fill your disk.
What was happening
When your output device changes mid-meeting — AirPods connect, you unplug headphones — Minutiva has to rebuild its system-audio capture, and it writes the rest of the recording to a new fragment file alongside the first.
Rebuilding involves creating an audio device, and macOS reports that as a change to your output device. So finishing a rebuild announced a change, which started another rebuild, which announced another change. One real device switch could turn into hundreds of rebuilds, each leaving an empty fragment behind.
On a real library one recording had ended up with 175 fragments, 171 of them empty, holding about 945 MB. Normally these are merged back into one file and cleaned up when you stop the recording — but that recording had crashed before it stopped, so nothing ever tidied up.
What changed
Minutiva now checks whether your output device actually changed before rebuilding, instead of trusting the notification. A rebuild that announces itself is recognised for what it is and ignored. There’s also a one-second floor between rebuilds — a real device switch is someone unplugging something, and never happens faster than that.
And a rebuild that captures no audio now reuses its fragment instead of leaving an empty one behind, so even if something does cause repeated rebuilds, they stop piling up. Any stragglers are cleared when you stop the recording.
If you already have some
Fragments from past recordings are still on disk. Settings → Storage shows them — they appear as unfinished recordings — and clears them in one click.
Auto-update
Existing beta channel testers get this within 24 hours. Or trigger now: Minutiva Private → Check for Updates…