Why does Reel Name not persist when set via davinci-resolve-mcp even though the write returns success?
Writing the Reel Name clip property through davinci-resolve-mcp returns success: true, but reading it back shows the field still empty. The reporter used DaVinci Resolve Studio 21.0.0 on macOS Apple Silicon with external scripting set to Local, and tested 4 clips, with other fields writing correctly.
Originally asked on GitHub: https://github.com/samuelgursky/davinci-resolve-mcp/issues/77
4 answers
The maintainer's status: fixed in v2.57.5 (released on npm), but the fix changes reporting rather than the write itself. Resolve silently ignores scripted writes to Reel Name when the project setting "General Options → Assist using reel names from the:" is set to derive names automatically (from source clip file, embedding, or filename pattern), while SetClipProperty and SetMetadata still return True.
What v2.57.5 changes: set_clip_property, set_metadata (both the {key,value} and {metadata} forms), and normalize_metadata now read Reel Name back after writing. If it did not persist, the response includes verified: false, the requested and actual values, and a hint pointing at the project setting. Other fields and Reel Name writes that do stick are unaffected.
To get reel names to stick from the API, the maintainer says to set that General Options field to blank/manual, or assign reel names in the Resolve UI. The scripting API cannot override the gate.
A later comment reports that after upgrading to v2.57.5 with the General Options checkbox unchecked, the readback was still empty, so if this persists for you, check the project setting and the verified flag in the response. The fix was validated offline with unit tests, and the maintainer asked for confirmation against a real Resolve 21.0.0 ingest.
Did this work for you?What a GitHub user tried on GitHub (Didn't work)
Set the Reel Name clip property through several different write methods on Resolve 21.0.0 with davinci-resolve-mcp; each returned success: true, but an immediate read-back showed the field empty. A control write to another field on the same clip persisted correctly.
Source: https://github.com/samuelgursky/davinci-resolve-mcp/issues/77 (opens external site)
Did this work for you?What @samuelgursky tried on GitHub (Outcome unclear)
Maintainer suggested setting the project General Options field "Assist using reel names from the:" to blank/manual, or assigning reel names in the UI, since the scripting API cannot override the setting. Upgrading to v2.57.5 makes the failure report verified: false with a hint instead of silent success.
Did this work for you?What @DannyVR123 tried on GitHub (Didn't work)
Reporter upgraded to v2.57.5 with the General Options checkbox unchecked on Resolve 21.0.0 and still saw an empty readback after the write.
Did this work for you?
Related questions
- scriptapp('Resolve') returns None with DaVinci Resolve 20 on macOS
- Are quit_app/restart_app and save_project in davinci-resolve-mcp dangerous for LLM use?
- davinci-resolve-mcp on Linux: "No valid Resolve scripting module path found" despite correct PYTHONPATH?
- Why does davinci-resolve-mcp report no QuickTime codecs for ProRes LT renders?
- Automate Fusion rectangle masks and title text in davinci-resolve-mcp? Audio conversion is an API gap