The argument in one line.
Connecting an AI agent directly to editing software lets one written prompt handle camera metadata, audio sync, color space, and proxy generation, cutting a wedding editor's project setup down to minutes of walk-away time.
Read if. Skip if.
- A wedding or multi-cam video editor who repeats the same footage-organizing setup, metadata, syncing external audio, color space, proxies, at the start of every project.
- Someone who hands off multi-cam sync to another editor and needs standardized metadata fields, like an exact 'angle' tag, for that handoff to work.
- An editor curious about connecting Claude to desktop creative software through MCP, beyond just chat-based prompting.
- You don't use DaVinci Resolve or software with an MCP integration, since the walkthrough is specific to that connection.
- You're looking for a step-by-step manual tutorial on multi-cam syncing in Resolve itself rather than an AI-automation overview.
The full version, fast.
A wedding video editor connects Claude Desktop to DaVinci Resolve and writes a chained prompt that tags every clip's camera angle, syncs an external interview mic to the matching camera footage by timecode, sets a camera's color space, and generates proxy media, tasks he otherwise repeats project after project. The agent asks clarifying questions when instructions are ambiguous, figures out which footage actually overlaps by timecode instead of syncing everything, and, once granted full screen control, can multi-select folders and batch a proxy render across hundreds of clips in one action. The payoff is a reusable prompt: refine it once against your own folder structure and field names, then paste it into every new project and let the setup run itself.
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.

01 · Cold open: reactions to the tool
Reaction montage stating the thesis before any setup is shown: one prompt can start a whole project.

02 · New wedding project, camera legwork
Context for why this setup happens on every project: footage has to be tagged by camera before it's handed to the multi-cam editor.

03 · First prompt: metadata as camera angles
Opens Claude Desktop connected to Resolve via MCP and writes the first prompt, tagging A/B/C-cam folders with angle numbers.

04 · Chaining prompts: audio sync and color space
Adds instructions to sync the interview mic to A-cam footage by timecode and set C-cam's color space to S-Log3/S-Gamut3.Cine, then runs the combined prompt.

05 · A clarifying question, then a naming mistake
Claude asks whether to also number the drone and ceremony-backup folders; the run then reveals the prompt updated 'camera number' instead of the 'angle' field the SOP actually needs.

06 · Corrected run: smart sync in six minutes
Rerunning the fixed prompt, the agent limits the mic sync to the 24 A-cam clips that actually overlap in timecode (out of 177) and finishes metadata, sync, and color space in six minutes.

07 · Verifying the fix, queuing proxies
Spot-checks confirm the angle field is now correct across B-cam, C-cam, and drone bins, then queues a new prompt for H.265 quarter-resolution proxies.

08 · Granting computer-use control
The proxy prompt requires more than MCP calls, so Claude is granted full computer-use permission and starts moving the window, screenshotting, and reading the screen directly.

09 · Why a reusable prompt matters
Explains the real payoff: perfect a prompt once and reuse it unchanged on future projects, then sends a follow-up prompt telling Claude to multi-select bins instead of working one at a time.

10 · 499 clips, one proxy batch
Claude command-clicks all five video bins and runs proxy generation across all 499 clips in a single action instead of per-bin.

