Re: Email Exchange with Randy Ubillos, FCP X Designer

[Michael Pierro] "Yeah, but working in a company that does a lot of broadcast and has for years, I've had to open up older projects, from FCP 6 or 5. Being able to do that is critical. I may not use that feature everyday, but being able to do that has been essential. The fact that I wouldn't be able to now is a huge deal breaker."

But this is alleviated by being able to install FCP X side-by-side with FCP 7.

[Michael Pierro] "Obviously if I had FCPx I would start new projects on it, but that doesn't alleviate the need for legacy compatibility. Say whatever you want about the lack there of, but frankly it seems pretty obvious to me, as I'm sure to a lot of people here, the people who created FCPx MUST HAVE INTENTIONALLY left out the functions that would make this app useful to any pro user. The things that are missing are just too blatantly obvious to just leave out..."

See my post here. The importing issue is not straightforward.

And I agree that certain features were deliberately left out... of the first release. I don't agree that this implies Apple isn't working on these things or doesn't recognize that some people need them. It makes a great deal of sense to structure releases to focus on mainstream features first, then start selling a product suitable for most users while you continue working on features for the higher end segment of the market.

--
Digital Workflow/Colorist, Nice Dissolve.

You should follow me on Twitter here. Or read our blog.