When Apple transitioned its Final Cut Pro product family from Final Cut Studio to Final Cut Pro X, Motion 5, and Compressor 4, it lost a number of features that editors really liked. Some of these “missing” features show up as consistent and reoccurring requests on various wish lists. One of the most popular is the roundtrip function that sent Final Cut Pro “classic” timelines over to Motion for further compositing. To many, it seemed like Motion had become relegated to being a fancy development tool for FCPX plug-ins, rather than what it is – a powerful, GPU-enabled compositor.
At last, that workflow hole has been plugged, thanks to Automatic Duck. Last year the father/son development team brought us a way to go from Final Cut Pro X to Adobe’s After Effects by way of the Automatic Duck Ximport AE bridge. This week at the FCP Exchange Workshop in Las Vegas, Wes Plate reveals the new Automatic Duck Xsend Motion. This tool leverages the power of the FCPX’s version of XML to move data from one application to the other. Thanks to FCPXML, it provides a bridge to send FCPX timelines, clips, or sections of timelines over to Motion 5.
Xsend Motion reads FCPXML exports or is able to process projects directly from the Final Cut Pro X Share menu. The Xsend menu enables a number of settings options, including whether to bring clips into Motion as individual clips or as what Automatic Duck has dubbed as “lanes”. When clips are left individual, then each clip is assigned a layer in Motion for a composition made up of a series of cascading layers. If you opt for lanes, then the Motion layers stay grouped in a similar representation to the FCPX project timeline. This way primary and secondary storylines and connected clips are properly configured. Xsend also interprets compound clips.
Automatic Duck is striving to correctly interpret all of the FCPX characteristics, including frame sizes, rates, cropping, and more. Since Final Cut Pro X and Motion 5 are essentially built upon the same engine, the translation will correctly interpret most built-in effects. However, it may or may not interpret custom Motion templates that individual users have created. In addition, they plan on being able to properly translate many of the effects in the FxFactory portfolio, which typically install into both FCPX and Motion.
While Xsend Motion and Ximport AE are primarily one-way trips, there is a mechanism to send the finished result back to Final Cut Pro X from Motion 5. The first and most obvious is simply to render the Motion composition as a flattened QuickTime movie and import that back into FCPX as new media. However, you can also publish the Motion composition as an FCPX Generator. This would then show up in the Generators portion of the Effects Palette as a custom generator effect.
Automatic Duck Xsend Motion will be officially released later this year. The price hasn’t been announced yet. Current Automatic Duck products (Automatic Duck Ximport AE and Automatic Duck Media Copy) are available through Red Giant.
©2016 Oliver Peters