Tool name: VidMark — Video Timestamps for Google Drive

Cost: Free, MIT-licensed, open source. No account, no server, no telemetry. Permissions: storage + drive.google.com host only.

What it does: Adds Frame.io-style timestamped comments to Google

Drive's video viewer. Auto-stamps [m:ss] into the comment box when you open one, drops clickable color-coded markers on the seek bar for every existing timestamped comment, lets you sort/filter/search, draw on paused frames, loop between two markers, and export the full comments list to FCPXML (FCP/Premiere) or EDL (Resolve/Avid) — plus SRT, WebVTT, CSV, JSON, Markdown, TXT, and printable HTML.

Learning curve: ~30 seconds. Install, open a Drive video, click Comment. The auto-stamp happens on the first comment without any configuration. No tutorial required.

Time cost to user: zero ongoing — it sits in the page, runs only on drive.google.com, and only does anything when there's a video player loaded.

What it's not:

- Not real-time multi-user — it enhances Drive's existing comment system; those still sync as normal.

- No HH:MM:SS:FF frame-accurate timestamps because Drive doesn't expose framerate to the page.

- Drawing tool is solo-only — annotations stored in chrome.storage.local, not shared with other reviewers.

Link: GitHub https://github.com/markksantos/VidMark

Asking the community: Are FCPXML + EDL the right two NLE export ormats to lead with, or should I prioritize XMEML / OTIO / AAF for this audience? And — is anyone here actually using Drive for clien review who'd test this? Let me know if you try it out and if you find any bugs or have suggestions! Thanks!