Import client notes into DaVinci Resolve as markers
Install the UC marker script, configure your API key, match the review clip and check timing before using it on a client timeline.
Updated 16 September 2026
The UC Python marker script reads review notes and places markers on the current Resolve timeline. Run it again to refresh its markers. It is a script you launch, not a continuously syncing panel, and changes made to markers do not update the client’s notes.
Verify the handoff into the edit
Verify the handoff into the edit
Test one note with a recognizable video position before transferring a full round of feedback. Check the version and timecode convention so the note points to the intended moment in the edit. Preserve the original request even if the timeline position changes later.
Keep a neutral list of requests and completed work outside the editing timeline as well. This is a manual record-keeping recommendation, not a claim that the current review workflow supports every Resolve marker import or export format.
Install and connect the script
- Download uncompressed-markers.py below. Make sure Python scripting works in your Resolve edition and installation; consult the scripting documentation shipped with that version.
- Put the file in Resolve’s user Scripts/Utility folder. On macOS: ~/Library/Application Support/Blackmagic Design/DaVinci Resolve/Fusion/Scripts/Utility. On Windows: %APPDATA%\Blackmagic Design\DaVinci Resolve\Support\Fusion\Scripts\Utility.
- Create a .uncompressed file in your home folder containing api_key= followed by your UC API key from dashboard Settings. Keep the key private. The script also reads configuration alongside itself.
- Open the project and timeline, then run Workspace Scripts Utility uncompressed-markers. Read progress and matching messages in Workspace Console.
Match the right film before importing
The script tries the timeline name, then the project name, against UC clips with notes. If necessary, set clip_title=Exact clip title in your .uncompressed file. Use a unique title and confirm the matched film shown in the console. Similar or duplicate titles need extra care.
Make a copy of the timeline first. Place a known note near the start and one near the end of your review export. Import them, then compare their frames with the browser notes. The script calculates frames from note seconds and the timeline frame rate; different timing, slates or retimed exports can create mismatches.
What is imported and what is not
Top-level notes become markers: red for open, green for done, with the author and note text. Replies are not separate markers. A drawing is flagged in the marker text; the drawing itself does not appear as a Resolve marker image.
The current script fetches a film’s top-level notes without filtering by version or aspect. Do not assume it selects only the revision on your current timeline. For a clean pilot, use a film with one review version and inspect the imported list before relying on it.
When notes land on an occupied frame, the script tries that frame and the next five. Markers can therefore be shifted by up to five frames, or omitted if none are available. Check the placed-note count and crowded timestamps. This is not a guarantee that every note lands on an identical frame.
Refresh after a review round
Resolve a note in the UC room and run the script again. It removes and recreates markers tagged as its own; other markers are left in place. Editing or deleting a marker in Resolve does not resolve the browser note. The room remains the source of its done state.
If nothing imports, check the API key, selected timeline, unique clip title, notes and network response in the console. If the script is absent from the menu, check its folder, Python configuration and scripting support in that Resolve installation.
Compatibility and verification scope
These instructions were checked against the downloadable script and its UC endpoints on 16 September 2026. No new end-to-end recording in a named Resolve version accompanies this release. Run the two-note pilot on the exact editing machine before adopting it for a deadline.
Editor integrations and downloads · Archiving the completed timeline. Archiving is a separate script and requires paid cold storage.
Frequently asked
How do I bring client comments into DaVinci Resolve?
Install uncompressed-markers.py in Scripts/Utility, configure your UC API key, open the correct timeline and run it from Workspace Scripts. Confirm the matched film and test two known note positions before importing a full round.
Does the script import only the current version’s notes?
No. The current script fetches top-level notes for the film without filtering by version or aspect. Inspect the set and use a simple one-version pilot before relying on it.
Are the markers always frame-exact?
Timing comes from note seconds and the timeline frame rate. Occupied frames cause retries up to five frames later, and a note can be skipped if those positions are occupied. Verify timing and marker counts.
Does marking a Resolve marker green update UC?
No. Resolve the note in UC, then rerun the script. The synchronization is one-way into Resolve.
Host your work at full bitrate
Play your uploaded export without another platform re-encode. Browser compatibility and connection requirements still apply. Start with one film, then compare current storage and team allowances.
Start free