Match the file to the receiving department
A colorist may request a Resolve marker file, an assistant editor may need Avid locators, an audio team may need a Pro Tools EDL or Pro Tools Marker AAF, and a subtitle workflow may need SRT. The best format depends on the receiving application and the specific import path that facility uses.
MarkerBuddy keeps those choices explicit by grouping format cards into three purposes: Reports & data, Editorial interchange, and Publishing & backup. DaVinci Resolve exports appear in the relevant report or editorial group. Every card explains its output before the one-click Export action, and recurring configurations can be saved as presets. Always run a small test with the receiving system before a critical turnover.
Supported handoff choices
MarkerBuddy exports all 21 choices in its catalog: CSV, Standard Marker CSV, Standard Marker TSV, Plain Text Marker Table, Excel 97–2004 Workbook, PDF report, Premiere XML, FCPXML, OpenTimelineIO, OTRN, Avid Media Composer XML, Avid Locators TXT, Avid SubCap TXT, Pro Tools EDL, Pro Tools Marker AAF, Resolve EDL, Resolve Marker Report CSV, Resolve Python Script, YouTube Chapters TXT, Subtitles SRT, and a MarkerBuddy session snapshot.
Selected markers export by themselves. With no selection, the export uses the currently visible marker set after filters, which is useful for department-specific turnovers.
Know what a marker handoff is not
Marker exports transfer marker information, not an entire conform. They do not replace picture, audio, media, project, or color-management turnovers. MarkerBuddy does not create native PTX sessions; its Pro Tools choices are Pro Tools EDL and the export-only Pro Tools Marker AAF for an existing session.
Applications differ in which marker fields and ranged behaviors they accept. Verify the receiving application and frame rate rather than assuming every field will round-trip identically.
Add the AAF markers to an existing Pro Tools session
Pro Tools Marker AAF is export-only and standalone. MarkerBuddy creates it locally without Pro Tools, PTSL, or a companion app on the export computer. It uses the active sequence's frame rate, display start, and drop-frame setting.
The file contains markers and timecode but no audio or video media, so importing it leaves the destination Pro Tools session's sample rate unchanged.
-
01
Open Session Data import
In Pro Tools, choose File → Import → Session Data and select the AAF.
-
02
Do not import a track
On the Tracks tab, choose Clear All.
-
03
Map the marker ruler
On the Marker Rulers tab, map Markers to Markers.
-
04
Choose timecode mapping
Select the timecode mapping required for the destination session, finish the import, and verify the marker times.
Range markers become points at their start. Characters the Pro Tools importer cannot read, including emoji, are replaced with ?.
Workflow
A practical four-step process
-
01
Ask for the destination format
Confirm the application, version, import command, frame rate, and whether point or ranged markers are expected.
-
02
Prepare the marker set
Filter or select only the markers the receiving department needs.
-
03
Choose the matching export
Use the dedicated Resolve, Avid, FCPXML, Pro Tools EDL, Pro Tools Marker AAF, SRT, XML, or report option.
-
04
Test before turnover
Import a small sample in the receiving application and verify timing, text, colors, and ranges.
Good fit
Use this workflow for
- Color turnovers to DaVinci Resolve
- Editorial handoffs to Avid Media Composer or Final Cut Pro
- Pro Tools EDL lists or marker-only AAF handoffs for existing Pro Tools sessions
- Subtitle, chapter, spreadsheet, and archive deliveries
Important limit
What this workflow does not assume
MarkerBuddy does not write PTX sessions and does not replace a complete sequence or media conform. Pro Tools Marker AAF is a marker and timecode handoff, not an audio or video turnover. Destination applications may support different marker fields, colors, durations, or timebases.