Troubleshooting

If your problem isn’t covered here, see Report a problem at the bottom of this page.

---

Model download stalls or fails

The model download is the only network operation the free build makes. If it stalls or errors:

Check the obvious first:

• Confirm you have an internet connection.
• Pause any VPN or proxy; some intercept large binary downloads and drop the connection mid-transfer.
• Check that you have enough disk space. The app shows the total download size before you start; if space runs out partway through, the download fails silently on some platforms.

If the download bar stops moving:

1. Cancel the download from the progress screen.
2. Quit Minutist fully (don’t just close the window).
3. Reopen and click Download models again. The app resumes from where it left off where the server supports range requests; otherwise it restarts.

If it fails repeatedly:

The model files are also available as direct downloads from the GitHub releases page. Copy the files into the directory the app shows in Settings → Models and restart; the app skips the download when the files are already present.

Note

Model filenames and sizes change between releases. The app shows the exact expected filenames during download; the releases page lists the same names with checksums.

---

No audio, or the wrong microphone is recording

No audio at all:

1. Open Settings → Capture and confirm a microphone is selected.
2. Check that the system hasn’t muted that device, or routed it to a different app.
3. On macOS: go to System Settings → Privacy & Security → Microphone and confirm Minutist is listed and enabled.
4. On Windows: check Settings → Privacy → Microphone and also the Windows sound control panel input levels; a muted input shows no activity there either.
5. On Linux: Minutist uses PipeWire or PulseAudio (whichever is active). Open your system audio mixer and confirm the input is not muted and the correct device is the default source, or select it explicitly in Settings → Capture.

Recording with the wrong microphone:

Open Settings → Capture mid-session (or before the next meeting) and change the selected input device. The change takes effect on the next recording; you can’t switch mid-meeting.

System audio on Linux:

System-audio loopback is not available on Linux; Minutist records the selected microphone input only. On Windows, loopback appears as an option in Settings → Capture when the audio driver supports it.

Muffled or quiet mic on Windows (multi-microphone laptops):

On Windows, Minutist captures the microphone through the OS communications pipeline (WASAPI communications mode). This applies the OS beamforming, echo cancellation and noise suppression before Minutist receives the audio. If your laptop’s built-in microphone array sounds muffled or quiet in other apps but fine in Minutist (or vice versa), the difference is this pipeline. It is not configurable inside Minutist; adjust the system’s communications-device settings in the Windows sound control panel if needed.

---

A meeting is stuck on “processing”

After you stop a recording, the pipeline runs in order: transcription, then speaker labelling, then ready to summarise. Each step can take longer than expected on slower hardware, or if a large model is in use.

How to tell whether it’s genuinely stuck or still running:

Open Settings → Logs (or find the log file: Windows %APPDATA%\ai.minutist\logs\, macOS ~/Library/Logs/ai.minutist/, Linux ~/.local/share/ai.minutist/logs/). If lines are still appearing, the pipeline is still running; give it more time.

If it has genuinely stopped:

1. Note the meeting ID shown in the URL or meeting list (you will need it for the bug report).
2. Quit Minutist.
3. Reopen the app. Minutist resumes interrupted pipelines on startup. Check whether the meeting advances.
4. If it still doesn’t move after a few minutes, file a bug report; see Report a problem. Attach the log file; it contains the last error.

Note

Meetings whose duration was not recorded (for example, a recording that was interrupted) are capped at a 30-minute processing timeout rather than running indefinitely. A recording that fails to finalise returns to Idle instead of hanging. You should see stuck meetings less often than in earlier builds.

Caution

Do not delete the meeting while it is in a stuck state. The raw audio file is intact and the pipeline can retry from it. Deleting removes the audio.

---

Phone recording stops in the background (Android)

This is a battery-optimisation issue, not a Minutist bug; the OS suspends apps it considers idle. The phone companion is Android-only (iOS coming soon).

Disable battery optimisation for Minutist:

The exact path varies by manufacturer, but the general route is:

1. Open Settings → Battery (or Settings → Apps → Minutist → Battery).
2. Set battery usage to Unrestricted (Samsung: Unrestricted; stock Android: Unrestricted or Don’t optimise).
3. Start a new recording to confirm it keeps running with the screen off.

On some devices (Xiaomi/MIUI, OnePlus OxygenOS) there is an additional “autostart” permission separate from battery optimisation; enable that as well.

Note

The phone records audio only; no on-device ML runs there. The full pipeline (transcription, speaker labels, summary) runs on one of your own desktops after the phone hands the recording across over the encrypted sync channel.

---

Checking your build version

The window title shows the version and the git build stamp, for example Minutist 0.1.0 (a1b2c3d). When filing a bug report, include this string so the report names the exact build.

---

Playback from the transcript

On a saved, finished meeting you can click any transcript row to hear the original audio for that segment. If the play control is not showing, hover over the row. Playback is not available while a meeting is still recording or processing.

---

Report a problem

The most useful bug reports include the log file and a description of what you were doing when it went wrong.

Collect the log file:

Platform	Location
Windows	%APPDATA%\ai.minutist\logs\
macOS	~/Library/Logs/ai.minutist/
Linux	~/.local/share/ai.minutist/logs/ (or $XDG_DATA_HOME/ai.minutist/logs/)
Android	Export from Settings → Logs → Share in the app

Open a GitHub issue with the log attached:

Open an issue on GitHub.

Pre-fill the template:

• What you were doing (record, download, processing, etc.)
• Platform and OS version
• Whether this is the free build or connected tier
• The log file or the relevant lines from it

Please redact anything from the log you’d prefer not to share before attaching.