MAJORFailure Reference

OpenAI Sora Audio Sync Drift — Refund Guide

Technical Classification

Audio-Visual Temporal Misalignment

Audio-Visual Temporal Misalignment on Sora occurs when the generated audio track and visual track are produced as loosely coupled streams. Sora 2 introduced native audio generation but synchronisation is statistical, not strict. On longer clips (≥ 4 seconds) or scenes with multiple discrete audio events (footsteps, impacts, dialogue), the audio can lead or lag the visual by 100-500ms — small enough to be subconsciously jarring, large enough to fail any professional QC.

How to identify this failure

✕Footstep audio fires before foot lands on the ground
✕Door slam audio precedes the visual door closing
✕Voice plays while mouth is closed or stationary
✕Ambient audio (rain, traffic) starts or stops outside visual cue
✕Drift increases over the duration of the clip

Real generation examples

Prompt used

"A man walking down a wooden hallway, footsteps echoing"

Failure observed @ 0:01 → 0:05

Footstep audio fires 200ms before each foot lands — gets worse over 5 seconds

Prompt used

"Coffee shop scene, barista calling out an order"

Failure observed @ 0:02 → 0:04

Barista voice plays for 1.2s while mouth is closed; mouth movement starts at 0:03

Documentation strength

If you need to escalate

HIGH — Audio sync is a marketed Sora 2 capability. Refund tickets citing temporal misalignment on paid clips are honoured with timestamp evidence.

AVA is a pre-purchase prevention tool, not a post-purchase recovery tool. Platforms generally do not guarantee credit refunds for output-quality failures; goodwill credits are at each platform's discretion. The strength rating reflects how well-formed your support ticket can be, not a promised outcome.

Prevention + documentation steps

01
Score your prompt before you generate
Run your prompt through AVA's pre-flight scoring against the Audio-Visual Temporal Misalignment pattern. Green light = generate. Yellow/red = rewrite using the suggested fix before you commit credits.
02
Capture Generation ID + timestamp if it failed anyway
Find the Generation ID in the URL or share link. Note the exact time when the Audio-Visual Temporal Misalignment first appears (e.g. "failure first visible at 1.2s"). Timestamped evidence is significantly stronger than a general complaint.
03
Use the correct technical term in your support ticket
Describe this failure as "Audio-Visual Temporal Misalignment". This term maps to a recognised internal workflow in the support system and routes the ticket to the right team.
04
Submit via the correct support channel
Runway has no direct email intake. Pro+ plan: open the in-app AI Assistant (help widget bottom-right of app.runwayml.com), describe the failure with the technical term, attach evidence. Free/Standard plan: human support isn't available — your channel is Discord #community-help with @On Call - Moderators.

Frequently asked questions

Does OpenAI refund Sora audio sync failures?

Yes — Sora support honours refunds when audio-visual misalignment is documented with paired timestamps (audio event time vs visual event time). Cite "Audio-Visual Temporal Misalignment" in the ticket.

Why does Sora audio drift out of sync?

Sora generates audio and visual through separate but cross-conditioned diffusion paths. There is no strict alignment constraint, so per-event timing drifts statistically — most visible on percussive events (footsteps, impacts) where 100ms is perceptible.

How do I avoid audio sync drift on Sora?

Keep clips short (≤ 4 seconds). Avoid scenes with multiple discrete audio events. Prefer continuous audio (music, ambient noise) over percussive cues. AVA flags percussive-heavy prompts as audio-sync risk.

Score your prompt

Score your prompt against this failure mode in 30 seconds

Paste your prompt and the platform you intend to use. AVA returns a red/yellow/green score against this specific failure mode plus a concrete rewrite if the risk is high.

Install free All 105 failure modes

AVA Pro · founders' round

$50 for 6 months of unlimited scoring across all failure modes + personal failure-history dashboard. Locks in $13/mo grandfathered after.

Claim $50 founders