ben treston

Final Cut Pro X Furore

Final-Cut-Pro-X-Furore

Now that the dust has settled a little on the launch of Apple’s Final Cut Pro X - it’s time to take stock of the situation with a clear head.

Why the outrage?

When Apple first debuted the preview of FCPX at NAB this year, editors went wild for the speed and features demonstrated - now there is a significant amount of pro users who are saying they will jump ship and move to Avid or even Premiere.

The cause of this anger appears to be focused on a few key facts -
  • You cannot open projects from Final Cut Pro 7 (or earlier) in FCP X
  • You cannot export OMF/EDL/XML from FCP X
  • Multicam-editing support is not present

I believe a lot of the frustration here would have been avoided if Apple simply came out and said this when previewed. Of course people would have been upset, but at least they would not find this out at launch and then witness the rather surprising backlash that occurred.

Final Cut Pro X is a fundamental re-write and re-think of media management, non-linear editing and full use of all the core technologies in OS X - I am not surprised that there were going to be a few bumps on the way, perhaps the surprise is how loud and public they have been.

No professional editor would ever adopt a brand new piece of software mid project, so at the moment the prudent idea would be to assess the software and see if it is worth getting on board in future. No one is being forced to upgrade on day one. As much as people might disagree, Apple does listen to user feedback - so until some feedback has been gathered, the direction of FCP X is not known yet.

The biggest showstopper in our current workflow is the lack of support for working from AFP shared storage - which is how we share a RAID array. Not sure if this is going to be addressed, however this may require a re-think of our media managment in future for this to work.

So now, the waiting and wondering for the first software update begins - let’s hope sooner rather than later.