Tractus

Picking a model to transcribe Korean meetings on a Mac: Qwen3-ASR, Whisper and Nemotron

Measured 2026-10-02 · Apple M3, 16 GB unified memory · everything runs locally with MLX · 28 runs, 0 failures

TL;DR: On Korean meetings, Qwen3-ASR-1.7B made 36% fewer errors than Whisper-large-v3-turbo (CER 9.49 vs 14.92) and transcribed an hour of audio in 8.2 minutes. Tractus uses it as the default model.

Tractus turns meeting recordings into text on your Mac, so we needed a model that runs on a Mac, handles Korean meetings well, and keeps the English terms people drop into Korean (p95 latency, connection pool). Most published numbers are for read speech or English, so we measured on data closer to real meetings.

What we measured

DatasetWhat it testsMetric
FLEURS-koClean read Korean; checks we reproduce published numbersCER
HiKEKorean–English code-switchingMER
AI Hub meeting speechReal multi-speaker meetings, 4 sessions, 66–90 min, 5.2 h totalCER
AMIEnglish meetingsWER

Lower is better for every metric. AI Hub data can't be redistributed, so only metrics are published.

Results

ModelFLEURS-ko CERHiKE MERAI Hub meetings CERAMI WER1 h of audioPeak memory
Qwen3-ASR-1.7B2.6224.19.499.508.2 min3.6 GB
Qwen3-ASR-0.6B3.9226.111.4710.143.3 min2.4 GB
Whisper-large-v3-turbo3.0826.614.9214.286.0 min2.2 GB
Nemotron 3.5 ASR 0.6B7.0245.110.9314.137.6 min2.0 GB

What we learned

Why not Nemotron

Its meeting CER beats the 0.6B model, but on code-switched speech its MER (45.1) is nearly twice the others, and it spells English acronyms in Hangul — term recall was 1.1%.

Limits

Code and full tables: bench/ · original write-up (Korean)