Resolve Audio
Audio and Fairlight work in the DaVinci Resolve MCP.
Install
npx skills add samuelgursky/davinci-resolve-mcp --skill resolve-audio -g -a claude-code -y- Repository
- samuelgursky/davinci-resolve-mcp3.9k
- Category
- AI and agents
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 1,471 tokens
- Runs scripts
- No, instructions only
What it does
Audio and Fairlight work in the DaVinci Resolve MCP. Apply when setting audio properties, syncing audio, isolating voice, generating subtitles, planning Fairlight track/bus layouts, checking loudness, routing buses, or splitting/trimming/converting audio, live in a running Resolve OR offline. Routes to the live audio tools, the offline audio planning/bus-routing tools, and the Fairlight kernel.
Resolve Audio / Fairlight
Thin router; depth stays in the kernel.
- Live tool mechanics,
docs/kernels/audio-fairlight-kernel.md(thetimelineaudio/Fairlight boundary). - Offline planning + bus routing,
resolve-advanced/README.md→audio_plan,fairlight,audio.
Rough mix before anything else
If the ask is "make this sound balanced" rather than "route these buses", start with
media_analysis mix_plan (Python server, no Resolve needed). Give it the dialogue stems
and it derives the dialogue-normalisation gain, the music-bed level under it, and ducking
windows from the dialogue's own silence, then renders a premix and measures it, so
what you report is the loudness achieved rather than the gain arithmetic.
dry_run defaults to true: show the gains and the window count first. On a
full-programme standard (ebu_r128, web) a measured programme trim lands the whole mix
on target; on ott_dialogue_gated it deliberately does not trim, because dialogue is the
figure being graded. Flags (loudness_off_target, true_peak_over, clipped) come back
with remedies and are never auto-corrected, report them, do not paper over them.
