Comment by cnj
21 hours ago
I've had Claude Code drive DaVinci Resolve before in three ways: - Generate .otio files that are imported. Unfortunately, .otio doesn't fully support everything Resolve can do. - Resolve has a scripting engine. Claude can write Lua scripts, then execute the script (through UI Automation) - Computer Use. It's quite token intense, but it works.
I didn't try it, but for the paid version, someone also built a MCP server based on the scripting engine.
I'm programmatically adding analysis to sim racing lap guides, therefore my flow is probably different from the usual editing flow, but I have to say I found Claude Code + Opus to be quite capable of making edits with computer use.
I had AI write a program to edit with resolve. It does transcription, looks at the transcript and decides where to make cuts. If does a decent job and saves me a bunch of time.
I spent a few tokens last year trying to create a Python lib for native (undocumented) Resolve files. I was making progress, but it was slow (I ended up scripting Resolve in different ways). I imagine that current models could reverse-engineer the native file format relatively quickly.
I helped my girlfriend use the MCP server as she had a project where all the media files had been moved to a new source location, and using Codex, it managed to hunt down all the files and stitch it all back together. Ended up saving quite a lot of manual boring labour, and was quite cool to see it work in real time:)
I used IntelliScript a lot. I give Claude a subtitle export, ask it to cut it and import the cut subtitle track with IntelliScript. Resolve then creates a video version that’s cut based on the subtitle changes
Works pretty well!
> I'm programmatically adding analysis to sim racing lap guides
Yosh is that you?
No, I'm Chris :) But if you know Yosh well, would be happy to connect and compare notes!