Built for the Sync Pass — where story is found in language. Read your rushes as text, compile the story, and apply it to your Resolve timeline at word-level precision with one click.
Or let AI do the heavy lifting. The SyncPass Automation Tool uses your favourite AI assistant to build a structured Sync Pass instantly — then you refine it with the judgment only an editor has.
DaVinci Resolve is famous for finishing.
But the story isn't built in the colour suite — it's built in words.
Every NLE connects footage to a timeline. None of them connect the words to the timeline — not in a way that works both directions. The moment you start cutting, text and edit diverge and stay diverged.
SyncPass changes that.
Use it to build your initial structure - Sync and Voice Over - the script and the timeline the same thing — then move on to the next stage with your edit script and timeline skeleton ready to be crafted.
Documentary editors have always lived between two worlds — and every tool forces them to abandon one to use the other. SyncPass is built for the sync pass: the initial assembly stage where you work purely with sync sound, finding the story in the words before adding GVs, music, or effects.
Read transcripts. Mark up lines. Lift them into a Word doc with timecodes. Rearrange on the page until the structure feels right. Then manually execute every cut on the timeline.
The moment the edit exists on the timeline, the document becomes a maintenance burden — constantly out of sync with what's on the timeline.
Modern NLEs like DaVinci Resolve let you select transcript lines and add them to the timeline. A genuine improvement — but with one fatal limitation.
Once material lands on the timeline, the text relationship is broken. Assembly begins, text-based thinking ends.
A third mode: one where the timeline and the text document are the same thing, represented two different ways simultaneously. Edit the text, the timeline updates. Reorder a paragraph, the sequence changes. Delete a sentence, the clip disappears.
And when the sync pass is complete, export a fully-structured edit script — with speaker labels, scene headers, and VO notes — as a Word document. The handoff document your Edit Producer needs, generated automatically from the edit itself.
Word-level precision. One click to apply. One click to export.
See how SyncPass connects your transcripts directly to DaVinci Resolve — from sync pass assembly to timeline in one click.
If the video shows an error - just click "Watch Video on YouTube"
Run the SyncPass Transcriber from inside Resolve. It scans your media pool, passes each clip through OpenAI Whisper (running locally on your machine — no internet required after initial download), and saves a transcript sidecar file next to each media file on disk. Transcription is a one-time operation per clip.
Open SyncPass from the Resolve Workspace menu. The Rushes tab shows your media pool as a bin tree — identical folder structure to Resolve, but only showing transcribed clips. Click a clip, its full transcript appears — every word, with natural paragraph breaks. Toggle timecode on or off. Fix any typos and label contributors (optional). Highlight any passage, add it to your pull list.
When your pull list reflects the edit you want, click Apply to Timeline. SyncPass places each selected passage on the timeline at the correct source in and out points — to the frame.
Switch to the Script tab. Your timeline is now displayed as editable text — one paragraph per clip sequence, speaker labels in bold. Cut and paste text to rearrange the edit. Delete a line to remove a clip. Move a sentence and SyncPass moves the frame-accurate clip data with it.
Add VO notes inline. Insert scene headers. Mark beats. Click Apply to Timeline to rebuild to your new version. When the sync pass is complete, export the whole thing as a formatted Word document — the edit script you, your Edit Producer or the Director takes forward as the cut evolves beyond the sync pass.
Don't want to build the sync pass manually? Export a word-tagged transcript package to any AI assistant — Claude, ChatGPT, Gemini, or anything else. Prompt your AI with instructions for how you want your sequence (this is the part that will always require a creative brain to input) - the AI reads your full rushes as text, proposes a structured edit, and SyncPass imports the result, building the timeline from it.
Hours of rushes can become a rough sync pass in minutes. You review, reshape, and apply your editorial judgment to a structure that already exists — rather than building from nothing. The creative decisions stay yours. The mechanical sorting doesn't have to be.
Moving a word in the Script tab moves the exact frames it represents — some trimming may still be required, but you'd need to trim if you were punching in Timecodes too!
Edit the text, the timeline updates. Reorder a paragraph, the sequence changes. Changed the sequence? Click "Reload from Timeline" and the script updates. The two representations are always in sync. There's no translation step between thinking and doing.
Transcription runs entirely offline using Whisper after initial model download. No audio, video, or transcript is ever sent anywhere. The only external step is the optional AI Automate export — and that's always something YOU choose to do.
Transcript files live next to the media, not inside the project. Move a drive, change a machine, hand off to a colleague — the transcript travels with the media. Any machine that has the file has the transcript.
Assign speaker labels by right-click. Labels appear inline in the Script tab and colour-coded in the Rushes browser. Automatic diarisation is on the roadmap for v2.
Toggle the timecode on and off - useful for finding the moment in the rushes if you need to check how it really sounds!
Find any word or phrase across all transcribed clips instantly. Click a result to jump directly to that moment in the Rushes browser.
Every Apply to Timeline operation creates a snapshot of the previous timeline state. Step back through your edit history at any point.
Export your Script as a formatted Word document — speaker labels, scene headers, VO notes, timecodes, and all. The handoff document you need to manage the cut as it evolves beyond the sync pass.
John: Hello, how are you today?The sync pass produces a timeline. It should produce a document too — one that stays in sync with the edit rather than being maintained by hand across every version.
Whether you're doing the sync pull yourself, or your editor is working "Stream of Consciousness" - someone has to update the script. The edit moves on, but the document is constantly wrong. Keeping an edit script current is time-consuming manual work that scales badly across a long cut.
The Script tab always reflects the current Resolve timeline. Speaker labels, scene headers, VO notes, and timecodes are all inline. When the sync pass is complete, one click exports a formatted .docx — the document to take forward as the cut evolves into full picture editing.
As the editor works through the sync material, they add VO rows (voice-over copy or production notes), scene headers to divide the structure, and beat markers for pacing. These aren't notes about the edit — they're part of the edit document. By the time the sync pass is done, the basic script is already written.
When music, GVs, and coverage begin — when the edit moves beyond the sync pass — SyncPass steps back and Resolve takes over. At that point, theer is a complete, structured Word document to manage manually through the rest of post. Not a transcript. Not a rough timeline printout. An edit script.
Every other tool treats words as navigation aids. SyncPass treats them as the edit itself.
In every other transcript tool, words are labels on clips. You find a word, you find the clip, you add the clip. In SyncPass, words are the clips. Moving a word moves the media it represents. There is no translation step. There is no gap between the thinking and the timeline.
Resolve's own transcript data lives inside the project file. Move a drive, change a machine, hand off to a colleague — the transcript stays behind. SyncPass sidecars live next to the media file with the same name. They follow the media everywhere.
SyncPass doesn't try to be an NLE. It works with Resolve's own infrastructure — media pool, timeline tracks, audio channels — and hands control back to Resolve the moment the editor wants it. An editor who uses SyncPass still works in Resolve.
SyncPass is two things in one: a text-based editing tool that drives the timeline, and a script generator that produces the document your Edit Producer needs. Most editors build the edit and then document it separately — or don't document it at all. SyncPass makes the document a byproduct of the edit, not extra work after it.
SyncPass knows when a word starts more reliably than when it ends. It cuts where the next word begins, not where the current word ends. The result is consistently cleaner cuts.
SyncPass was built by an editor, for editors and the Edit Producers they work with. The design question at every step was the same: what part of this process requires creative judgment, and what part is just mechanical labour?
The sync pass produces a timeline. It should also produce a script — a living document the Edit Producer can take forward as the cut evolves, updated automatically from the edit rather than maintained by hand.
SyncPass is a DaVinci Resolve Python extension. No cloud infrastructure, no subscription, no account required.
SyncPass v1.0 is built for one stage of the documentary process: the sync pass. Before B-roll. Before music. Before colour. If you're in that stage, it does everything you need. Once the cut moves beyond it, you export your script and hand back to Resolve. A tightly scoped tool is a tool that works reliably.
No. Transcription runs entirely on your machine using Whisper, which runs offline after the initial model download (roughly 140MB for the base model). No audio, no video, and no transcript is ever sent anywhere. The only exception is the optional AI Automate feature — an explicit export action that you initiate.
Very good for English. Whisper's base model handles accented English well and produces word-level timestamps accurate to within approximately 2 frames. It's forced to English by default to prevent misidentification on regional accents (including Scottish English). The small and medium models improve accuracy on technical vocabulary at significant speed cost.
On a typical Windows workstation using the base model on CPU, approximately 5 minutes per hour of audio. Transcription is a one-time operation per clip — the sidecar is checked before processing and skipped if it already exists. GPU acceleration via CUDA can significantly reduce this time.
Any version of DaVinci Resolve with the Python scripting API enabled. The free version of Resolve includes the scripting API. SyncPass runs from Workspace > Scripts in the Edit menu.
SyncPass is designed for the sync pass — the stage before B-roll, music, colour work, or effects enter the picture. While you're working with sync sound and building story structure from words, it's the right tool. The moment you start adding coverage, laying music, or making L and J cuts, that's your cue to export the edit script and hand back to Resolve. From that point, SyncPass steps back and Resolve takes over. Non-destructive apply — which would preserve colour grades and audio levels across versions — is planned for a future release.
Yes — SyncPass has been tested with NAS-mounted media including standard Windows drive mappings (e.g. Y:\). The sidecar file is written next to the media file wherever it lives.
v1.0 is Windows-first. Mac OS and Linux versions are in active development — the plan is to package SyncPass for all major platforms once the Windows version is stable and tested. If you're on Mac or Linux, get in touch and we'll let you know when your platform is ready.
Free 30-day beta trial. Download the installer and be up and running in minutes.
Copyright © 2026 John Steventon / JKL Editing · All rights reserved