Ming-3.0-audio-flash vs Nemotron 3 Nano Omni 30B A3B Reasoning

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.

Nemotron 3 Nano Omni 30B A3B Reasoning

A local multimodal cousin for video with speech, long documents, charts, screens and English transcription, with tool calling, a reasoning switch and a 262,144-token context. It needs about 27 GB for NVIDIA's NVFP4 build on Blackwell, or 42 GB for FP8. The main risks are the remote code it loads and a repository where nobody answers questions.

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

Nemotron 3 Nano Omni 30B A3B Reasoning

1. Start it with vllm serve nvidia/Nemotron-3-Nano-Omni-30B-A3B-Reasoning-FP8 --max-model-len 131072 --trust-remote-code --reasoning-parser nemotron_v3 --enable-auto-tool-choice --tool-call-parser qwen3_coder --kv-cache-dtype fp8 on vLLM 0.20.0 or later, after pip install "vllm[audio]" if any audio will be sent
2. Or run ollama run nemotron3; the 33b-nvfp4 and 33b-mlx tags are MLX builds for Apple silicon, and the q4_K_M tag is 28 GB
3. Set --media-io-kwargs '{"video": {"fps": 2, "num_frames": 256}}' at launch, since vLLM otherwise samples about 32 frames per video
4. Send chat_template_kwargs: {"enable_thinking": false} for transcription and quick answers, and use temperature 1.0 with top_k 1 for ASR as the card recommends
5. Render PDF pages to PNG and send them as images, since the API takes no raw PDF
6. Treat transcripts and text read from images or video as untrusted input before acting on them