Turn Frame.io comments into Cubase markers
Drop a comment CSV, download MIDI .mid markers you import into Cubase — one named marker per comment. Free, no account needed.
Match your session's tempo so markers land in time.
The Frame.io video's rate — not your session or timeline's.
How it works
- 1
Export your comments from Frame.io
Open the file's comment list in Frame.io and choose Export comments → CSV.
- 2
Drop the CSV here
Preview every marker live. Frame rate is auto-detected, with manual override — then set your session tempo so the markers line up in Cubase.
- 3
Download your MIDI markers
A MIDI .mid with one named marker per comment. Set your Cubase project tempo to match, then import — the same file also works in Logic, Reaper, and Studio One.
Tryfree — skip the CSV entirely
Stop the export-convert-import shuffle. In Cuevue, clients leave comments right on the review link — then you push them to markers in one click. No Frame.io, no CSV, no conversion.
Frequently asked questions
In Frame.io, open the file's comment panel and choose Export comments → CSV. The converter reads the standard export columns — Commenter, Comment, Frame, Timecode — and turns each top-level comment into one marker. Replies are skipped so threads don't become duplicate markers.
Choose the MIDI markers (.mid) export format, set your Cubase project tempo to the session's BPM, and import the downloaded .mid. Each comment becomes one named marker on the marker track. Because MIDI marker positions are tempo-relative, matching the tempo is what makes them land at the right time.
MIDI has no absolute clock — positions are stored in beats, not seconds. The converter places each marker using the BPM you enter, so it must match your Cubase project tempo. If the markers are off by a consistent ratio, the tempo is the first thing to check. For a session with tempo changes, import the file's tempo track rather than a single BPM.
Yes — each comment becomes the marker's name. MIDI markers carry a single text string, so there's no separate comment field; the note you leave in Frame.io is exactly what shows on the marker in Cubase. Long notes are trimmed to keep the marker list readable, and the full text is always visible in the preview before you download.
23.976, 24, 25, 29.97 (including drop-frame), 30, 48, 50, 59.94, and 60 fps. Use the frame rate of the video you reviewed in Frame.io — not your Cubase project settings. It's auto-detected from the export, and the picker is only there for the rare case the CSV can't be read. The frame rate is how the converter reads each comment's timecode; the tempo is how it places the marker in Cubase.
Yes. The same MIDI markers (.mid) file imports into Logic Pro, Reaper, and Studio One — set the project tempo and import. There are dedicated converters at cuevue.io/tools/frameio-to-logic-markers and cuevue.io/tools/frameio-to-reaper-markers, and Pro Tools and video editors have their own pages too.
No. The file is converted in memory and discarded as soon as your .mid is returned. Nothing is written to storage, logged, or retained — client notes on unreleased work never stick around on our servers.
We make Cuevue, a review platform for audio and video teams where marker export is built into the review player. The standalone converter is free because the CSV shuffle is a pain we know well. No signup, no watermark, no catch.