DeepSeek V4.1 Flash vs Qwen3-Omni-30B-A3B-Instruct

DeepSeek V4.1 Flash

A large multimodal agent model with a 1M-token context, documented tool calls, JSON Schema output and a reasoning budget, under MIT. It needs about 612 GB of memory across several GPUs in vLLM or SGLang. The main risks are prompts built from DeepSeek's code rather than a template, no published safety results and no answers in its repositories.

Qwen3-Omni-30B-A3B-Instruct

An omni-modal cousin that listens, watches and reads, then answers in text or one of three voices, with tool calls from spoken requests, under plain Apache 2.0. Its only build, BF16, needs about 85 GB, and speech out needs Transformers or vLLM-Omni. The main risk is no answers from Qwen and no safety work for speech-driven actions.

DeepSeek V4.1 Flash

1. DeepSeek's reference run is its inference folder, convert.py with --model-parallel 8 --expert-dtype fp4, then torchrun --nproc-per-node 8 generate.py --ckpt-path "$SAVE_PATH" --config config.json --interactive
2. In vLLM 0.32.0 the parsers are named deepseek_v41 for both --tool-call-parser and --reasoning-parser. That's vLLM's naming, DeepSeek doesn't document a vLLM command
3. Build prompts with encoding.py or pip install deepseek-recipe, not the September repository's chat_template.jinja, which an open pull request says trails the 16 October encoding
4. Tool calls come back in a DSML calls block with a space before calls, invoke and parameter, unlike V4
5. Set reasoning_effort to 1 to 100, or low, high or max (50, 75, 100), in thinking mode only. Default is 75
6. Sample at temperature 1.0 and top_p 1.0 and allow 256K or more output tokens, as the card recommends
7. Without the hardware, call DeepSeek's API as deepseek-flash, which serves this exact update

Qwen3-Omni-30B-A3B-Instruct

1. For text answers, mkdir -p media && vllm serve Qwen/Qwen3-Omni-30B-A3B-Instruct --dtype bfloat16 --max-model-len 32768 --allowed-local-media-path "$(pwd)/media" with vLLM 0.11.1 or later serves the Thinker on an OpenAI-compatible API
2. The card's command passes --allowed-local-media-path /, which lets anyone who can reach the server have it read any file on the machine through a file:// URL. Point it at a dedicated folder that holds only the media you mean to send, as above, and give vLLM an absolute path
3. Send audio as audio_url and images as image_url content parts; vLLM serve doesn't take use_audio_in_video, so pass a video's audio separately
4. For speech out, load Qwen3OmniMoeForConditionalGeneration in Transformers 4.57.0 or later with qwen-omni-utils, pick speaker Ethan, Chelsie or Aiden, and write the returned waveform at 24 kHz
5. Call model.disable_talker() or pass return_audio=False when you only need text, which saves about 10 GB and time
6. Parse tool calls as JSON inside <tool_call> tags yourself, since no parser is named, and confirm actions triggered by speech before running them
7. Keep use_audio_in_video the same across every step of a conversation, the card warns results go wrong otherwise
8. Budget memory for video, the card's table rises from 78.85 GB for 15 seconds to 144.81 GB for 120 seconds in BF16