FCP X xml to nuke v1.3
This location is for Registered Users Only.
Perhaps you need to login or register.
Contributor: Thomas Szabo
This script reads a fcpxml-file in and outputs separate Nuke- and Syntheyes-files for each video that is in the Final Cut Pro X sequence. Use it as shell-script or Automator workflow.
Requirements:
6.3 or later
Mac
6.3 or later
Mac
14 Dec 2011
731
I´m missing the "export as quicktime reference" option in FCP X. Luckily Apple introduced the XML-export feature which gave me all data I needed to "reconstruct" a video-clip in a Read node. This (bash) shell script parses a fcpxml-file and generates Nuke .nk-files and Syntheyes .synInfo-files for every clip in the Final Cut Pro X sequence (project). Tested on Mac OS X 10.6.8.
Features
- No files are copied. The Read Nodes point to the same files as in FCP X.
- All in-/out-frames, sequence frame positions, clip durations stay intact
- Handle frames can be added to extend the frame range.
- Only video-files. No audio.
- Different FPS and dimensions were recognized.
- Cropping, Animations, Translations, Color Corrections, Effects and every other Final Cut related modification on a clip will be discarded!
- The generated Nuke-files are named after their FCP X name with a following "_v01"
- and more... see update notes below
Usage:
Please take a look at the contained readme-file.Update 1.1 changes:
- added an Automator-workflow file for easy right-click usage
- bugfix: when FCP-X Timeline starts with Timecode set to 00:00:00 the first clip was misplaced in time in Nuke.
- bugfix: the script failed when an empty space was found in the filename.
- notes: empty spaces in filenames will be replaced by a "_".
Update 1.2 changes:
- bugfix: decimal framerates were rounded to integer (23.98->23 changed to ->23.9760)
- added export option for generating syntheyes-infofiles. The provided synInfo.szl script is required for the import. See Notes Below.
- added serialization so all files have unique filenames starting with 001_.....nk
- the script now creates shot folders
- Notes: the generated .synInfo file is not an official Syntheyes file-format. Double-clicking it will not open Syntheyes. It´s just a plain text file that gets imported by the "synInfo.szl"-Importer and feeds Syntheyes with all needed data for a tracking session. You´ll have to save this shot as .sni file afterwards!
Update 1.3 changes:
- Nothing changed. Just reuploaded the file. I´ve mirrored the download on VFXTalk. See thread #16.
watch the Tutorial on vimeo
Thanks
A big THANKS to the Nuke-community for sharing knowledge, gizmos and scripts. I´m a silent forum-reader and Nukepedia-leecher. This is my tiny contribution and I hope this script helps someone.
HAVE FUN!
Please login in order to download these files.
Comments
In four steps:
1) In terminal and type:
sudo chmod 775
2) Before pressing enter, make sure you have a space after 775, and drag and drop the shell file into the Terminal window. NOW press enter.
3) You'll be prompted for your password. Go ahead and type it in, press enter when you're done.
thanks for the script. It does not seem to work with the "old" Final Cut pro 7, does it?
Even with the sudo chmod 775 permission change I can't get it to work. Or am I doing somthing wrong?
I found something similar for Final Cut Pro 7, but Its not released yet.
http://vimeo.com/25720019
Cheers
@Maetis: the FCPX and FCP7 xml-outputs are very different XML structures. In short: this script doesn´t work with prior versions of FCP - only FCPX XML-files will be processed. The vimeo-video is awesome. I saw it before. Philips work inspired me a lot for this script.
And add some screenshots to here. I gonna try it soon.
Unfortunately, I can't get it working when the clips were transcoded by FCP X itself. After each path, Terminal is prompting "${1%/*}/$clip_ name'_v01.nk': ambiguous redirect"
I think the problem comes from the way fcpx names the clips. Maybe the space or the parenthesis.
Am I the only one having this problem? Is there a way to fix this without renaming all the medias?
would you mind mailing me your fcpxml file which causes the error? thomas(at)mindtransplant.com.
I could not recreate the error.
Error when I unzip the file
Hope you like it! Please report if any bugs occur.
Would be nice to have just these clips exported which were marked.
Cause the Export seems to be very slow when converting a whole (3-minute) timeline.
I´ll contact Nukepedia to fix this problem.
cd ~/Desktop
unzip -j filename.zip
http://www.vfxtalk.com/threads/33883-Final-Cut-Pro-X-to-Nuke-script?p=162465#post162465
But the good news is that this script has grown up to an application. It is called ClipExporter for Final Cut Pro X. I worked on it the last 2 month and now it is available on the Mac App Store - but it´s not free anymore. This app is also capable to export your clips as Quicktime reference movie now so you can work with other post-production tools too. I use the app on my current project and I really like the FCP X-ClipExporter- Nuke workflow.
Please visit the ClipExporter website (http://clipexporter.mindtransplant.com/) for more infos.
Thomas
RSS feed for comments to this post