vllm - ✅(Solved) Fix [Usage]: qwen3-asr-1.7b pre-allocated encoder cache size limit [1 pull requests, 4 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vllm-project/vllm#39408Fetched 2026-04-10 03:40:48
View on GitHub
Comments
4
Participants
2
Timeline
7
Reactions
0
Author
Timeline (top)
commented ×4cross-referenced ×1labeled ×1renamed ×1

Error Message

When i request a longer audio , return {'error': {'message': 'The decoder prompt contains a(n) audio item with length 3476, which exceeds the pre-allocated encoder cache size 2048. Please reduce the input size or increase the encoder cache size by setting --limit-mm-per-prompt at startup.', 'type': 'BadRequestError', 'param': None, 'code': 400}},

Fix Action

Fixed

PR fix notes

PR #39409: [UX] Improve error message for MM input too long

Description (problem / solution / changelog)

Purpose

Improve the wording of the error message to avoid confusion like in https://github.com/vllm-project/vllm/issues/39408, because "length" can be confused with video/audio length.

Test Plan

Test Result


<details> <summary> Essential Elements of an Effective PR Description Checklist </summary>
  • The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
  • The test plan, such as providing test command.
  • The test results, such as pasting the results comparison before and after, or e2e results
  • (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.
  • (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.
</details>

Changed files

  • vllm/v1/engine/input_processor.py (modified, +3/-3)
RAW_BUFFERClick to expand / collapse

Your current environment

vllm 0.19.0

How would you like to use vllm

pip install vllm[audio] exec python3 -m vllm.entrypoints.openai.api_server
--model /Qwen3-ASR-1.7B
--host 0.0.0.0
--port 30000
--served-model-nameqwen3-asr
--max-model-len "65536"
--limit-mm-per-prompt '{"audio":{"count":1,"length":32768}}' When i request a longer audio , return {'error': {'message': 'The decoder prompt contains a(n) audio item with length 3476, which exceeds the pre-allocated encoder cache size 2048. Please reduce the input size or increase the encoder cache size by setting --limit-mm-per-prompt at startup.', 'type': 'BadRequestError', 'param': None, 'code': 400}}, how to change limit-mm-per-prompt parameter

Before submitting a new issue...

  • Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

extent analysis

TL;DR

Increase the --limit-mm-per-prompt parameter value to allow for longer audio inputs.

Guidance

  • The error message indicates that the audio input length exceeds the pre-allocated encoder cache size, which is currently set to 2048.
  • To fix this, you need to increase the --limit-mm-per-prompt parameter value, specifically the audio.length property, to a value greater than 3476.
  • You can do this by modifying the command to include a higher value for --limit-mm-per-prompt, for example: --limit-mm-per-prompt '{"audio":{"count":1,"length":65536}}'.
  • Verify that the new value allows for longer audio inputs without exceeding the maximum allowed length.

Example

python3 -m vllm.entrypoints.openai.api_server \
  --model /Qwen3-ASR-1.7B \
  --host 0.0.0.0 \
  --port 30000 \
  --served-model-name qwen3-asr \
  --max-model-len "65536" \
  --limit-mm-per-prompt '{"audio":{"count":1,"length":65536}}'

Notes

The optimal value for --limit-mm-per-prompt will depend on the specific requirements of your application and the available resources.

Recommendation

Apply workaround: Increase the --limit-mm-per-prompt parameter value to allow for longer audio inputs, as this will resolve the immediate issue and allow for further testing and evaluation.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING