I’ve just finished an update to the public beta of the Conduit plugin for Final Cut Pro X and Motion 5. It’s still a free download.
If you’ve signed up for this beta previously, dvGarage will send you an email about the update. And if you haven’t got the beta yet, why not sign up at dvGarage’s site to see how much more Motion 5 and FCPX can do!
There’s an important change in this update. Briefly: the Conduit plugin now works in video colorspace again, rather than the linear light colorspace which became the default in Motion 5 + FCPX.
When I made the previous beta release at the end of June, nobody had much experience with FCP X yet. Using the default colorspace of the application seemed sensible at that time. However, it turns out that requesting video colorspace is a better match for how Conduit works in other applications (and also previous versions of the Final Cut Studio apps).
If you’ve got effect files created with the previous beta, you may find that their look has been altered by this change. Don’t worry, getting the effect working in linear colorspace again is very easy:
- Create a Video to Linear node and place it just after the Input node.
- Create a Linear to Video node and place it just before the Output.
- Connect your effect nodes so that they are between these newly created nodes.
That’s all. You may wonder if adding these conversion nodes has a performance impact… Thanks to Conduit’s node-fusing capabilities, the effect of adding the conversions is vanishingly small in most situations. For example, if you’re making a keyer or a color correction effect, the conversions will most likely be fused together in the same rendering pass with other nodes in the same effect.
Similarly, there is no adverse effect on image quality from the conversions, because both FCP X and Conduit use floating-point pixels.