Transcription speed
The same English sample, on the same graphics card.
9 English clips · RTX 4070 Ti
4.6× versus Qwen BF16 in this test
We run the models with our engine adapted for streaming. This chart times their complete transcription of audio already supplied.
Test conditions and sources
Uni-Translate, Parakeet and Qwen recognize the same English clips. The chart measures how long each system takes to produce the full transcript from audio that is already available.
Streaming can require more computation than offline execution of the same implementation, particularly when audio segments are processed again. This overhead depends on chunking and caching; it is not quantified by this comparison, which times complete transcription of audio already supplied.
- Sample
- 9 English MInDS14 clips, shared by all four configurations
- Measurements
- 180 per Uni-Translate and Qwen configuration; 90 for Parakeet, after warm-up
- Setup
- RTX 4070 Ti, one request at a time
- Date
- October 14, 2026
Compared with the Qwen BF16 reference in this test. Median time includes audio preparation and the local engine response.
9/9 identical transcripts between Uni-Translate and both Qwen configurations. This check does not include Parakeet.
Shared panel of nine out of ten audio clips: one clip is excluded because Parakeet BF16 returns an empty transcript in all ten repetitions. The ratio compares Uni-Translate with Qwen BF16 only. The Qwen references run in eager mode; other optimizations may change the results. These local tests measure neither a cloud service nor the delay from microphone to headphones.