A video that plays without sound is not necessarily a video without an audio track. For a Qwen3-Omni pipeline on vLLM, that distinction deserves its own input-admission check—not just a “silent video” label in the asset library.
The vLLM v0.28.0 release notes, under Model Support → Correctness, report a fix for “a Qwen3-Omni crash on video without an audio track,” linking pull request #48420. That is a reported crash fix, not a new video-quality claim or proof that a particular deployment now accepts these assets. The checks below are proposed validation, not results from a test run.
Keep two different fixtures
For this regression check, use the same visual content where practical, but distinguish the files by their actual track structure:
| Fixture | What to verify | What it can test |
|---|---|---|
| Video with no audio track | No audio track is present at the intended ingestion boundary | The input condition named in the Qwen3-Omni crash fix |
| Video with a silent audio track | An audio track is present, but its content is silent | A comparison case that still contains audio structure |
A successful run of the second file does not cover the first condition. Listening to the clip—or muting playback—is not a substitute for checking its tracks.
Make direct admission a measured decision
Before allowing no-audio-track assets through the intended Qwen3-Omni path:
- Inspect both fixtures and the preprocessing output. Confirm that the no-audio-track case still has no audio track when it reaches ingestion. If preprocessing adds one, that run has not tested the proposed direct path.
- Run each fixture through the path you intend to use on vLLM v0.28.0. Record the actual serving version, model identifier, preprocessing settings and asset format alongside completion or failure. Keep the two outcomes separate.
- Use the no-audio-track result to decide admission. A pass supports admitting the tested asset class under those tested constraints. A continuing crash, or only a silent-audio pass, is not enough to enable it on the strength of the release note.
If your pipeline already adds synthetic audio as a workaround, make its removal conditional on that direct-path check. The release note does not establish that this workaround was necessary, common or behaviorally equivalent; there is no reason to introduce it solely because it appears in a validation discussion.
Keep quality acceptance separate
Crash-free processing answers “can this tested input complete?” It does not answer “did Qwen3-Omni understand the video correctly?” Keep the workflow’s output-quality acceptance check separate, and do not extend a passing fixture to untested codecs, other Qwen variants or performance claims.
The useful change is narrow: preserve no audio track as a distinct input category, and test it directly before changing what the pipeline admits or how it alters incoming assets.