Skip to content

feat(tts/supertonic3): v2 CoreML bundles fix padding leak at chunk ends - #1002

Merged
Alex-Wengg merged 1 commit into
mainfrom
feat/supertonic3-v2-edge-pad
Oct 8, 2026
Merged

Alex-Wengg merged 1 commit into
mainfrom
feat/supertonic3-v2-edge-pad

Conversation

@Alex-Wengg

Copy link
Copy Markdown
Member

The Supertonic-3 text encoder, duration predictor and vector estimator use ConvNeXt convs that pad both sides with edge (replicate) padding upstream. We right-pad text to T=128 and, on the default ANE path, the latent to the 128/256/512 bucket. The conv at the last valid frame therefore read padded zeros instead of a copy of the last frame. That left audible energy in the last ~250 ms of most chunks, plus small duration and text-embedding drift.

Fix

  • New _v2 bundles fill padded frames with the last valid frame before each two-sided conv. Unpadded inputs give identical results, and inputs, outputs, sizes and ANE placement are unchanged.
  • The bundles are already published next to v1 in FluidInference/supertonic-3-coreml (commit 1b540236), so older releases keep working.
  • ModelNames.Supertonic3 now points at the TextEncoder_v2, DurationPredictor_v2 and VectorEstimator_v2* bundles. The Vocoder's convs only look backward, so it is unchanged.

Results (M5 Pro, macOS 27, compared against unpadded ONNX)

v1 v2
Spectral SNR, ANE L128 1.0 dB (int4) 25.4 dB (fp16) / 19.8 dB (int8)
Last-250 ms tail energy median −47 dB, worst −5.5 dB (56/80 files audible) −77 to −79 dB (ONNX: −79)
VectorEstimator, 8 steps ~35 ms ~35 ms
WER (80 utterances) ~1% ~1%

In an end-to-end CLI run on an 8-chunk paragraph, chunk tails went from −109…−21 dB (v1) to −109…−81 dB (v2), with 0% WER for both.

Notes

  • On macOS 27, the dynamic dyn-int8 and dyn-int6 builds return garbage on .cpuAndGPU for v1 and v2 alike. That's a pre-existing OS issue, not addressed here.
  • XCTest isn't available locally, so the updated naming tests run in CI only.

🤖 Generated with Claude Code

Upstream's ConvNeXt depthwise convs in text_encoder, duration_predictor and
vector_estimator pad both sides with ONNX `Pad mode=edge` on the unpadded
sequence. The CoreML pipeline right-pads text to T=128 and, on the default ANE
path, the latent to the L=128/256/512 bucket, so the v1 conv at the last valid
frame read masked zeros instead of a replicated frame.

Pure-ONNX FP32 repro of the leak: duration -1%, text_emb max |d| 0.22-0.34,
VE 8-step latent RMSE 0.08-0.26 on a ~0.3 rms signal, concentrated in the last
frames of each chunk.

v2 fills padded frames with the last valid frame before each symmetric conv
(x*m + (1-m)*x_last; identical when nothing is padded). Same I/O, sizes and
ANE placement; the causal vocoder is unchanged so it keeps its name.

Measured (M5 Pro, macOS 27, shared noise vs unpadded ONNX):
- mag-STFT SNR, ANE L128: shipped int4 1.0 dB -> v2 fp16 25.4 / int8 19.8 dB
- last-250 ms tail energy: v1 median -47 dB (max -5.5, 56/80 files audible)
  -> v2 -77..-79 dB, matching ONNX (-79); all quant levels
- VE 8 steps ~35 ms unchanged (still ANE); WER ~1% on 80 utts, unchanged
- Swift CLI e2e, 8-chunk paragraph: chunk tails v1 -109..-21 dB, v2 -109..-81 dB

v2 files are published next to v1 in FluidInference/supertonic-3-coreml
(HF commit 1b540236), so older releases keep working.
@github-actions

github-actions Bot commented Oct 8, 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 7.98x Real-time factor (higher = faster)
Total Audio 470.6s Total audio duration processed
Total Time 63.1s Total processing time

Streaming Metrics

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

Test runtime: 1m27s • 10/07/2026, 11:32 PM 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 8, 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: 0m36s

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 8, 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 17.41x >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 14.408 23.9 Fetching diarization models
Model Compile 6.175 10.2 CoreML compilation
Audio Load 0.099 0.2 Loading audio file
Segmentation 18.079 30.0 Detecting speech regions
Embedding 30.132 50.0 Extracting speaker voices
Clustering 12.053 20.0 Grouping same speakers
Total 60.284 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 • 60.3s diarization time • Test runtime: 4m 23s • 10/07/2026, 11:33 PM EST

@github-actions

github-actions Bot commented Oct 8, 2026

Copy link
Copy Markdown

PocketTTS Smoke Test ✅

Check Result
Build ✅
Model download ✅
Model load ✅
Synthesis pipeline ✅
Output WAV ✅ (161.3 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.

@github-actions

github-actions Bot commented Oct 8, 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 9.01x >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 20.284 17.4 Fetching diarization models
Model Compile 8.693 7.5 CoreML compilation
Audio Load 0.143 0.1 Loading audio file
Segmentation 31.231 26.8 VAD + speech detection
Embedding 116.161 99.7 Speaker embedding extraction
Clustering (VBx) 0.127 0.1 Hungarian algorithm + VBx clustering
Total 116.486 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 • 147.5s processing • Test runtime: 2m 30s • 10/07/2026, 11:42 PM EST

@github-actions

github-actions Bot commented Oct 8, 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.3x >1.0x ✅
Speakers 4/4 - -

Sortformer High-Latency • ES2004a • Runtime: 2m 33s • 2026-10-08T03:47:01.046Z

@github-actions

github-actions Bot commented Oct 8, 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% 434.1x faster 50
VOiCES 94.0% 89.3% 100.0% 94.3% 416.7x 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 8, 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.42x ✅
test-other 1.19% 0.00% 2.49x ✅

Parakeet v2 (English-optimized)

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

Streaming (v3)

Metric Value Description
WER 0.00% Word Error Rate in streaming mode
RTFx 0.39x Streaming real-time factor
Avg Chunk Time 2.176s Average time to process each chunk
Max Chunk Time 3.305s Maximum chunk processing time
First Token 2.642s 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.56x Streaming real-time factor
Avg Chunk Time 1.583s Average time to process each chunk
Max Chunk Time 2.102s Maximum chunk processing time
First Token 1.662s 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: 9m55s • 10/08/2026, 12:20 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 merged commit 184c111 into main Oct 8, 2026
20 checks passed
@Alex-Wengg
Alex-Wengg deleted the feat/supertonic3-v2-edge-pad branch October 8, 2026 04:44
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