创建

登录 ReadmeX

或

了解我们如何处理你的信息: 隐私政策

ReadmeX

陪你读懂 AI 动态

今天,想先了解什么?

选一份动态总结,或直接聊聊你的问题。

社区和关注动态总结只属于你自己。

资讯

Pixel 11上的Nemotron 3.5流式ASR测试

AI 总结

PyTorch通过ExecuTorch在Google Pixel 11上测试了多语言Nemotron 3.5流式ASR,比较音频分块、FP16与QC8W精度及Arm SME2加速效果。启用SME2后,处理一段24.9秒录音的时间由FP16的9.79秒降至4.61秒,QC8W则由5.20秒降至3.24秒。研究还显示,较大的音频分块可改善字错误率,但会增加估算的首字延迟。

深度见解

该案例为边缘AI开发者提供了在同一设备上评估流式ASR准确率、延迟、量化与Arm CPU加速的实测参考,但结论仅来自PyTorch撰写的一项单机研究。

When you’re speaking to a device, you expect text to appear as you talk. That makes streaming automatic speech recognition (ASR) a different challenge from batch transcription, where the model has the complete recording before it starts. Strong batch accuracy does not necessarily carry over into streaming. One cross-model ASR study illustrates this gap. Qwen3-ASR-1.7B achieved the best batch accuracy among the models tested, but its word error rate (WER) rose by 77% when evaluated with 2.4-second audio chunks.

In that study’s cross-model streaming comparison (Table 5), NVIDIA® Nemotron

™

Speech Streaming 0.6B had the lowest average streaming WER when operating over 560 ms audio chunks. The comparison makes a critical point: accuracy must be measured at the chunk cadence used in deployment.

This case study takes the newer, multilingual Nemotron 3.5 from PyTorch to ExecuTorch and profiles its on-device execution on a Google Pixel 11. We ask how precision and chunk size change streaming quality, how much processing time the audio requires with one inference thread, where the workload spends its time, and which native kernels run. The goal is a practical way to evaluate accuracy and latency together.

#Nemotron 3.5#PyTorch#ExecuTorch#Google Pixel 11#Arm SME2#XNNPACK#KleidiAI#NVIDIA Nemotron Speech Streaming 0.6B#Qwen3-ASR-1.7B

原文约 9 分钟读完阅读原文
群聊

还没有评论,来说说你的看法。