ClipExporter is a free workflow and export tool for Final Cut Pro X.
ClipExporter opens exported Final Cut Pro X projects (fcpxml) and exports each clip as a Quicktime (reference) movie, Nuke file or Syntheyes importable file. It also exports whole timelines (or just parts of it) to After Effects by translating all edits and many parameters. All clips can be extended by a certain number of handle frames. ClipExporter keeps your post-production workflow organized by creating a shot based folder structure with customizable subfolders.
- Export for After Effects. Translates complete projects to compositions. To find out more see the After Effects export section of the manual.
- Exports raw video clips as Quicktime reference or self-contained movies. These files can be opened in other applications like Mocha, Motion, PFTrack etc.
- Exports Nuke files. All in-/out-frames and timeline positions match your exported Final Cut Pro X project.
- Export for Syntheyes. A custom file format is created for import in Syntheyes. Therefore an importer sizzle-script is required, which can be downloaded >>here.
- Supports roles for selective export of a single clip or a group of clips.
- Adds handle frames (optionally). Extends each clip length by a given number of frames.
- Creates a shot based folder structure with naming conventions and custom subfolders.
- Sorts all generated files into predefined subfolders.
- Saves disc space by refering to the original source media. No files are copied.
- ClipExporter does not export timelines as a whole as Quicktime Reference movies (just like FCP 7 did)!
- r3d (Red) files are not supported for Quicktime export. ClipExporter utilizes QTKit which does not have native r3d support.
- Retimed clips are only supported for After Effects export. Please “unretime” all clips before export. ClipExporter warns you, if retimed clips were found in your project.
- Effects, translations, animations and every other Final Cut Pro X related modification on a clip will be discarded (Nuke and Quicktime only).
- Video-clips with unsupported or odd fps (frames per second) values could cause inaccurate timming results. We encountered such problems while using unconverted iPhone videos that were shot with the built-in camera app.
- Event-XMLs are not supported.