Copy of a thread I just started at DVinfo. net User:
Like so many, I bought FCP X on the day it was out, and trashed it after a couple of hours of experience. I tried to edit a theatre play on it, and got frustrated for multiple reasons.
I still think that 10.0.0 release was a terrible update-release for a professional program with such legacy.
I bought the Adobe Production Premium at a 50% discount, because their RED support is very good, I didn't know about the future of FCP and I didn't have a Photoshop license yet, so having their suite at such discount coulnd't hurt. I kept editing with FCP 7 in the meanwhile.
After the 10.0.3 update I got interested again, especially because of how powerful multicam was implemented.
So carefully, I began buying some tutorials again, reading articles, etc.
Last week, I got a job that needed a LOT of pictures to have an Ken Burns-like animation on them for bumpers on a congress.
Because I knew FCP 7 had a 4K picture limit, but especially because I knew FCP X had the automated Ken Burns effect (instead of putting manual keyframes everywhere), I thought it could be a good change to try out the program: small project.
I won't go into details, but my conclusion is:
I got frustrated a lot of times. I sent Apple feedback a couple of times. But I also got some very speedy workflows and exports. When I had to return to FCP 7 to put some filters that weren't compatible with FCP X yet on some finished videos, I really hated the render and export times, how fast FCP X felt.
The interface, the reaction, the background renders, the immediate render previews, the superfast exports, ...
I'm still not fond of how FCP X works with media management. I still think the program has to mature a lot, and there are a lot of weird choices. But if you really learn it, you can be very fast with it, and once you do... You will ALSO get very frustrated with how much better things work in FCP X instead of FCP 7, and not only the other way around.
Now I'm curious to learn more and more about the new program, and I'll see how and if I can implement it more and more in my professional workflow too.
This is a quote from the Crumblepop page: Why we’re betting everything on FCP X - CrumplePop BlogAs developers for FCP, we have a strong bias in favor of FCP’s continued success. That said, we had spent much of the year prior to FCP X’s release expecting that we might have to leave the platform. We were hearing the same rumors that everyone else was – that FCP X would be another iMovie, wouldn’t be pro, etc. – and we were ready to bail. Happily, we don’t have to. While there are obviously missing features (like a comprehensive redo of Compressor), the foundation of FCP X is extremely solid. FCP X, for the reasons listed above, is going to be what most professional editors use to edit. Maybe not tomorrow, but likely within a year
After working a couple of days on FCP X, the more I think there is a lot of truth in this.
But Apple botched the launch, and they will really need to do some extra effort to win some people back (including keeping adding features, listening to feedback, and getting more of the industry - and camera manufacturers) to support the program.
After all the trash that FCP X got, many for it deserved (and I was one of the critics, and in a way, I still am), I also thought it would be only fair to share my (rather good) experiences after editing with it for 4 days.