# Resolve Audio

Audio and Fairlight work in the DaVinci Resolve MCP.

- Repository: https://github.com/samuelgursky/davinci-resolve-mcp (3887 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add samuelgursky/davinci-resolve-mcp --skill resolve-audio -g -a claude-code -y`
Codex: `npx skills add samuelgursky/davinci-resolve-mcp --skill resolve-audio -g -a codex -y`
Cursor: `npx skills add samuelgursky/davinci-resolve-mcp --skill resolve-audio -g -a cursor -y`
Gemini CLI: `npx skills add samuelgursky/davinci-resolve-mcp --skill resolve-audio -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Resolve Audio / Fairlight
Thin router; depth stays in the kernel.

- **Live tool mechanics**, `docs/kernels/audio-fairlight-kernel.md` (the
  `timeline` audio/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.

## Live subtitle effects

The rest: https://github.com/samuelgursky/davinci-resolve-mcp/blob/HEAD/.agents/skills/resolve-audio/SKILL.md