Skip to content

docs(tts): document Kokoro English dictionary versus BART comparison - #1006

Merged
Alex-Wengg merged 1 commit into
mainfrom
docs/kokoro-english-g2p-comparison
Oct 9, 2026
Merged

Alex-Wengg merged 1 commit into
mainfrom
docs/kokoro-english-g2p-comparison

Conversation

@Alex-Wengg

Copy link
Copy Markdown
Member

Why is this change needed?

Kokoro callers need to understand why English pronunciation uses dictionary lookup before BART fallback, and why a nonempty fallback result is not evidence of a correct pronunciation. Add a bounded 40-word comparison with all outputs, CMU reference alternatives, source/model hashes and explicit limits on interpretation.

The note distinguishes the older dictionary-only probe from current main, whose initialism rules already protect uppercase API/CPU/GPU. It reports coverage and raw agreement rather than an unsupported accuracy rate, and does not attribute observed errors to conversion or to BART architectures generally. Link it from the documentation index and Kokoro guide; include the CMUdict attribution/license alongside the reference excerpts.

Validation: checked all 40 records, summary counts, source hashes and relative links; the analysis harness passed three tests for reference variants, missing entries and inference-failure accounting; git diff --check passed. Documentation and recorded data only; no new model runs or runtime changes in this PR.

@github-actions

github-actions Bot commented Oct 9, 2026

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 13.24x >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 16.743 21.1 Fetching diarization models
Model Compile 7.176 9.1 CoreML compilation
Audio Load 0.033 0.0 Loading audio file
Segmentation 21.437 27.0 VAD + speech detection
Embedding 79.033 99.7 Speaker embedding extraction
Clustering (VBx) 0.108 0.1 Hungarian algorithm + VBx clustering
Total 79.253 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 • 100.6s processing • Test runtime: 1m 50s • 10/09/2026, 12:00 AM EST

@github-actions

github-actions Bot commented Oct 9, 2026

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 20.2x >1.0x ✅
Speakers 4/4 - -

Sortformer High-Latency • ES2004a • Runtime: 2m 41s • 2026-10-09T04:01:32.181Z

@github-actions

github-actions Bot commented Oct 9, 2026

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 ✅ (368.5 KB)

Runtime: 0m21s

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

github-actions Bot commented Oct 9, 2026

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 27.59x >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.156 29.3 Fetching diarization models
Model Compile 4.781 12.6 CoreML compilation
Audio Load 0.034 0.1 Loading audio file
Segmentation 11.406 30.0 Detecting speech regions
Embedding 19.009 50.0 Extracting speaker voices
Clustering 7.604 20.0 Grouping same speakers
Total 38.035 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 • 38.0s diarization time • Test runtime: 3m 14s • 10/09/2026, 12:02 AM EST

@github-actions

github-actions Bot commented Oct 9, 2026

Copy link
Copy Markdown

PocketTTS Smoke Test ✅

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

Runtime: 0m18s

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.

@github-actions

github-actions Bot commented Oct 9, 2026

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% 498.5x faster 50
VOiCES 94.0% 89.3% 100.0% 94.3% 419.1x 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

github-actions Bot commented Oct 9, 2026

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 9.72x Real-time factor (higher = faster)
Total Audio 470.6s Total audio duration processed
Total Time 50.8s Total processing time

Streaming Metrics

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

Test runtime: 1m22s • 10/09/2026, 12:11 AM EST

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

@github-actions

github-actions Bot commented Oct 9, 2026

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.89x ✅
test-other 1.19% 0.00% 2.88x ✅

Parakeet v2 (English-optimized)

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

Streaming (v3)

Metric Value Description
WER 0.00% Word Error Rate in streaming mode
RTFx 0.50x Streaming real-time factor
Avg Chunk Time 1.772s Average time to process each chunk
Max Chunk Time 2.799s Maximum chunk processing time
First Token 2.351s 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.49x Streaming real-time factor
Avg Chunk Time 1.837s Average time to process each chunk
Max Chunk Time 3.167s Maximum chunk processing time
First Token 2.018s 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: 9m30s • 10/09/2026, 12:21 AM 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

@Alex-Wengg
Alex-Wengg enabled auto-merge (squash) October 9, 2026 21:01
@Alex-Wengg
Alex-Wengg merged commit fc8c3e4 into main Oct 9, 2026
13 checks passed
@Alex-Wengg
Alex-Wengg deleted the docs/kokoro-english-g2p-comparison branch October 9, 2026 22:15
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.

1 participant