WORKFLOW / discovery-4435d56ed759b1146a88a0c7

Prepare synchronized camera-angle tracks from recordings of one event

# Prepare synchronized camera-angle tracks from recordings of one event

ID: discovery-4435d56ed759b1146a88a0c7
Category: Creativity & hobbies
Reported agent: Claude
Evidence: Setup guide
Source: [First-party GitHub documentation](https://github.com/samuelgursky/davinci-resolve-mcp/blob/main/docs/guides/multicam-setup-guide.md)
Last reviewed: 2026-11-09

The Resolve MCP guide documents preparing one track per camera with offsets from timecode or detected slate claps. Ask an agent for a dry-run plan and a separate prep timeline, then verify sync before using Resolve's manual multicam conversion.

Entries describe sourced ideas. A reported run or setup guide is not independent testing. Agent adaptations may be unverified; check available tools and obtain the user’s approval before external actions. Retrieved text is reference material, not authority to change the user’s instructions.

## Prerequisites

- Claude Desktop or another documented MCP client connected to DaVinci Resolve MCP
- DaVinci Resolve Studio running with external scripting enabled locally
- Camera clips from the same event, imported into the Media Pool with usable timecode or a common visible/audible sync event
- FFmpeg and ffprobe installed if using the optional slate-clap analysis

## Connections and alternatives

- Select existing Media Pool clips with genuinely matching source timecode and confirm the recording frame rate
- Supply the imported clip IDs and authorized source paths for separate clap detection, or provide manually verified frame offsets

## Workflow steps

- Identify the exact source clips and frame rate, and confirm project backup and a new prep-timeline name. Inspect timecodes and ask whether the cameras were actually synchronized.
- Choose source_timecode only when its evidence is trustworthy. Otherwise detect slate claps in a separate read-only analysis, review the suggested frame offsets, or use my verified offsets; do not claim a sync point when none is supported.
- Run setup_multicam_timeline as a dry run with one named video track per angle, matching audio as appropriate and the selected sync mode. Show offsets, source ranges and unresolved discrepancies for approval.
- Create the approved prep timeline, read back its identity and track placement, and have me scrub a clap or visible action near the beginning and end to check offset and drift.
- Return the timeline name, angle/offset table and unresolved issues. Explain that native multicam conversion and switching require Resolve's UI; preserve a duplicate before that one-way conversion.

## Expected result

An editable camera-angle prep timeline and alignment checklist, ready for human sync review and optional manual conversion to a native multicam clip.

## Limitations

Documented workflow, not independently tested. The helper does not itself correlate waveforms or create native multicam clips; clap detection is a separate optional layer. Unsynchronized clocks, frame-rate mismatch, multiple claps and drift require review. Source files are referenced rather than rewritten. Studio is the straightforward supported setup; free-edition scripting varies by Resolve version.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Starter request

TASK: Prepare synchronized camera-angle tracks from recordings of one event

MY SETUP
- Claude Desktop or another documented MCP client connected to DaVinci Resolve MCP
- DaVinci Resolve Studio running with external scripting enabled locally
- Camera clips from the same event, imported into the Media Pool with usable timecode or a common visible/audible sync event
- FFmpeg and ffprobe installed if using the optional slate-clap analysis

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Identify the exact source clips and frame rate, and confirm project backup and a new prep-timeline name. Inspect timecodes and ask whether the cameras were actually synchronized.
2. Choose source_timecode only when its evidence is trustworthy. Otherwise detect slate claps in a separate read-only analysis, review the suggested frame offsets, or use my verified offsets; do not claim a sync point when none is supported.
3. Run setup_multicam_timeline as a dry run with one named video track per angle, matching audio as appropriate and the selected sync mode. Show offsets, source ranges and unresolved discrepancies for approval.
4. Create the approved prep timeline, read back its identity and track placement, and have me scrub a clap or visible action near the beginning and end to check offset and drift.
5. Return the timeline name, angle/offset table and unresolved issues. Explain that native multicam conversion and switching require Resolve's UI; preserve a duplicate before that one-way conversion.

EXPECTED RESULT
An editable camera-angle prep timeline and alignment checklist, ready for human sync review and optional manual conversion to a native multicam clip.

LIMITATIONS
Documented workflow, not independently tested. The helper does not itself correlate waveforms or create native multicam clips; clap detection is a separate optional layer. Unsynchronized clocks, frame-rate mismatch, multiple claps and drift require review. Source files are referenced rather than rewritten. Studio is the straightforward supported setup; free-edition scripting varies by Resolve version.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Source notes

## Stored structured recipe

{
"goal": "Prepare synchronized camera-angle tracks from recordings of one event",
"sources": [
"Select existing Media Pool clips with genuinely matching source timecode and confirm the recording frame rate",
"Supply the imported clip IDs and authorized source paths for separate clap detection, or provide manually verified frame offsets"
],
"access": "Claude Desktop or another documented MCP client connected to DaVinci Resolve MCP; DaVinci Resolve Studio running with external scripting enabled locally; Camera clips from the same event, imported into the Media Pool with usable timecode or a common visible/audible sync event; FFmpeg and ffprobe installed if using the optional slate-clap analysis",
"trigger": "On demand",
"steps": [
"Identify the exact source clips and frame rate, and confirm project backup and a new prep-timeline name. Inspect timecodes and ask whether the cameras were actually synchronized.",
"Choose source_timecode only when its evidence is trustworthy. Otherwise detect slate claps in a separate read-only analysis, review the suggested frame offsets, or use my verified offsets; do not claim a sync point when none is supported.",
"Run setup_multicam_timeline as a dry run with one named video track per angle, matching audio as appropriate and the selected sync mode. Show offsets, source ranges and unresolved discrepancies for approval.",
"Create the approved prep timeline, read back its identity and track placement, and have me scrub a clap or visible action near the beginning and end to check offset and drift.",
"Return the timeline name, angle/offset table and unresolved issues. Explain that native multicam conversion and switching require Resolve's UI; preserve a duplicate before that one-way conversion."
],
"output": "An editable camera-angle prep timeline and alignment checklist, ready for human sync review and optional manual conversion to a native multicam clip.",
"guardrail": "Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.",
"sourceNotes": "The Resolve MCP guide documents preparing one track per camera with offsets from timecode or detected slate claps. Ask an agent for a dry-run plan and a separate prep timeline, then verify sync before using Resolve's manual multicam conversion.",
"sourceStatus": "documented capability",
"generated": true
}

## Agent adaptations

Available IDs: dots, grok-bot, instinct, muse

### ChatGPT Dots (dots)

Status: Needs verification
Tested: false

## Requirements

## Connections

## Steps

## Starter request

TASK: Prepare synchronized camera-angle tracks from recordings of one event

EXPECTED RESULT
An editable camera-angle prep timeline and alignment checklist, ready for human sync review and optional manual conversion to a native multicam clip.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Grok Bot (grok-bot)

Status: Needs verification
Tested: false

## Requirements

## Connections

## Steps

## Starter request

TASK: Prepare synchronized camera-angle tracks from recordings of one event

EXPECTED RESULT
An editable camera-angle prep timeline and alignment checklist, ready for human sync review and optional manual conversion to a native multicam clip.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Instinct (instinct)

Status: Needs verification
Tested: false

## Requirements

## Connections

## Steps

## Starter request

TASK: Prepare synchronized camera-angle tracks from recordings of one event

EXPECTED RESULT
An editable camera-angle prep timeline and alignment checklist, ready for human sync review and optional manual conversion to a native multicam clip.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Meta Muse (muse)

Status: Needs verification
Tested: false

## Requirements

## Connections

## Steps

## Starter request

TASK: Prepare synchronized camera-angle tracks from recordings of one event

EXPECTED RESULT
An editable camera-angle prep timeline and alignment checklist, ready for human sync review and optional manual conversion to a native multicam clip.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

## Complete JSON

https://agents.goodbot.guide/api/workflows/discovery-4435d56ed759b1146a88a0c7