Native audio video generation: Veo 3.5 + Sora 2 — the property that removes the separate-audio-pipeline step

3 sources

Veo 3.5 (native audio generation with lip-synced dialogue + ambient sound) and Sora 2 (native audio + 60+ second character / scene consistency) both ship native audio generation in the same week. Together they define the 'native-audio video model' surface that removes the separate audio pipeline step from creator workflows — instead of generating video, exporting, then running a separate audio model, creators can ship single-take clips with synchronized audio. The two are not equivalent: Veo 3.5 ships on Vertex AI with explicit camera-motion API; Sora 2 ships with the Storyboard editor for shot planning.

Why now

Both shipped in the same week — creators can now rely on a single model for video + audio, simplifying the workflow significantly.

Why it is worth publishing

Demo potential: side-by-side of the same 30-second scripted scene with dialogue generated across Veo 3.5 vs Sora 2, measuring lip-sync accuracy and ambient-sound fidelity.

Evidence basis

Two independent vendor primary sources + The Decoder weekly roundup

“Veo 3.5 and Sora 2 both shipped this week — and together they remove the separate audio pipeline step from creator video workflows: one model handles video + synchronized audio.”

Angle

Frame the two as 'native-audio video model' surface — Veo 3.5 and Sora 2 remove the separate audio pipeline step from creator workflows.

Format

Long-form explainer

Demo idea

Record a 10-minute explainer: 3 min intro on 'native-audio video' framing, 3 min on Veo 3.5 (native audio + camera-motion API), 3 min on Sora 2 (native audio + Storyboard editor), 1 min on the workflow simplification.

Platform notes

Specific lip-sync accuracy and ambient-sound fidelity beyond the captured summary are not extracted; confirm with creator-side demo. Per-tier pricing is not extracted.

Usable claims

Google DeepMind Veo 3.5 GA on Vertex AI — 4K resolution support, native audio generation (lip-synced dialogue, ambient sound), camera-motion API.
OpenAI Sora 2 — 60+ second shots with character / scene consistency, native audio generation, Sora Storyboard editor.

Evidence pipeline

From the news

Breakdown

Veo 3.5 and Sora 2 both ship native audio generation, but they take different bets on workflow integration — Veo 3.5 on Vertex AI with camera-motion API, Sora 2 on Storyboard editor for shot planning. This explainer uses the workflow-integration comparison as the lens for picking a model, rather than collapsing them into 'both are native-audio, pick one'.

Sources

Risks

Use The Decoder and IT之家 as media-type corroboration, but read the underlying vendor docs for any specific capability or pricing claim before stating it on the record. Verify specific capability claim against the underlying vendor docs and the actual license / pricing matrix before stating it on the record; do not paraphrase per-platform pricing or license terms into specific dollar figures or commercial-use clauses.
Vendor docs confirm feature existence but specific pricing beyond the captured summary is not in this pass. Verify specific capability claim against the underlying vendor docs and the actual license / pricing matrix before stating it on the record; do not paraphrase per-platform pricing or license terms into specific dollar figures or commercial-use clauses.

Demo ideas

Side-by-side 30-second scripted scene with dialogue across Veo 3.5 vs Sora 2, measure lip-sync accuracy and ambient-sound fidelity.
Workflow simplification story: 'replace video-export + separate-audio-model with single-take native-audio generation', measure time saved and quality delta.
Workflow matrix: plot Veo 3.5 vs Sora 2 on workflow integration (Vertex AI vs Storyboard editor), input surface (camera-motion API vs script).