Re:Qwen3-Omni-Flash-2025-12-01:a next-generation native mult...
by artur44 on Wednesday December 10, 2025 @02:19PM
(#46222239)
A simple way is to split the model’s output stream before TTS.
Reasoning/structured tokens go into one bucket, actual user-facing text into another. Only the second bucket is synthesized. Most thinking out loud issues come from feeding the whole stream directly into audio.
[ Parent
| on HN ]
Re:Qwen3-Omni-Flash-2025-12-01:a next-generation native mult...
by pugio on Wednesday December 10, 2025 @03:19PM
(#46223160)
There is no TTS here. It's a native audio output model which outputs audio tokens directly. (At least, that's how the other real-time models work. Maybe I've misunderstood the Qwen-Omni architecture.)
Re:Qwen3-Omni-Flash-2025-12-01:a next-generation native mult...
by artur44 on Wednesday December 10, 2025 @03:35PM
(#46223385)
True, but even with native audio-token models you still need to split the model’s output channels. Reasoning/internal tokens shouldn't go into the audio stream only user-facing content should be emitted as audio. The principle is the same, whether the last step is TTS or audio token generation.
Re:Qwen3-Omni-Flash-2025-12-01:a next-generation native mult...
by regularfry on Thursday December 11, 2025 @10:32AM
(#46232625)
There's an assumption there that the audio stream contains an equivalent of the <think>/</think> tokens. Every reason to think it should, but without seeing the tokeniser config it's a bit of a guess.