ClipExporter is an important tool for VFX workflows in the FCP X eco-system. ![]() So ClipExporter did not evolve (on the base of voluntary supporters) and this was sad. I was hoping for developers to join the open source development and help ClipExporter to grow, but no one was interested. To implement them would have meant a big time investment, which I could not afford. Users sent me feature requests that I had to deny because I didn’t use these specific features in my own work.Why I rewrote ClipExporter and made it commercial (again)? Also the support for export of trimmed, native RED files that opens the app to a new user base. This is something that I was missing in my own workflows. For example the linked mode, which rebuilds some kind of "consolidated" timeline in After Effects using the exported and trimmed video files. It took several months to rewrite it and I am excited about some features. ![]() I am happy to announce that ClipExporter 2 is available in the App Store. Thomas explains in these videos and in the text below: Things have moved on and Thomas wanted to update ClipExporter, after all it was a tool he designed to make his life easier! So we welcome back a completely rewritten ClipExporter 2.0. Keeping the app updated to match Apple's mutating XML and providing support was too time consuming. It then got removed from the app store and the source code was made public. You might recall that ClipExporter started life as small $16 application for taking a clip from FCPX into a third party application. There is 19% off until the 23rd of November bringing the price down to $89.99. Monday morning and we are pleased to announce that ClipExporter 2 is available to download for $109.99. Thomas Szabo wrote to us last week indicating that his ClipExporter software had been updated and was about to go back onto the MAS. Let me know what detail I've inevitably forgotten to include.Want to export a section from a clip (or clips) out of FCPX for use in another application? ClipExporter 2 is now live, new features and it's back on the Mac App Store. I'm not sure that any of this would be relevant but: ![]() I'm exporting to prores 422 (w the default settings, not HQ or LT) because it matches the transcoded footage from the fcpx project and when possible or if there's no upside I'd like to keep the file sizes down. I've never been an Adobe wiz so there may be a codec setting I'm missing when I render/export. To test if I was just getting bad exports from AE I exported one of the clips with no effects applied and the result looked just like the original noisy footage w/o the blotchy artifacting. I am planning on relinking my fcpx project to the newly denoised clips if I can manage to get the clips to look right. After denoising the individual clips in AE I'm exporting them to prores 422. I used clipexporter (a lifesaver) to open my fcpx project in AE. ![]() It's dslr footage that was originally h.264 and was transcoded to prores 422. The footage is lit in an expressionist manner so there's a lot of that and as a result the skin tones can look posterized. It looks more like big blotchy, chunky artifacting then standard video noise. However when I export the clips I get some pretty serious artifacting in the regions that go from light to dark. I'm getting truly impressive results in the ram preview.
0 Comments
Leave a Reply. |