Originally Posted by robogobo
The only mistake apple made was to discontinue support for fcp7. Bad idea. So if they bring that back, problem solved. Major redesigns and overhauls need time to iron out the kinks and get up to speed. Most pros don't adopt a new release until it's proven in the field. This is certainly true of major studios. The majority of people who are trying fcpx and complaining about it are semi pro and amateurs. That doesn't make the problems less significant, but this is how it always goes. Give it a few months and all will be fine in movie land.
Do you actually work in "movie land"? Do you understand that it's only semi pros and amateurs who finish projects alone, in one machine? Everyone else collaborates, using tools FCS had that don't exist in FCP X. Major studios, as you put it, will never use it. Not because it's bad, but because it's useless. It has no way to engage with anything else people are doing, and is therefore no use.
I'm amazed how many rank amateurs are offering advice to people who actually do this as their day job, regurgitating the line about how slack we are to expect to upgrade mid-project, and how unprofessional that is.
The real pros bought this, still own it, will try it on small projects as we did today (like making a DVD screener lol) but want to see a path forward that includes the stuff we've done over the past 12 years in FCP. Few jobs just begin, on day 0, and end neatly. There are many reasons to need backwards compatibility on projects, and only idiots see our work as being about starting and finishing "a movie" on one machine, as a self-contained exercise. In "movie land" that simply isn't how it works.
Any Avid editor can work with any Avid project ever made since 1992. Not always the media, but the edit, which has always lived as metadata (no, Apple didn't invent the term). Apple sees no need for that, and they're wrong. Wrong.