Originally Posted by digitalclips
It is a discussion that's been had over and over in AI.
Many multi-seat production houses were created to work around FCPro as it was and had input much into the development to suit there needs. Half of all US production was on FCPro (I have no idea what the current numbers are). As you said the EOL was dropped on these companies like a brick and they simply could not change even if X was better, it didn't fit in the work flow as was.
As I just said above maybe the parts lacking in X for these production houses could be added and a 'Studio Pro X' could be created out of X. Believe me, I am not a luddite, I have bled all the way on Macs from 1984 with arrows in my back and front keeping up with digital technology.
Two of the biggest issues, IMO, are:
1) The inability to open legacy FCP 7 projects in FCP X
I think Apple just dropped the ball and assumed that once a project is finished -- there's no need to access it again... Once editors finished their active FCP 7 projects, there would be no need to access them again -- therefore no requirement to Open or Migrate FCP 7 to FCP X.
2) The inability to pass content between FCP X and other apps, including FCP 7 (in both directions).
I think Apple did/does not have all the pieces in place to make FCP X as self-contained as it eventually will be. Obviously, an XML import/export was/is not complete -- so there was no way to exchange data among apps.
However, less than 3 months after FCP X release, they added fcpxml... not great, but a good start. This illustrates that Apple was working on XML import/export -- and was able to add it to the product in an amazingly short period of time (compared the FCP 1-7 updates). And, there is another FCP X XML flavor named axel. AFAICT, it is very robust and can handle all the things in FCP X -- orders of magnitude more robust than FCP 7 xml.
Apple has said there are some things that they do not want to implement, or want third parties to provide.
I suspect, that within the next 6-12 months we will see acceptable solutions to both the above issues -- likely fro mthird parties.
I think the way it will shake (maybe a bad choice of words for this topic) out is that the "pros" will begin to use FCP X more and more for what it does well: quick editing turn-around. And round trip to other apps for specialty processing.
In the video link I posted earlier...MacBreak Studio talks about audio editing and plugin problems in FCPX
These guys demonstrate how easy and fast it is to sync and edit multi cam and pure sound tracks (even though multi cam is not supported in FCP X)
1. Select: Audio, Camera A, Camera B...
2. Click Sync -- (based on audio) creates compound clip with a track for each camera and sound (synced ala PluralEyes)
3. Disable sound in video tracks
4. Edit/Disable portions of video tracks as desired to expose different camera shots
It is amazingly fast and simple -- compared to anything I've seen!