Skip to content

feat(logger): AppLogger.minimumLevel + mirrorsToConsole (#958) - #959

Merged
Alex-Wengg merged 1 commit into
mainfrom
feat/958-applogger-level
Sep 24, 2026
Merged

Alex-Wengg merged 1 commit into
mainfrom
feat/958-applogger-level

Conversation

@Alex-Wengg

Copy link
Copy Markdown
Member

Closes #958.

In Debug builds, AppLogger mirrors every level to stderr, and some ASR debug lines include recognised words. Apps that transcribe sensitive audio had no way to keep that text off the console.

  • AppLogger.minimumLevel drops messages below the chosen level from both os_log and the console. Default is .debug, so nothing changes unless an app sets it.
  • AppLogger.mirrorsToConsole = false stops console output and logs to os_log only (the Release path), in Debug builds too. Default is true.
  • Both settings are backed by an OSAllocatedUnfairLock. The routing now lives in an internal route(for:), and AppLoggerTests covers it.

Note: when Xcode's debugger is attached, os_log output still appears in the Xcode console, so minimumLevel is the setting that keeps transcript text out of it.

🤖 Generated with Claude Code

Debug builds mirror every AppLogger level to stderr, and several ASR debug
lines carry recognised words. Host apps handling sensitive audio (e.g.
clinical dictation) had no way to keep transcript text out of the Xcode
console short of not running Debug builds on real recordings.

- AppLogger.minimumLevel: levels below it are dropped from os_log and
  console alike (default .debug, unchanged behavior).
- AppLogger.mirrorsToConsole: false routes everything to os_log only,
  i.e. the Release path, in Debug too (default true).
- Both backed by an OSAllocatedUnfairLock rather than nonisolated(unsafe).
- Routing factored into an internal route(for:) so it is unit-testable.
- Level gains Comparable.
@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: 0m23s

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

Runtime: 0m26s

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

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

Streaming Metrics

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

Test runtime: 2m10s • 09/24/2026, 02:31 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

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 20.31x >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.313 21.9 Fetching diarization models
Model Compile 4.849 9.4 CoreML compilation
Audio Load 0.059 0.1 Loading audio file
Segmentation 15.496 30.0 Detecting speech regions
Embedding 25.827 50.0 Extracting speaker voices
Clustering 10.331 20.0 Grouping same speakers
Total 51.678 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 • 51.7s diarization time • Test runtime: 3m 16s • 09/24/2026, 02:33 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% 701.4x faster 50
VOiCES 94.0% 89.3% 100.0% 94.3% 638.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%

@Alex-Wengg
Alex-Wengg merged commit 0ceba1c into main Sep 24, 2026
13 checks passed
@Alex-Wengg
Alex-Wengg deleted the feat/958-applogger-level branch September 24, 2026 18:39
@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 13.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 16.286 20.5 Fetching diarization models
Model Compile 6.980 8.8 CoreML compilation
Audio Load 0.032 0.0 Loading audio file
Segmentation 21.753 27.4 VAD + speech detection
Embedding 79.107 99.7 Speaker embedding extraction
Clustering (VBx) 0.105 0.1 Hungarian algorithm + VBx clustering
Total 79.322 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 • 101.0s processing • Test runtime: 1m 46s • 09/24/2026, 02:40 PM EST

@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% 4.26x ✅
test-other 1.19% 0.00% 2.61x ✅

Parakeet v2 (English-optimized)

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

Streaming (v3)

Metric Value Description
WER 0.00% Word Error Rate in streaming mode
RTFx 0.56x Streaming real-time factor
Avg Chunk Time 1.573s Average time to process each chunk
Max Chunk Time 2.660s Maximum chunk processing time
First Token 2.128s 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.62x Streaming real-time factor
Avg Chunk Time 1.498s Average time to process each chunk
Max Chunk Time 1.702s Maximum chunk processing time
First Token 1.501s 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: 8m22s • 09/24/2026, 02:41 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

@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.0x >1.0x ✅
Speakers 4/4 - -

Sortformer High-Latency • ES2004a • Runtime: 4m 2s • 2026-09-24T18:41:57.647Z

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.

AppLogger: a minimum level or console switch for Debug builds (transcript words reach stderr)

1 participant