Re: Email Exchange with Randy Ubillos, FCP X Designer

[Eric Susch] "Businesses can't just jump off a cliff with no connection to the past. They need to do their work the way the client wants, and many times that means building on what they've done with the client before. "

I have no idea what sort of work you do, but in our operation each project is essentially self-contained, or if there are elements shared between projects for a given client, they've things like stock media and motion graphics files that could easily be imported into FCP X. I'm just not seeing how the capability to move a specific sequence to FCP X is really critical for migration. Sure, it would speed migration up if FCP X could flawlessly open every FCP 7 project, because you could just switch immediately. But in the absence of perfect import (which would probably be nearly impossible with a whole new rendering engine, etc. even without the new timeline features), continuing to work on projects originated in FCP 7 in FCP 7 was always going to be the only sensible choice.

For most users, I think, if they just start creating all of their new projects in FCP X (once Apple fills a couple of feature gaps), 12 months later they'll probably be opening FCP 7 all of once a month.

--
Digital Workflow/Colorist, Nice Dissolve.

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