Candidate models
Candidate model evaluation
Tail-word retention
The release suite records production v3 on synthetic short-clip cuts with 80 ms and 400 ms capture-grace bounds. This is a report-only diagnostic, not a quality pass or a simulation of live RMS end-of-speech detection. The separate Unified padding gate remains opt-in candidate evidence.
Private corpus
For candidate-model decisions, maintainers can run Unified, the linear-int8 v3 encoder, and current Nemotron candidates over private real-dictation clips. Reports keep transcript text and filenames redacted by default while showing WER, final-word failures, and latency.
Release gate
run-release-asr-checks.sh requires private real-dictation clips, five hand-audited non-speech controls with no text in any measured trial, the benchmark and app to pin the exact same FluidAudio revision, and validated English and German multi-window corpora. It gates production v3 long-form results with conservative corpus WER and consecutive-deletion limits; private short-dictation WER remains for maintainer review, not an absolute pass threshold. It also reports a same-pin production-v3 versus explicit no-mel comparison as candidate-only evidence. That comparison does not change runtime selection or the release verdict. An explicit candidate-dependency mode can compare unreleased APIs, but cannot produce a production release-pass verdict.
Private dictation fixtures stay on the evaluator's computer; a lightweight run may explicitly omit them but cannot report a production release pass. This matters because public read-speech quality does not establish spontaneous-dictation quality: a multilingual conversational-speech study found substantial performance drops relative to standard read-speech benchmarks (Maheshwari et al., 2024).
The public-fixture fetcher can also import a deterministic row range from a pinned Google FLEURS language split. This gives encoder candidates reproducible multilingual and cross-script coverage; private human dictation is required separately for the release gate.
Language coverage is not a quality guarantee. NVIDIA lists 25 supported languages, but benchmark accuracy varies by language and speech variant. In FluidAudio's published Parakeet TDT v3 CoreML FLEURS results (24 evaluated languages, M4 Pro), WER ranges from 4.0% for Italian to 36.9% for Greek; Danish is 20.2% and Slovenian 27.4%. These are upstream results, not Presspeech measurements, and the read-speech-focused corpus, sample counts, runtime and hardware do not establish accuracy for short, spontaneous dictation. NVIDIA also notes that its European Portuguese training data differs from Brazilian Portuguese used in most evaluation benchmarks. Presspeech's result table above is English-only; use reproducible per-language fixtures and human dictation before making multilingual quality claims. Sources: FluidAudio FLEURS benchmark and the NVIDIA model card and evaluation notes.
A recent upstream report on conversational Latin-American Spanish was corrected by its author: the mixed Spanish/English output was not translation or a CoreML-only defect; the same model behaved worse in a full-precision upstream run. The author attributed it to Parakeet v3's behavior on spontaneous speech and English prior, and the issue was closed as not planned. This is a single upstream report on FluidAudio v0.15.5, not a Presspeech reproduction or evidence about the current v0.15.6 pin. NVIDIA's model card describes automatic language detection; Presspeech's selected language is documented in code as a decoder script-filter hint, not a language-forcing mechanism. To characterize this risk, use the same-input Spanish probe on the production pin, and keep its FLEURS read-speech result distinct from local spontaneous dictation. Both remain evaluation evidence, not a quality claim or release pass.
Evidence scope: the public comparison below ran on FluidAudio v0.15.5 (19600a4). The app pins v0.15.6 (4dbf4f9), so the table supports retaining Parakeet v3 over the tested Nemotron candidates; it does not validate the app's pinned inference-library revision for release.
Broader evidence also argues against extrapolating from this clean read-speech sample: NVIDIA's model card reports 1.93% WER on LibriSpeech test-clean, versus 11.31% on AMI and 11.42% on Earnings-22 (different corpora, not a Presspeech head-to-head). ASR evaluation research likewise finds multi-benchmark averages more informative about noisy real-world performance than a single corpus. Keep multi-window and human-dictation checks in the product gate; these outside results do not establish a Presspeech quality score.
Upstream FluidAudio v0.15.7 changed Parakeet v3's default long-form chunking policy and added final-window re-decode/seam fixes; v0.15.8 added fresh per-window decoder state, blank-window recovery, and text-based seam reconciliation (v0.15.7 notes, v0.15.8 notes). As checked on 2026-09-24, upstream's latest release is v0.17.1 (release notes), a CocoaPods podspec metadata fix with no Swift Package Manager code change from v0.17.0. That code includes an ASR optimization that bulk-resets and copies MLMultiArray storage. The upstream PR reports warm median inference on an 11-second clip falling from 71.1 ms to 48.3 ms with identical transcripts, on an M3 Pro and its Parakeet v3 Orukeet bundle (PR #941 and measurements). This is a candidate signal, not a Presspeech result: the app still pins v0.15.6 and has no same-input v0.17.0 quality or latency measurement. A separate German long-form report on v0.15.5 exposed token-order corruption with mel-context chunking; upstream PR #830 fixed that specific merge-order defect, and the v0.15.6 release notes show it is already in Presspeech's current pin. The PR notes that first-chunk mel-context degradation is separate, so the fix does not establish that all multilingual seams are safe. Presspeech still explicitly uses its reviewed mel-context policy.
A separate upstream Ukrainian right-context repro isolated deterministic single-window word corruption to the shipped v3 CoreML encoder's 6-bit-LUT weights. FluidAudio's opt-in linear-int8 Encoder_v2 decoded all three reported cuts correctly in its controlled swap, but is larger (568 MB vs 425 MB) and still needs broad WER and Apple Neural Engine latency evaluation. Presspeech pins the original encoder today; its benchmark has a candidate-only comparison path, but no Presspeech result establishes a quality or latency gain. Evaluate the same Ukrainian FLEURS fixtures and human-reviewed local dictation, plus cache/memory and ANE latency, before considering promotion. This upstream case motivates testing; it is not a Presspeech reproduction or evidence to change production.
The required Presspeech multi-window release corpus is English LibriSpeech with an English hint; it cannot validate the German failure class or upstream fix. The benchmark guide documents a pinned FLEURS German long-form probe. For an SDK update, save v0.15.6 baselines on both the required English corpus and the same composed German corpus, then compare v0.17.0 using run-release-asr-checks.sh --sdk-upgrade-only --allow-candidate-dependency, moving only the benchmark pin. Compare explicit production-config v3 against those baselines; the candidate SDK-default/no-mel path is also evaluated on German with an explicit de hint, alongside its English long-form and private/public checks. Match fixture digests, trial counts, and hints. Upstream speed figures and fixes motivate evaluation but do not establish a Presspeech quality or latency gain; candidate results are not a production release pass.
On 25 LibriSpeech dev-clean clips, repaired Nemotron English and Nemotron 3.5 multilingual both stayed behind Parakeet TDT v3. Multilingual is much faster than the older English path, but its accuracy and final-word retention are worse, so v3 remains the production model.