Skip to content

fix(vocab): make alignBaseWordsToUTF8Ranges iterative (#961) - #962

Merged
Alex-Wengg merged 1 commit into
mainfrom
fix/961-align-recursion
Sep 25, 2026
Merged

Alex-Wengg merged 1 commit into
mainfrom
fix/961-align-recursion

Conversation

@Alex-Wengg

Copy link
Copy Markdown
Member

Fixes #961.

alignBaseWordsToUTF8Ranges recursed once per base word and copied the path at each level, so ctcTokenEvaluateCandidates SIGBUSed inside Swift concurrency tasks at ~1–2k words (linear depth, quadratic memory, quadratic time).

Fix

  • Explicit-stack backtracking over one shared path (no recursion, no per-level copies)
  • Candidate starts limited to the delimiter run after the cursor, probed with anchored literal matches
  • Memoize (wordIndex, cursor) states that yielded no alignment
  • Uniqueness semantics unchanged (0 or ≥2 alignments → all nil)

Verification

  • Differential vs. old implementation: 0 mismatches over 200k randomized texts
  • 16k words in 7 ms, 50k in 21 ms inside a detached Task; old code SIGBUSes at 1k in the same harness
  • New test: 20k-word alignment in Task.detached, plus fail-closed on a truncated word list

🤖 Generated with Claude Code

The exact-alignment search recursed once per base word and passed
`ranges + [match]` down each level, so stack depth was linear and live
memory quadratic in transcript length. ctcTokenEvaluateCandidates
SIGBUSed inside Swift concurrency tasks at ~1-2k words (512 KB stacks),
and each level also scanned to the end of the text looking for a second
alignment, making time quadratic too.

Rewrite as explicit-stack backtracking over a single shared path:
- a word can only start inside the delimiter run after the cursor, so
  candidates per level are those positions, probed with an anchored
  literal match instead of an unbounded forward search
- (wordIndex, cursor) states that produced no complete alignment are
  memoized, bounding pathological delimiter-only words
- uniqueness semantics unchanged: 0 or >=2 alignments -> all nil

Differential check against the old recursive implementation: 0
mismatches over 200k randomized texts (quotes, C++, combining marks,
repeated words, delimiter-only tokens). 50k words align in 21 ms inside
a detached Task; the old code SIGBUSes at 1k in the same harness.
@github-actions

Copy link
Copy Markdown

Supertonic3 Smoke Test ✅

Check Result
Build ✅
Model download (incl. VectorEstimatorVariants/ int4 buckets) ✅
Model load ✅
Synthesis pipeline (--ve-variant int4) ✅
Output WAV ✅ (364.7 KB)

Runtime: 0m35s

Note: CI VMs lack a physical Neural Engine; the ANE-bucketed VectorEstimator falls back to CPU here. This validates download + variant resolution + synthesis, not ANE residency/perf.

@github-actions

Copy link
Copy Markdown

PocketTTS Smoke Test ✅

Check Result
Build ✅
Model download ✅
Model load ✅
Synthesis pipeline ✅
Output WAV ✅ (168.8 KB)

Runtime: 0m27s

Note: PocketTTS uses CoreML MLState (macOS 15) KV cache + Mimi streaming state. CI VM lacks physical GPU — audio quality and performance may differ from Apple Silicon.

@Alex-Wengg
Alex-Wengg merged commit b908638 into main Sep 25, 2026
13 checks passed
@Alex-Wengg
Alex-Wengg deleted the fix/961-align-recursion branch September 25, 2026 16:13
@github-actions

Copy link
Copy Markdown

Parakeet EOU Benchmark Results ✅

Status: Benchmark passed
Chunk Size: 320ms
Files Tested: 100/100

Performance Metrics

Metric Value Description
WER (Avg) 7.03% Average Word Error Rate
WER (Med) 4.17% Median Word Error Rate
RTFx 5.76x Real-time factor (higher = faster)
Total Audio 470.6s Total audio duration processed
Total Time 82.6s Total processing time

Streaming Metrics

Metric Value Description
Avg Chunk Time 0.083s Average chunk processing time
Max Chunk Time 0.165s Maximum chunk processing time
EOU Detections 0 Total End-of-Utterance detections

Test runtime: 2m30s • 09/25/2026, 12:14 PM EST

RTFx = Real-Time Factor (higher is better) • Processing includes: Model inference, audio preprocessing, state management, and file I/O

@github-actions

Copy link
Copy Markdown

Sortformer High-Latency Benchmark Results

ES2004a Performance (30.4s latency config)

Metric Value Target Status
DER 30.3% <35% ✅
Miss Rate 28.2% - -
False Alarm 0.9% - -
Speaker Error 1.2% - -
RTFx 14.6x >1.0x ✅
Speakers 4/4 - -

Sortformer High-Latency • ES2004a • Runtime: 3m 31s • 2026-09-25T16:15:31.778Z

@github-actions

Copy link
Copy Markdown

Offline VBx Pipeline Results

Speaker Diarization Performance (VBx Batch Mode)

Optimal clustering with Hungarian algorithm for maximum accuracy

Metric Value Target Status Description
DER 10.4% <20% ✅ Diarization Error Rate (lower is better)
RTFx 9.23x >1.0x ✅ Real-Time Factor (higher is faster)

Offline VBx Pipeline Timing Breakdown

Time spent in each stage of batch diarization

Stage Time (s) % Description
Model Download 23.220 20.4 Fetching diarization models
Model Compile 9.951 8.7 CoreML compilation
Audio Load 0.076 0.1 Loading audio file
Segmentation 29.157 25.6 VAD + speech detection
Embedding 113.431 99.7 Speaker embedding extraction
Clustering (VBx) 0.134 0.1 Hungarian algorithm + VBx clustering
Total 113.738 100 Full VBx pipeline

Speaker Diarization Research Comparison

Offline VBx achieves competitive accuracy with batch processing

Method DER Mode Description
FluidAudio (Offline) 10.4% VBx Batch On-device CoreML with optimal clustering
FluidAudio (Streaming) 17.7% Chunk-based First-occurrence speaker mapping
Research baseline 18-30% Various Standard dataset performance

Pipeline Details:

  • Mode: Offline VBx with Hungarian algorithm for optimal speaker-to-cluster assignment
  • Segmentation: VAD-based voice activity detection
  • Embeddings: WeSpeaker-compatible speaker embeddings
  • Clustering: PowerSet with VBx refinement
  • Accuracy: Higher than streaming due to optimal post-hoc mapping

🎯 Offline VBx Test • AMI Corpus ES2004a • 1049.0s meeting audio • 142.7s processing • Test runtime: 2m 37s • 09/25/2026, 12:15 PM EST

@github-actions

Copy link
Copy Markdown

Speaker Diarization Benchmark Results

Speaker Diarization Performance

Evaluating "who spoke when" detection accuracy

Metric Value Target Status Description
DER 15.1% <30% ✅ Diarization Error Rate (lower is better)
JER 24.9% <25% ✅ Jaccard Error Rate
RTFx 26.64x >1.0x ✅ Real-Time Factor (higher is faster)

Diarization Pipeline Timing Breakdown

Time spent in each stage of speaker diarization

Stage Time (s) % Description
Model Download 11.841 30.1 Fetching diarization models
Model Compile 5.075 12.9 CoreML compilation
Audio Load 0.054 0.1 Loading audio file
Segmentation 11.814 30.0 Detecting speech regions
Embedding 19.690 50.0 Extracting speaker voices
Clustering 7.876 20.0 Grouping same speakers
Total 39.397 100 Full pipeline

Speaker Diarization Research Comparison

Research baselines typically achieve 18-30% DER on standard datasets

Method DER Notes
FluidAudio 15.1% On-device CoreML
Research baseline 18-30% Standard dataset performance

Note: RTFx shown above is from GitHub Actions runner. On Apple Silicon with ANE:

  • M2 MacBook Air (2022): Runs at 150 RTFx real-time
  • Performance scales with Apple Neural Engine capabilities

🎯 Speaker Diarization Test • AMI Corpus ES2004a • 1049.0s meeting audio • 39.4s diarization time • Test runtime: 3m 0s • 09/25/2026, 12:22 PM EST

@github-actions

Copy link
Copy Markdown

VAD Benchmark Results

Performance Comparison

Dataset Accuracy Precision Recall F1-Score RTFx Files
MUSAN 94.0% 89.3% 100.0% 94.3% 427.3x faster 50
VOiCES 94.0% 89.3% 100.0% 94.3% 442.0x faster 50

Dataset Details

  • MUSAN: Music, Speech, and Noise dataset - standard VAD evaluation
  • VOiCES: Voices Obscured in Complex Environmental Settings - tests robustness in real-world conditions

✅: Average F1-Score above 70%

@github-actions

Copy link
Copy Markdown

ASR Benchmark Results ✅

Status: All benchmarks passed

Parakeet v3 (multilingual)

Dataset WER Avg WER Med RTFx Status
test-clean 0.57% 0.00% 3.98x ✅
test-other 1.19% 0.00% 2.35x ✅

Parakeet v2 (English-optimized)

Dataset WER Avg WER Med RTFx Status
test-clean 0.80% 0.00% 3.67x ✅
test-other 1.00% 0.00% 2.56x ✅

Streaming (v3)

Metric Value Description
WER 0.00% Word Error Rate in streaming mode
RTFx 0.44x Streaming real-time factor
Avg Chunk Time 2.070s Average time to process each chunk
Max Chunk Time 2.789s Maximum chunk processing time
First Token 2.496s Latency to first transcription token
Total Chunks 31 Number of chunks processed

Streaming (v2)

Metric Value Description
WER 0.00% Word Error Rate in streaming mode
RTFx 0.46x Streaming real-time factor
Avg Chunk Time 2.020s Average time to process each chunk
Max Chunk Time 2.351s Maximum chunk processing time
First Token 2.074s Latency to first transcription token
Total Chunks 31 Number of chunks processed

Streaming tests use 5 files with 0.5s chunks to simulate real-time audio streaming

25 files per dataset • Test runtime: 9m45s • 09/25/2026, 12:33 PM EST

RTFx = Real-Time Factor (higher is better) • Calculated as: Total audio duration ÷ Total processing time
Processing time includes: Model inference on Apple Neural Engine, audio preprocessing, state resets between files, token-to-text conversion, and file I/O
Example: RTFx of 2.0x means 10 seconds of audio processed in 5 seconds (2x faster than real-time)

Expected RTFx Performance on Physical M1 Hardware:

• M1 Mac: ~28x (clean), ~25x (other)
• CI shows ~0.5-3x due to virtualization limitations

Testing methodology follows HuggingFace Open ASR Leaderboard

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ctcTokenEvaluateCandidates crashes on transcripts over ~1,700 words: alignBaseWordsToUTF8Ranges recurses once per word and copies its path

1 participant