Compatibility with other NLE systems
Reeltime Pro exports editing data as Final Cut Pro XML (.fcpxml). While the tightest integration is achieved with Final Cut Pro, the XML can also be used with other non-linear editing (NLE) systems. Depending on the target application, there are some limitations regarding metadata, timelines, and monitoring workflows.
DaVinci Resolve#
- Supports .fcpxml import natively
- Does not import keywords, markers, or most metadata
- Auto-generated timelines can be used, including multicam editing
Monitoring:
- No native NDI output support
- Third-party tools such as FlowCaster or Nobe Display may provide a workaround
- Alternatively, use an SDI output device (e.g. Blackmagic UltraStudio Monitor 3G) to route the timeline signal back into Reeltime via a video I/O device
Adobe Premiere Pro#
- Does not support .fcpxml directly (Final Cut Pro 7 XML only)
- Requires conversion using third-party tools such as XtoCC
After conversion:
- Range-based metadata and annotations transfer into the bin structure
- Multi-track timeline is preserved (one track per camera angle)
- Multicam timeline is not supported
Monitoring:
- Native NDI output support available
Avid Media Composer#
- Does not support Final Cut Pro XML import
- Requires a conversion workflow:
- Import .fcpxml into DaVinci Resolve or Adobe Premiere Pro
- Export an AAF file from there for use in Avid
Monitoring:
- Native NDI output support available
Summary#
Using .fcpxml export enables flexible handover to other editing systems, but may require conversion steps and comes with reduced metadata support depending on the target NLE. For the most complete workflow—including metadata, timelines, and seamless round-tripping—using Final Cut Pro is recommended.