DeepSeek-V4-Flash-0731 vs Qwen3-Omni-30B-A3B-Instruct

DeepSeek-V4-Flash-0731

A long-context agent cousin under MIT with documented tool calls, three reasoning effort levels and support in every major runtime but Ollama. It needs about 190 to 200 GB of memory, though six inference providers serve it. The main risks are prompts built from DeepSeek's Python, no published safety results and no answers in its repository.

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-Flash-0731

1. vllm serve deepseek-ai/DeepSeek-V4-Flash-0731 --trust-remote-code --kv-cache-dtype fp8 --block-size 256 --data-parallel-size 4 --enable-expert-parallel --moe-backend deep_gemm_mega_moe --attention-config '{"use_fp4_indexer_cache": true}' --speculative-config '{"method":"dspark","num_speculative_tokens":7,"draft_sample_method":"greedy"}' --tokenizer-mode deepseek_v4 --tool-call-parser deepseek_v4 --enable-auto-tool-choice --reasoning-parser deepseek_v4 (the card's 4x GB300 example plus the parser flags from vLLM's recipe)
2. Build prompts with encoding_dsv4.py, deepseek-recipe's V4 encoder or vLLM's --tokenizer-mode deepseek_v4, since the repository has no Jinja template
3. Tool calls come back in a DSML tool_calls block with invoke elements, string parameters carry string="true" and JSON values string="false"
4. Set temperature 1.0 and top_p 0.95 for agent work, and allow up to 384K output tokens at reasoning effort high or max
5. Without the hardware, call it through a Hugging Face inference provider (Together, DeepInfra, Novita, Baseten, Scaleway, Featherless), not DeepSeek's API, where deepseek-v4-flash now means V4.1 Flash
6. LM Studio's library build is a 156.4 GB MXFP4 GGUF and LM Studio states 156 GB minimum system memory

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