Speakr is a personal, self-hosted web application designed for transcribing audio recordings
Python
docs: document filename date parsing, export filename templates, cache self-healing, chat truncation, and mic detection changes; bump version to 0.10.3-alpha
Murtaza Nasir25d8a2821654
diff --git a/README.md b/README.mdindex 118c7958..70eb2f38 100644--- a/README.md+++ b/README.md@@ -9,7 +9,7 @@<a href="https://www.gnu.org/licenses/agpl-3.0"><img alt="AGPL v3" src="https://img.shields.io/badge/License-AGPL_v3-blue.svg"></a><a href="https://github.com/murtaza-nasir/speakr/actions/workflows/docker-publish.yml"><img alt="Docker Build" src="https://github.com/murtaza-nasir/speakr/actions/workflows/docker-publish.yml/badge.svg"></a><a href="https://hub.docker.com/r/learnedmachine/speakr"><img alt="Docker Pulls" src="https://img.shields.io/docker/pulls/learnedmachine/speakr"></a>- <a href="https://github.com/murtaza-nasir/speakr/releases/latest"><img alt="Latest Version" src="https://img.shields.io/badge/version-0.10.2--alpha-brightgreen.svg"></a>+ <a href="https://github.com/murtaza-nasir/speakr/releases/latest"><img alt="Latest Version" src="https://img.shields.io/badge/version-0.10.3--alpha-brightgreen.svg"></a></p><p align="center">@@ -210,7 +210,11 @@ Complete documentation is available at **[murtaza-nasir.github.io/speakr](https:- [Troubleshooting](https://murtaza-nasir.github.io/speakr/troubleshooting) - Common issues and solutions- [FAQ](https://murtaza-nasir.github.io/speakr/faq) - Frequently asked questions-## Latest Release (v0.10.2-alpha)+## Latest Release (v0.10.3-alpha)++**A features and fixes release shaped by community reports and contributions.** Meeting dates can now be parsed from filenames on upload, with preset patterns and an optional custom expression, which saves manual edits on batch uploads of older recordings. Auto-export filenames are configurable through a template, and existing exports can be renamed to a new scheme in one pass. Mobile recording gains an external microphone selector for USB and wireless receivers, and a new webhook endpoint accepts uploads directly from the ASR Voice Recorder Android app, both community contributions. The transcription language dropdown now offers the full Whisper language set. On the fixes side, chat responses that hit the output token limit are now flagged instead of being presented as complete, a database-lock failure when editing speakers with Inquire mode enabled is resolved, browser caches self-heal after image upgrades so stale interfaces no longer appear, audio files with non-UTF-8 metadata no longer crash processing, and embedding provider compatibility is improved. Database columns migrate automatically; no configuration changes are required. **Full release notes on the [GitHub release page](https://github.com/murtaza-nasir/speakr/releases/tag/v0.10.3-alpha).**++### v0.10.2-alpha (previous release)**A security and dependency release. Upgrading is recommended for all deployments.** This release resolves three coordinated security reports: a stored cross-site scripting issue reachable by a group administrator through a tag color or name, a webhook server-side request forgery via DNS rebinding, and an SSO account-takeover path through an unverified email claim. Verified-email enforcement for SSO is now on by default; deployments whose identity provider does not send an `email_verified` claim must set `SSO_REQUIRE_VERIFIED_EMAIL=false`. The web framework moves to the Flask 3.1 and Werkzeug 3.1 line, which also closes two Werkzeug multipart denial-of-service issues. New features include contextual speaker labelling for transcription engines that diarize without voice embeddings, and pause/resume for in-app recording. This release also fixes malformed browser recording uploads, restores the API documentation page under the default Content-Security-Policy, and improves transcription-failure error messages. A one-time migration lowercases existing stored email addresses. **Full release notes on the [GitHub release page](https://github.com/murtaza-nasir/speakr/releases/tag/v0.10.2-alpha).**diff --git a/VERSION b/VERSIONindex c2ef6ba3..8ab8b060 100644--- a/VERSION+++ b/VERSION@@ -1 +1 @@-v0.10.2-alpha+v0.10.3-alphadiff --git a/docs/troubleshooting.md b/docs/troubleshooting.mdindex 5b391e13..9991755e 100644--- a/docs/troubleshooting.md+++ b/docs/troubleshooting.md@@ -137,8 +137,18 @@ Browser performance degrades with very large transcriptions. Recordings over 2 hClear your browser cache if the interface gradually becomes slower over time. Speakr caches data locally for performance, but this cache can become corrupted. In Chrome or Firefox, hard refresh with Ctrl+Shift+R to reload fresh assets.+### Blank Screens or Missing Text After Upgrading++If the interface shows blank panels or raw translation keys (console messages like `Translation not found for key: ...`) right after upgrading the Docker image, your browser is serving cached assets from the previous version against the new pages. Clear the site data for your Speakr domain (in Chrome: DevTools → Application → Storage → Clear site data), or unregister the service worker and hard refresh.++From v0.10.3-alpha onward this heals itself: each release installs a service worker with its own cache namespace, static assets are revalidated on load, and translation files are always fetched fresh, so an image upgrade can no longer strand a stale app shell. Upgrades from versions before v0.10.3-alpha may still need the one-time manual clear described above.+## Feature-Specific Issues+### Chat Responses End Mid-Sentence++If a chat or Inquire response stops abruptly with a note that the output token limit was reached, the model hit the configured `CHAT_MAX_TOKENS` ceiling (default 2000). This is common with reasoning models, whose hidden reasoning tokens share the same budget as the visible answer. Ask the model to continue from where it stopped, or raise `CHAT_MAX_TOKENS` in your `.env`. Before v0.10.3-alpha these truncated responses were displayed as if they had completed normally; they are now flagged explicitly.+### Speaker Identification Not Working[Speaker diarization](features.md#speaker-diarization) requires the [ASR endpoint](getting-started.md#option-b-custom-asr-endpoint-configuration), not standard Whisper API. Configure speaker settings in [system settings](admin-guide/system-settings.md). Verify you've configured ASR settings correctly in your environment file. The ASR_BASE_URL should point to a valid ASR service that supports diarization.diff --git a/docs/user-guide/recording.md b/docs/user-guide/recording.mdindex b41e20a8..773f0661 100644--- a/docs/user-guide/recording.md+++ b/docs/user-guide/recording.md@@ -136,7 +136,7 @@ Under the recording buttons is a collapsible **Input devices** section. ExpandedOpening **New Recording** does not request microphone permission. Device labels are normally blank until permission is granted. You can expand the picker and click **Request microphone permission**, or simply press **Microphone** and respond to the browser's normal permission prompt.-On mobile, after permission is granted, Speakr checks the labeled inputs. If a likely separate physical microphone is available and you have not already selected one, the existing **Input devices** section expands with an **Another microphone is available** notice before recording starts. Choose the input and continue, or keep the system default. When only the built-in/default microphone is present, recording starts immediately with no extra Speakr prompt. Because browsers do not reliably expose connection type, the detection covers likely USB receivers, wireless/headset microphones, webcams, and audio interfaces rather than claiming that a device is definitely USB.+On mobile, after permission is granted, Speakr checks the labeled inputs. If a likely separate physical microphone is available and you have not already selected one, the existing **Input devices** section expands with an **Another microphone is available** notice before recording starts. Choose the input and continue, or keep the system default. When only the built-in/default microphone is present, recording starts immediately with no extra Speakr prompt. Detection is deliberately conservative: it only triggers on devices whose labels clearly indicate an external input (USB receivers, wireless and headset microphones, webcams, audio interfaces), so a device the browser exposes without a recognisable label starts no prompt — you can still select it manually from the picker. The prompt also never appears when a recording is being resumed after an interruption; a continued session always keeps its original input.diff --git a/docs/user-guide/settings.md b/docs/user-guide/settings.mdindex 2f28e358..e300b7aa 100644--- a/docs/user-guide/settings.md+++ b/docs/user-guide/settings.md@@ -110,6 +110,14 @@ Three language settings shape your Speakr experience. The interface language droThese settings used to live on the Account Information tab. They moved here so all preferences that affect your day-to-day Speakr experience live in one place.+### Meeting Date from Filename++Voice recorders and phone apps commonly encode the recording date in the filename (`20260716_meeting.mp3`, `260716_1102.m4a`). When **Parse meeting date from filename** is enabled, Speakr extracts that date at upload time and uses it as the recording's meeting date, taking precedence over the file's timestamps and embedded metadata. This is especially useful for batch uploads of older recordings, where the meeting date would otherwise default to the upload time.++The **Filename date format** dropdown offers preset patterns — `YYYYMMDD`, `YYYYMMDD_HHMM`, `YYYY-MM-DD`, `YYMMDD_HHMM`, `YYMMDD` — plus an **Auto** mode that tries the common formats, and a **Custom pattern** option that accepts a regular expression with named groups (`(?P<year>...)`, `(?P<month>...)`, `(?P<day>...)`; `hour` and `minute` are optional). Auto mode deliberately skips the bare six-digit `YYMMDD` form, since any six digits in a filename would qualify; select that preset explicitly if your recorder uses it.++The setting is off by default. A file whose name contains no matching date keeps the existing behaviour (file timestamps, then upload time) without failing the upload, and the parsed date remains editable afterwards from the recording's details. Dates parsed from filenames are wall-clock times: browser uploads send your timezone so the stored date displays correctly everywhere, and date-only matches are anchored so the calendar date never shifts between viewers. The setting also applies to files dropped into the automated processing folder.+### Transcript Display**Show timestamps in simple view.** When enabled, a compact `mm:ss` (or `h:mm:ss` for long recordings) timestamp appears next to each speaker label in the simple transcript view, making it easier to navigate long meetings. The bubble view is unaffected. Off by default to keep the existing aesthetic for users who prefer a clean read.diff --git a/docs/user-guide/transcript-templates.md b/docs/user-guide/transcript-templates.mdindex 45880540..2c046fb4 100644--- a/docs/user-guide/transcript-templates.md+++ b/docs/user-guide/transcript-templates.md@@ -266,6 +266,14 @@ Create a default transcript template in your Speakr settings that formats the waFiles are organized into subdirectories by username, so multiple users can export to the same vault without conflicts. Obsidian picks up these markdown files automatically, and you can reference them in daily notes, link them to related content, and search across all your transcripts.+#### Export Filenames++By default, exported files are named `recording_<id>.md`. You can change this with the **export filename template** in your account settings (visible when auto-export is enabled). The template uses the same variable syntax as naming templates: `{{id}}`, `{{title}}`, `{{filename}}` (the original upload's name without extension), and date variables from the meeting date — `{{date}}`, `{{datetime}}`, `{{time}}`, `{{year}}`, `{{month}}`, `{{day}}`. For example, `{{date}} {{title}}` produces `2026-07-16 Team Standup.md`, and `{{filename}}` names the export after the uploaded audio file.++Rendered names are sanitized for filesystem safety (unicode titles are preserved; characters illegal on common filesystems are stripped), and if two recordings would render to the same name, the recording's id is appended to keep them unique. Each recording remembers the filename it was exported under, so re-exports overwrite the same file and deleting a recording renames its export with the `[deleted]_` prefix regardless of which template was active at the time.++Changing the template affects new exports only — files already exported keep their names. A **Rename existing exports** button next to the setting re-renders every existing export under the current template and renames the files on disk in one pass, so your whole vault can be migrated to a new scheme at once. Leaving the template empty returns to the default `recording_<id>` naming.+### Automated Processing WorkflowsMount Speakr's upload directory as a Docker volume pointing to a location your automation tools can access. Create a template that exports in a structured format (like JSON or CSV), then use scripts to process the files automatically.