Earlier today, Apple launched the much anticipated Final Cut Pro X (FCP X) to the Mac App Store. Originally described as a "dramatic and ambitious" change, it represents a complete rewrite and reimagining of Final Cut Pro, leading to some apprehension amongst professionals.
Since the initial release, several walkthroughs and impressions have been posted across the web and on our forums. Like the App Store ratings (shown above), the response has been mixed.
Philip Hodgetts provides an extensive blog post in question and answer form about what is and isn't included in Final Cut Pro X. He specifically reveals upcoming features that Apple has told him are coming. These include:
• "Multicam will come in a future release, when Apple decide[s] how best to implement it within the new application and architecture."
• "As of Version 1 and today’s release there is no direct import capability for [Final Cut Pro 6/7] projects. My understanding is that there will be an Apple-provided utility for importing XML from older projects to Final Cut Pro X."
• "the Apple folk made it abundantly clear that the ecosystem was very important to them, and that there will be a new, and much improved, replacement for the current XML workflow."
Larry Jordan who has been frequently quoted for his early comments about the Final Cut Pro X also weighs in. Jordan points out several of the improvements and disadvantages of the new system. He also points out that Apple is planning a quicker upgrade cycle for Final Cut Pro than they have in the past now that its in the App Store:
In the past, Apple used a 18 month, or so, cycle between updates. Now, Apple is telling me they are hoping to do an update once or twice a year.
Ultimately, despite the limitations, he expects that within the next 18 months practically all Final Cut customers will be running Final Cut Pro X due to the overall improvements.
Top Rated Comments
I strongly disagree. I think the strongest negatives are coming from editors like myself who use FCP7 EVERY SINGE DAY!! Consumers can welcome this product with open arms, because it was built for them. However, the current version is not of use to editors, in terms of their workflows and deliverables. Those who use FCP and gave a positive review are optimists. They probably even acknowledge all its faults. I commend their loyalty.
I'm sure you now have to had purchased the app to rate it.
I think now is a good time for FCP vets to start learning the new paradigms in preparation for when it reaches an acceptable level of maturity, and now is also obviously good for newcomers to the FCP fold to start learning their chops, but anybody who is either denouncing this as a write-off or claiming it to be the best thing ever when it's just 24 hrs old is probably jumping the gun somewhat.