FCP XML to Nuke v1.5
This location is for Registered Users Only.
Perhaps you need to login or register.
6.0, 6.1, 6.2, 6.3 or later
Linux, Mac
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
Comments
pls anyone help me..
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!
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.
put .py file here
/Applications/Nuke8.0v6/Nuke8.0v6.app/Contents/MacOS/plugins/fcpxml_to_nuke.py
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
/Applications/Nuke8.0v6/Nuke8.0v6.app/Contents/MacOS/plugins/menu.py
still working in 2016 and in windows
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.
RSS feed for comments to this post