With all the craziness of the Final Cut X going on, people threatening to switch NLE’s, wondering where to go and every blogger writing 10 articles about why FCPX is great or why it isn’t, I decided to take action. I didn’t want to write about it right away though. Cammon and I made our video about why you can’t use FCPX on a feature and that’s that.
Instead of talking about “what will we ever do to survive,” I decided to look for what answers there were. I thought back to the Media Composer 5 road show I attended in Burbank at KeyCode Media last summer and in my notes I wrote about Boris coming out with transfer software, similar to the infamous Automatic Duck. I don’t have Automatic Duck and I have looked into it before and for the type of projects I am doing lately, I just don’t have the budget for it. Especially because it is a one way street. So while you read this review, keep in mind I haven’t ever personally used Automatic Duck, I only know what it can do and know how it has performed for friends.
There are two great benefits I see immediately for editors who want to use Avid more in their workflows or want to keep aspects of FCP in their new Avid lives. I’ve successfully transferred a few Final Cut Pro projects into Avid using the Boris AAF export tool, even using AMA (ProRes only tested). I have also tested it with batch importing this clips. So there, I have moved a few clients archived projects they still like to pull from into the Avid, out of Final Cut.
