fix(cli/tts): native-level WAVs for KokoroAne in tts-asr-verify + tts-benchmark - #870
Conversation
…-benchmark Follow-up to #868, which moved KokoroAne output to the model's native level but missed two CLI artifact writers that still used the AudioWAV default (peak-normalize to 0 dBFS): - TTSAsrVerifyCommand (KokoroAne-only): persisted --audio-dir WAVs now write at native level, matching the shipping path. - TtsBenchmarkCommand: the shared phrase loop gains an explicit per-backend normalizeWavs policy — kokoro-ane writes native level; pocket-tts / styletts2 / supertonic3 keep peak normalization to match their shipping output paths. ASR scoring is level-invariant, so WER/CER numbers are unaffected; only the persisted artifact levels change.
Supertonic3 Smoke Test ✅
Runtime: 0m34s 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. |
PocketTTS Smoke Test ✅
Runtime: 0m28s 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. |
Parakeet EOU Benchmark Results ✅Status: Benchmark passed Performance Metrics
Streaming Metrics
Test runtime: 2m20s • 08/19/2026, 12:16 PM EST RTFx = Real-Time Factor (higher is better) • Processing includes: Model inference, audio preprocessing, state management, and file I/O |
Offline VBx Pipeline ResultsSpeaker Diarization Performance (VBx Batch Mode)Optimal clustering with Hungarian algorithm for maximum accuracy
Offline VBx Pipeline Timing BreakdownTime spent in each stage of batch diarization
Speaker Diarization Research ComparisonOffline VBx achieves competitive accuracy with batch processing
Pipeline Details:
🎯 Offline VBx Test • AMI Corpus ES2004a • 1049.0s meeting audio • 138.3s processing • Test runtime: 2m 26s • 08/19/2026, 12:16 PM EST |
Speaker Diarization Benchmark ResultsSpeaker Diarization PerformanceEvaluating "who spoke when" detection accuracy
Diarization Pipeline Timing BreakdownTime spent in each stage of speaker diarization
Speaker Diarization Research ComparisonResearch baselines typically achieve 18-30% DER on standard datasets
Note: RTFx shown above is from GitHub Actions runner. On Apple Silicon with ANE:
🎯 Speaker Diarization Test • AMI Corpus ES2004a • 1049.0s meeting audio • 62.3s diarization time • Test runtime: 3m 38s • 08/19/2026, 12:17 PM EST |
VAD Benchmark ResultsPerformance Comparison
Dataset Details
✅: Average F1-Score above 70% |
Sortformer High-Latency Benchmark ResultsES2004a Performance (30.4s latency config)
Sortformer High-Latency • ES2004a • Runtime: 3m 29s • 2026-08-19T16:27:07.682Z |
ASR Benchmark Results ✅Status: All benchmarks passed Parakeet v3 (multilingual)
Parakeet v2 (English-optimized)
Streaming (v3)
Streaming (v2)
Streaming tests use 5 files with 0.5s chunks to simulate real-time audio streaming 25 files per dataset • Test runtime: 16m12s • 08/19/2026, 12:36 PM EST RTFx = Real-Time Factor (higher is better) • Calculated as: Total audio duration ÷ Total processing time Expected RTFx Performance on Physical M1 Hardware:• M1 Mac: ~28x (clean), ~25x (other) Testing methodology follows HuggingFace Open ASR Leaderboard |
Follow-up to #868 (issue #852): two CLI artifact writers still peak-normalized KokoroAne output to 0 dBFS via the
AudioWAV.datadefault, contradicting the native-level behavior #868 shipped.TTSAsrVerifyCommand(KokoroAne-only): persisted--audio-dirWAVs now write at native level vianormalize: false.TtsBenchmarkCommand: the shared phrase loop takes an explicitnormalizeWavsper-backend policy —kokoro-anewrites native level;pocket-tts/styletts2/supertonic3keep peak normalization, matching each backend's own shipping output path.ASR scoring is level-invariant, so benchmark WER/CER numbers are unaffected; only the persisted WAV levels change.
swift build+swift format lintclean.🤖 Generated with Claude Code