This is the last in our series of MediaStorm producers responding to the new FCP X. If you missed them, you can check out Eric Maierson’s thoughts here, and Tim McLaughlin’s here.
FCP X, it was good while it lasted.
After working in FCP X for a week, I left on a Friday buoyed by the speed and efficiency at which the program runs. I had blazed through a weeks worth of work in just three days.
But on Monday morning, my work was gone.
I spent an hour on the phone with Apple. They asked me to run some tests. Several times I opened the project, made some changes, and closed it. Each time I reopened the file, it behaved differently.
Think Memento.
Sometimes the program “remembered” the changes correctly. Other times it reverted to a previously saved version. Other times it combined two previously saved versions to create a third!
The consultant on the phone sent my file to the engineers. He said they would analyze it and send me the prognosis in 48 hours. It’s over a week later, and I still haven’t heard back.
I’ve returned to FCP 7, but I can share my insights from a week of working with FCP X.
The Good
- It’s speedy. I definitely noticed the difference in response time when I returned to FCP 7
- Using keywords is a fast and easy way to organize your footage
The Bad
- Synching more than two cameras using synching doesn’t work (I tried to synch three cameras with no luck. I also combined two cameras into a compound clip, and attempted to synch the third camera to this clip. Still, no luck)
- FCP X crashes when editing multiple formats
- Skimming is annoying when you don’t need it, and I didn’t find it very helpful when scanning for sound bites. You can, of course, just turn it off, but it would be great if you could actually use it to scan for bites.
And the Ugly
- Being able to save your work is 101.
I believe it’s too early to predict the future, but after my experience I do not recommend using the program right now.
In summary: as much as we all really wanted to love FCP X, it’s not usable for us in its current iteration. We’ve all reverted back to FCP 7 for now. We’re hoping that updates will make the program work for us in the not-too-distant future, but we’re also starting to look at other possible solutions should we need to make a switch. Right now, it’s really too early to make a decision.
We’d love to hear thoughts and impressions from all of you – are you making the switch, or sticking with FCP 7, or switching to an entirely new system? Let us know in the comments.
8 Comments
Based on everything I’ve read, I’m surprised you don’t give Premiere Pro CS5.5 a go. It appears to import FCP XML project files without issue and one can go about editing as before with minor adaptation.
Being a native 64bit app, along with other improvements would seem to be a no brainer for anyone editing on a MAC.
Just an observation.
Went to PP5.5 after 10 years of FCP. Do not regret a thing.
I agree. Just started working at a place that mostly does PC editing workflows. They have two macs. I was on the FCP system. I just on the off chance tried to import my FCP project into premiere… It worked flawlessly. Including moving text editor files into premiere.
I haven’t used adobes editing software in about ten years ever since I mad the switch from building my own pcs to buying powerful macs. I loved the switch.
Now, someone point me in the dirction of a FCP keyboard layout for premiere. I want the file. I don’t want to have to edit it. Help!!!!!
Funny, I am running FCPX in 4 different production machine and haven’t seen any issued like you share.
Why not use Premier? Because FCPX will kick Premier butt once it mature.
I like it so far for the reasons you mentionned. I have not experienced crashes or lost of unsaved work … Yet. Since i have red a couple Times that it happened, i guess i Will experience it sooner or later, but for now I go on with using FCPX.
Important to note though, if I had to produce from an assignment or a contract, I would still use FCP 7. I am willing to take chances on my own production but not on a client’s job.
Actually your experience is exactly what someone would expect from a version 1.0…. which is what FCPX is… the beta version was called iMovie.
Love editing in FCPX but then one day my clips just went offline for no reason. Nothing I could do would bring them back. Think of FCPX as a prototype for a new editing paradigm, play with it learn it – but don’t depend on it for anything for at least another couple of versions.
Nice to read your thoughts on FCPX Jennifer.
I have pretty much had the exact same experience. The program keeps crashing on me and loosing files… ?
I wouldn’t rely on FCPX in its current state. I am heading back to FCP7 as well + thinking about making the switch to Adobe Premier.
In i FCPX really like the new tagging system, the background rendering and the keyboard shortcuts in .. but I find the audio skimming very annoying along with the magnetic timeline and all the Imovie-look-alike-tools for newbies.
It is very sad for FCP… and for all who relied on this program.