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…

With the major changes in Apple's new version of Final Cut Pro X, we've had a lot of people asking if MediaStorm is making the switch, and what we think of the program. This essay is the first in a series of MediaStorm producers responding to FCP X. Apple giveth and Apple taketh away. And with the release of Final Cut Pro X, Apple did a lot of both. Among the missing (at least for the moment): the ability to import FCP 7 projects. the ability to export only a portion of your project multicam support the auto-save vault And on and on.  To be fair, Apple recently promised to reintroduce absent functionality in future versions. It’s still painful to work with an incomplete toolset, particularly given that the toolset was doing pretty darn well just last week. Yes, FCP X is a 1.0 release but Apple is not new to this…