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!…

This is the second in our series of MediaStorm producers responding to the new FCP X. If you missed the first response, from Eric Maierson, you can check that out here. Well it's amazing how much difference a day makes.  Yesterday I had prepared a blog post about my qualified, yet upbeat first impression of FCP X.  Of that blog post, here's what I'll include; "I've been working in FCP X since it launched, and I've tried to approach it for what it is. A new piece of software that will have significant limitations, like all version 1 software.  In doing this, I've come to see the potential of the program. It's a young buck, but as it matures, I think we're going to be surprised at how robust it is.  Using metadata to organize and find assets is amazing. It's fast and efficient. I've been able to organize content quicker than…