FCP XML to Nuke v1.5

This location is for Registered Users Only.
Perhaps you need to login or register.
Contributor: Jed Smith
Website: jedypod.com
Processes an FCP XML file from FCP 7 or Premiere Pro into a Nuke Script for each clip in the timeline.
6.0, 6.1, 6.2, 6.3 or later
Linux, Mac
21 Aug 2012

This script takes a Final Cut XML file with a single flattened video track, and builds Nuke scripts for each clip in the timeline.It is intended as a simple way to automate workflows between FCP/Premiere and Nuke. It creates a Nuke script with global first and last frame set, a frameRange node with the proper framerange, and a Write node set to the output path. There is an option for creating subdirectories for every Nuke script created. Handles are also an option. It can parse reel number and clip number from Red and Alexa footage, or can use the clip filename as the base naming for the output files.

This script was somewhat inspired by compflows.blogspot.com, but has been written from scratch and is a bit more flexible (although it only goes from XML->NukeScripts and not back). This has only been tested on OSX, but in theory should be cross-platform compatible. Comments and suggestions are welcome!

v1.5 - Added render format selection, to allow the user to set what format the created write nodes are set to. Currently the choices are Prores4444, EXR, JPG (0.9 422), and DPX.  Rendering from Nuke in Prores 422HQ is not reccomended due to color shifts introduced by Nuke's YUV->RGB color transform. When Prores4444 is selected, the framerate is set to the clip framerate for the current clip.
v1.4 - Fixed a bug handling XMLs with multiple sequences.
v1.3 -  Made support for Premiere FCPXML format more robust. Premiere FCP XML stores all sequences in the project, whereasFinal Cut Pro's XML format stores only a single sequence. I added a box that lets you choose what sequence of the Premiere XML file to process, and it should work more reliably now. Added support for transfer of linear TimeRemaps, Translates, Scales, and Rotates into Nuke. Also transfers framerate for each clip, and many other improvements.
v1.0 - Initial release.

Here is a quick (6min) video demonstration of how it works:

FCP XML to Nuke Script Explanation from Jed Smith on Vimeo.

Add something like this to your menu.py to add the script to your toolbar:

import fcpxml_to_nuke
nuke.toolbar('Nodes').addMenu('Scripts').addCommand('FCP XML to Nuke', 'fcpxml_to_nuke.process_xml()')
This is also available on PasteBin
This software is provided with no guarantee of functionality, no warranty, and no support. I am not responsible if it breaks your computer or deletes your files. However, you are free to use it for anything, share it with anyone, and modify it however you wish. Have fun!
Please login in order to download these files.


+2 # Michael Todd 2012-05-31 07:56
this is awesome and exactly what I need right now . I wanted to ask though if it was possible and not too difficult to have it check the XML for speed changes, zooms, pans and flip-flops and create nodes accordingly ?
0 # William Eguienta 2012-06-20 04:16
Thanks so much, I've try to make that but unsuccessfull, awesome ! thanks again
0 # Daniel Miller 2012-08-20 06:34
Thanks for this, I can see this saving us a lot of time from or current workflow, I've been adapting it to our file-structure. Would it be possible for the write to get it's frame rate from the original FCP sequence rather than just 23.976? Cheers, Daniel
0 # Jed Smith 2012-08-20 16:50
I just updated the script to a new version which correctly sets the framerate attribute of quicktime export in write nodes. (Sorry about that oversite). I also added a feature to select from a few common Write node compression types. Hope this helps!
0 # Daniel Miller 2012-08-21 02:38
Wow talk about great service! I've bought products which didn't have that kind of responsiveness from the developers. Really cool stuff.
0 # Dmitry Kornilov 2013-01-03 02:43
Can you rewrite a script for windows?
+1 # kishan kumar 2014-04-27 02:50
pls send nuke to fcp xml link........

pls anyone help me..
0 # Matt Richardson 2014-08-07 12:33
Thanks Jed,
A very nice tool.

we use premier to edit playblasts of 3D shots, before we progress them down the 3D & comp pipeline. So i had to make some changes for it to work for our setup.

Some of the changes are:
_Enabled it to handle any image sequences (instead of movies) that are used in the edit.
_preserve the frame sequences in the individual Nuke shots (so if the original image sequence used in the edit is 0200-1200, the nuke script starts at frame 200 and goes to 1200, NOT 0-1000)
_rebuilt the edit using precomp nodes that look at the individual shot nuke scripts, and works with my custom writer and versioning notes system. So you can easily version up and version down to see the latest version of a shot in context of the edit, and read any notes that correspond to that shot.

I will make a demo video at some point showing how it all works together, but thanks for your staring point!

at some point I will add the functionality to update an edit using existing shots - but that's for another day!
0 # Michael McReynolds 2014-11-26 21:47
import fcpxml_to_nuke
nuke.toolbar('Nodes').addMenu('Scripts').addCommand('FCP XML to Nuke', 'fcpxml_to_nuke.process_xml()')

Isn't working for me. Says "no module named fcpxml_to_nuke"
But the script is in the same place as all my other scripts and they import fine.
0 # Matthew Ingram 2014-12-01 19:32
This one for the simpletons like myself:

put .py file here


add this text - without ""

"import fcpxml_to_nuke
nuke.toolbar('Nodes').addMenu('Scripts').addCommand('FCP XML to Nuke', 'fcpxml_to_nuke.process_xml()')"

to this file in a text editor

0 # Matthew Ingram 2016-09-26 09:40
Quoting Matthew Ingram:
This one for the simpletons like myself

still working in 2016 and in windows
+2 # lucas puccino 2015-03-22 21:24
I have an error message when I try to import my .xml saying "list out of range" what does that mean ?
0 # Andrew Witkowski 2016-11-03 14:42
Quoting lucas puccino:
I have an error message when I try to import my .xml saying "list out of range" what does that mean ?

I know this is old but in case anyone else stumbles across this.. I think it's a bad XML. I had the same error exporting an XML from AE using XMLGibson script. When I exported an XML from Premiere, the nuke script worked perfectly. Upon further research, XMLGibson states that the XML it creates requires "further processing" to be read into certain software.

So maybe if you receive this error, it is due to the XML creation for some reason.
0 # Peter Timberlake 2016-08-21 07:49
luv this
0 # goodis t 2017-11-28 22:42
Doesn't work anymore.

You have no rights to post comments

We have 2377 guests and 53 members online