Ming-3.0-audio-flash vs Qwen3-Omni-30B-A3B-Instruct

Ming-3.0-audio-flash

Ming-3.0-audio-flash is a cousin for Chinese and English transcription, questions about long audio and spoken replies in built-in or cloned voices, under MIT. It needs about 260 GB on a multi-GPU server, with inclusionAI's own runtime branches or Transformers remote code. The main risks are running repository code to load it and no published safety results.

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.

Ming-3.0-audio-flash

1. Start it with inclusionAI's recipe, hf download inclusionAI/Ming-3.0-audio-flash --local-dir inclusionAI/Ming-3.0-audio-flash && export MODEL_PATH="$PWD/inclusionAI/Ming-3.0-audio-flash" && pip install -r requirements-vllm-omni.txt && MING_OUTPUT_MODE=asr ./scripts/serve_vllm_omni.sh "$MODEL_PATH", run from a clone of github.com/inclusionAI/Ming-3.0-audio-flash
2. The 128K profile uses tensor parallelism over eight 80 GB H800 GPUs, the SGLang profile four and SGLang-Omni's cookbook two. It doesn't fit the 107.4 GB reference machine
3. Use MING_OUTPUT_MODE=asr with the validated prompt and greedy decoding for transcripts, and split the language label from the text at the tab
4. Use MING_OUTPUT_MODE=text for audio questions and the Talker profile with modalities=["text", "audio"] for spoken replies
5. Send audio as a base64 data URL in an audio_url item for vLLM-Omni, or as input_audio for SGLang
6. Pick a voice with audio.voice and an id, or clone one with ref_audio and its exact prompt_text, never both
7. Turn thinking on per request with chat_template_kwargs {"enable_thinking": true}, it's off by default and the reasoning comes back in think tags
8. Tool calls follow the template's <tool_call> with <arg_key> and <arg_value> pairs, and no parser is named, so parse them yourself
9. Review the repository's Python and the talker/ code, .pyc files included, before loading with trust_remote_code

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