11 · Recap and sign-off
Recaps the full automated setup, metadata, sync, color space, proxies, and closes with a comment/subscribe ask.
Lines worth screenshotting.
- Claude Desktop can connect to DaVinci Resolve through MCP so one prompt updates camera metadata, syncs audio, sets color space, and starts proxy generation without manual clicking.
- A prompt that said 'camera number' instead of 'angle' updated the wrong metadata field, so exact field-name language matters as much as the intent behind a prompt.
- Given a timecode-based sync instruction, the agent detected that an interview mic only overlapped 24 of 177 A-cam clips and synced just those instead of applying the sync to everything.
- Once a prompt is refined for one project's folder structure and camera setup, it can be copy-pasted into new projects and run unattended.
- Granting an AI agent full computer-use permission lets it click and multi-select inside desktop software directly, not just call predefined MCP actions.
- Command-clicking to multi-select all video bins let one proxy-generation prompt run across all 499 clips in a single batch instead of one bin at a time.
- A six-minute automated run replaced metadata tagging, audio sync, and color-space assignment that would otherwise be manual, per-clip work.
- Standardizing metadata field names, like 'angle' over 'camera number', matters because a downstream editor's SOP depends on exact naming to batch-sort footage correctly.
One prompt chain can run your whole pre-edit setup
Chaining an AI agent's prompts together, and correcting the ones that target the wrong field, replaces the manual metadata, sync, and proxy work that normally opens every multi-cam project.
- Standardizing per-camera metadata (angle 1, 2, 3) before handing footage to a second editor removes the need to manually re-sync every multi-cam clip later.
- Doing the repetitive setup work in the same order at the start of every project is what makes that work automatable in the first place.
- An AI agent connected to editing software through MCP can read a project's actual folder structure and apply a rule, like 'A cam is angle one', across every clip in that folder without you clicking into each one.
- Describing the exact task in plain language, including which folders map to which camera, is enough for the agent to start the update on its own.
- Multiple setup tasks, syncing external mic audio by timecode and setting a camera's color space, can be queued as a single chained prompt instead of done as separate manual steps.
- The agent asks for permission before checking the software's status, so a walk-away workflow still keeps a human in the loop on tool access.
- The agent asks a clarifying question when it finds ambiguity, like extra footage folders you didn't mention, rather than silently guessing.
- Using the wrong metadata field name in a prompt, 'camera number' instead of 'angle', produced a technically correct but practically useless result, because a downstream SOP depended on that exact field.
- Fixing a prompt that targeted the wrong field is faster than manually re-tagging clips by hand, but it still means the prompt's wording has to be exact, not just its intent.
- Given a timecode-based instruction, the agent worked out on its own that an interview mic only overlapped a subset of camera clips (24 of 177) and limited the sync to just those.
- A six-minute automated run replaced what would otherwise be per-clip manual tagging, audio syncing, and color-space assignment.
- Spot-checking a few clips after an automated batch update, rather than trusting it blindly, is what catches whether the fix actually propagated to every bin.
- A prompt that works for one project's structure can be saved and reused as-is on future projects with the same camera setup.
- Some actions, like generating proxies with specific codec and resolution settings, require an agent to have full mouse and screen control rather than just calling predefined commands.
- Granting that level of control means explicitly approving it, and the first run is slower while the agent figures out where things are in the interface.
- The real time savings come from perfecting one prompt once, then reusing it unchanged across every new project with the same footage structure.
- When an instruction causes an agent to do a repetitive action one item at a time, a follow-up prompt telling it to multi-select first can turn a per-item process into a single batch action.
- Batching a repetitive action, generating proxies for 499 clips in one command instead of triggering it per folder, is what actually creates the free time to do something else.
- An automated setup pass doesn't replace review, it just moves the editor's time from manual tagging into spot-checking the result.
Terms worth knowing.
- MCP (Model Context Protocol)
- An integration that lets Claude Desktop connect directly to software like DaVinci Resolve and read or change its project data through written prompts.
- A-cam / B-cam / C-cam
- Shorthand for the primary, secondary, and tertiary camera angles in a multi-camera shoot, used to label and sort footage by source.
- Angle metadata field
- A per-clip metadata tag recording which camera angle a clip came from, used by an editor's SOP to batch-sync multi-cam footage correctly.
- Timecode-based sync
- Matching separately recorded audio to camera clips by lining up their embedded timecodes, rather than manually scrubbing for overlaps.
- S-Log3 / S-Gamut3.Cine
- Sony's flat log color profile and matching color gamut, set on a camera's footage so it grades correctly alongside other camera sources.
- Proxy media
- Lower-resolution stand-in video files generated from full-resolution footage so a timeline plays back smoothly before final export.
- Computer-use permission
- A mode where an AI agent is granted mouse, keyboard, and screen control to operate an app's interface directly, beyond scripted commands.
Things they pointed at.
Lines you could clip.
“DaVinci linking up with Claude has to be the best update of literally my editing career.”
“I literally ran a prompt and six minutes later all these steps are done.”
“I can run this prompt and go pick my daughter up from school. Come back, whole project's done, gang.”
“This has to be, this should be paid for. There's no way you should be paying big money for this.”
Word for word.
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
The bait, then the rug-pull.
The video opens mid-reaction, before any context, with the editor already sold: one prompt to Claude can set up an entire wedding project inside DaVinci Resolve. What follows is the walkthrough of how he got there.
Named ideas worth stealing.
Multi-cam setup prompt chain
- Tag every clip's camera folder with its angle number (A cam = 1, B cam = 2, C cam = 3, etc.)
- Sync the external interview mic to the matching camera footage by timecode
- Set the input color space for the log-footage camera (S-Log3 / S-Gamut3.Cine)
- Number any remaining footage folders (drone, ceremony backup) so nothing is skipped
- Generate H.265 quarter-resolution proxies across every video bin in one batch
A sequence of instructions given to an MCP-connected AI agent that replaces the manual, per-clip setup work an editor normally repeats at the start of every project.
How they asked for the click.
“Any questions to this? Leave in the comment section below. As always y'all, keep creating and I will for sure see you in the next one.”
Soft closing ask paired with a standard subscribe/like end-card overlay rather than a hard pitch.





































































