Notes in, markers on the timeline, v2 on the same link.

4 things that go wrong

What breaks the revision loop, and how this fixes it

One revision cycle

The loop, with the friction removed

1. 01

   Footage lands organized

   The producer drops the shoot into your receive link, or the whole team works from one Project Sync folder. Either way the tree on your disk matches the tree that was shot.

2. 02

   The cut goes out from your desktop

   Flag your exports folder for review and export into it from any NLE — the app detects when the render finishes writing and uploads it on its own, encoded, ready for comments. Exporting IS publishing, and none of it requires Resolve.

3. 03

   Notes come back on frames

   The client comments at timecodes, replies in threads, reacts 👍 to what they agree with. You can answer a note and they'll get an email if they opted in — no 'did you see my note?' calls.

4. 04

   Notes become markers

   One click in the Resolve app pulls the link's comments onto your timeline as markers. Work marker to marker instead of window to window.

5. 05

   Render & upload from the same panel

   The Resolve app renders with your preset and sends the new version straight to the same review link as v2. The client gets the current cut at the URL they already have.

6. 06

   Approval, on the record

   When the client clicks Approve on the link, the loop is closed — in writing, on the same page where every note lived.

The loop's two surfaces

Their review page, your Resolve panel

Left: the review link where the client comments on timecode. Right: the Resolve app that turns those comments into markers and uploads the next version.

Questions editors ask

Frequently asked

How do client comments get into Resolve?

The free Mac app talks to DaVinci Resolve through its scripting API — no plugin install inside Resolve, just enable external scripting in Resolve's preferences once. Pick the project, click import, and the review link's comments land as markers at their timecodes on your timeline.

Can I render and upload without leaving Resolve's ecosystem?

Yes. The app's Resolve tab renders your current timeline with a render preset you choose and uploads the result as the next version on the review link — or drops it into a magic folder that publishes it automatically. It can also import a footage folder into your media pool as bins that mirror your folder structure, camera-card junk excluded.

Do new versions notify the client?

The review page shows the new cut at the top of the same link the client already has — they see it on their next visit, and a banner points out a new cut arrived while they were on the page. Prior versions stay accessible so 'wait, what changed?' has an answer.

How good are the transcripts?

They're generated by a dedicated speech engine, readable with timecodes alongside the player, and editable inline when a name or term needs fixing. Export .srt/.vtt for captions or plain text for paper edits. Each video's transcript is a click away for anyone on the review link.

Does the client need an account to comment or approve?

No. They type a name with their first comment and that's the whole setup. Optionally they add an email to be notified when you reply to their note. Approval is a button on the same page.

I'm on Premiere, not Resolve. Is this useless to me?

The Resolve integration is Resolve-only, but everything else — review links, stacked versions, transcripts, receive links, Project Sync, deliveries — is NLE-agnostic. You export from Premiere into a magic folder and the publish step is identical.

What does the client actually see when I share a link?

A clean player page with the current cut, a comment rail, version history, and optional transcript — under the project's name, not a third-party brand. No account wall, no app install, works on their phone.