FCP X xml to nuke v1.3


 
This location is for Registered Users Only.
Perhaps you need to login or register.
Contributor: Thomas Szabo
Website: www.mindtransplant.com
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
14 Dec 2011
729

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:

  1. added an Automator-workflow file for easy right-click usage
  2. bugfix: when FCP-X Timeline starts with Timecode set to 00:00:00 the first clip was misplaced in time in Nuke.
  3. bugfix: the script failed when an empty space was found in the filename.
  4. notes: empty spaces in filenames will be replaced by a "_".

Update 1.2 changes:

  1. bugfix: decimal framerates were rounded to integer (23.98->23 changed to ->23.9760)
  2. added export option for generating syntheyes-infofiles. The provided synInfo.szl script is required for the import. See Notes Below.
  3. added serialization so all files have unique filenames starting with 001_.....nk
  4. the script now creates shot folders
  5. 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:

  1. 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   

 
0 # Zach Lewis 2011-09-29 11:35
Welp, this is awesome. Now I actually have a reason to use FCP X. Clever idea with the services, too. Thanks - I'll let you know when I break your script.
 
 
0 # Zach Lewis 2011-09-29 14:06
Wanted to note that you gotta change permissions on the shell file to get this to work.

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.
 
 
0 # Maetis B 2011-09-30 03:16
Hi,
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
 
 
0 # Thomas Szabo 2011-09-30 03:54
@Zach: I like FCP X and now that the xml-export is implemented, I like it even more and will try to fully integrate it into my project-workflo ws. Thanks for your note on the user-permission s. I knew I´ve forgotten something.

@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.
 
 
0 # Jay Sambuev 2011-11-14 02:21
Can you make a tutorial for Youtube?
And add some screenshots to here. I gonna try it soon.
 
 
0 # Philippe METRO 2011-11-14 20:52
Thank you Thomas. This is very useful.
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?
 
 
0 # Thomas Szabo 2011-11-15 01:36
I will make a tutorial the next days but first I try to figure out how to solve Philippe´s problem.
 
 
0 # Thomas Szabo 2011-11-17 06:05
@Philippe METRO:
would you mind mailing me your fcpxml file which causes the error? thomas(at)mindtransplant.com.
I could not recreate the error.
 
 
0 # Thomas Szabo 2011-11-18 16:04
updated to v1.1: bugs fixed, automator-workf low added, tutorial on vimeo. see description above.
 
 
0 # Jacob Nachtfaber 2011-11-19 12:40
Anyone else having problems unzipping the the latest update?
 
 
0 # julian van mil 2011-11-19 13:56
thanks for sharing this- awesome work
 
 
0 # Peter Meyer 2011-11-22 04:38
Can't unzip the file :-(
 
 
0 # Thomas Szabo 2011-11-22 06:04
I will upload a new version later today. Somehow the zip doesn´t work :sad:
 
 
0 # nick editor 2011-11-22 09:07
+1 :sad:

Error when I unzip the file :sad:
 
 
0 # Jacob Nachtfaber 2011-11-22 12:53
I managed to open it using a Terminal command in the end, but perhaps a less complicated method would be preferable. Nonetheless, many thanks Thomas. A lovely little script.
 
 
0 # Thomas Szabo 2011-11-22 13:01
Dear all, please hold on I´ve uploaded v1.2 with a new feature - but I´m waiting for 3 hours now for Nukepedia to confirm the upload. I´ll try to repeat the upload later.
 
 
0 # Thomas Szabo 2011-11-22 13:40
updated to v1.2: bug fixed. added file serialization. now exports .synInfo-File for Syntheyes too. shot folder creation.
Hope you like it! Please report if any bugs occur.
 
 
0 # Peter Meyer 2011-11-22 15:08
Decompression works now :-) Thank you.
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.
 
 
0 # Thomas Szabo 2011-11-22 23:38
@Peter: there´s no way to tell FCP X that it should export only selected clips. Therefore I recommend to use the new Roles-tag-featu re to label "VFX-Clips". This way it´s very easy to sort them out. Then select them, copy them and make a new Timeline which you only use for exporting clips. Paste the clips and export. There is no better workaround.
 
 
0 # Andrew Hake 2011-11-22 23:40
It will be pretty trivial to get this working as a droplet as well to have a simple drag and drop workflow. Would be glad to help as well.
 
 
0 # Rachel alset 2011-11-30 03:15
i can't open this file. A Decompression failed still appears everytime it downloads the file
 
 
0 # Thomas Szabo 2011-11-30 03:30
@Rachel: jep, the zip file is broken ... again :sad:
I´ll contact Nukepedia to fix this problem.
 
 
0 # Rachel alset 2011-11-30 03:33
I made it work by opening the zip file in terminal:

cd ~/Desktop
unzip -j filename.zip
 
 
0 # veda bft 2011-11-30 06:03
Download doesn't work... (ERRRO) can you help me, Plez.
 
 
0 # Thomas Szabo 2011-11-30 10:08
If the downloaded zip-file doesn´t work, try downloading from VFXTalk.
http://www.vfxtalk.com/threads/33883-Final-Cut-Pro-X-to-Nuke-script?p=162465#post162465
 
 
0 # Thomas Szabo 2011-11-30 10:12
No links allowed in comments? Ok, plan B: Goto VFXTalk.com and search for the thread "Final Cut Pro X to Nuke script". See post #16.
 
 
0 # veda bft 2011-12-06 08:39
THANKYOU
 
 
0 # Oleg Kuryshev 2011-12-14 00:17
Can't unzip "fcpxml_to_nuke _v1_2.zip". Redownloaded 3 times, renamed - still cannot.
 
 
0 # Thomas Szabo 2011-12-14 16:33
Unzip should work now. I´ve reuploaded the file.
 
 
0 # Thomas Szabo 2012-03-03 06:04
Hi all,I won´t develop this shell script any further.
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
 
 
0 # paul paul 2012-04-14 02:29
am using mac osx lion where should i install the .workflow
 
 
0 # Thomas Szabo 2012-04-16 09:14
@paul: with Lion the user library folder is hidden by default. Open Terminal and type: chflags nohidden ~/Library/. Your Library folder is unhidden now and you can install the .workflow file at "/Username/Libr ary/Services/".
 
 
0 # Edward Grayclaws 2018-01-03 12:13
not working with sierra is there an alternative to this?
 

You have no rights to post comments

We have 2398 guests and 122 members online