Clam Down...Apple says missing features coming soon.

No that's not true! Its very easy to go from 32->64 bit, in 9 out of 10 cases you just recompile; I have done lots of 32->64 bit converts back in 1996 for Alpha and it was mostly a piece of cake.

So I don't understand why they didn't do this.

You were extremely lucky then. Recompilation from 32 to 64 means different pointer size (you allocated 32bit field in a structure for it once? Too bad), different default integer sizes depending on compiler, STL's size_t suddenly becomes 64 bit, structure padding changes and all 32 bit third party plugins stop working. Almost forgot, ALL libraries you've relied upon must be 64 bit too. Believe me, I work on a gigantic (200MB of source code) library which is compiled on many different platforms, 32 and 64 bit and I know exactly what it is all about.

I think that it's funny that people are making the OS9 OSX comparison. Because it reminds me of when Windows released Vista which was an incomplete OS, then had to rush out windows 7, and now is trying to rush out Windows 8.

We keep hearing things like "We looking at adding multicam". Soooo, why did they release an incomplete product?

How much of Apple is owned by Microsoft now?

It's also less about the unfinished release, and more about the attitude that apple is taking with this release. It's like they are saying. "We're going to tell you how to edit"

"How much of Apple is owned by Microsoft now?"

I am not sure, but think i read once that they own 49% of apple stocks.

But may need to be corrected.

Joshua Irwin wrote:

It's also less about the unfinished release, and more about the attitude that apple is taking with this release. It's like they are saying. "We're going to tell you how to edit"

I so agree. And the thing about editors, is they all have their own methodology, and I feel here like they are trying to force us all into doing things only one way, and it is not a way that has proven to be in any way superior, at least as far as I have seen.

like they are trying to force us all into doing things only one way, and it is not a way that has proven to be in any way superior

Exactly what happened to Quantel in the past and the reason why most of us made the transition from AVID to FCP. History repeats itself and Adobe could be an option for some if not most of us.

Just thought you guys might want to know:

According to fortune magazine - FCPX is officially a "debacle": http://tech.fortune.cnn.com/2011/06/22/the-final-cut-pro-x-debacle/

I bought it to learn how to use the new final cut. if full functionality is coming then I would rather be able to fly with this version. I have no use for FCPX in a professional setting right now. FCP7 does everything I need it to.

but for offline editing the ease and speed of which I can assemble is vastly improved. This is and will be a powerful tool.

evolve.

Sadly, I'm afraid FCPX might be the death of FCP-line.

It's already being accepted that FCPX is not FCP - it is an iMoviePro. Thanks to FCPX's inability to assimilate into a professional workflow, we professionals are forced to leave the FCP system.

Therefore your "evolve" statement falls upon an empty room --- unless its a room for iMovie users.

I wouldnt be surprised if in 5-years, we find FCPX on our iphone5s -- because its dumbed down so significantly that it would be suitable for a future iOS-styled environment.

Clearly, FCPX is not a professional solution. But potentailly great for home video use. Therefore, i say:

FCP -- RIP 2011

https://discussions.apple.com/thread/3134605?tstart=0

I heard Apple just deleted all comments for FCPX from the Appstore -- is this true??

steady, steady....fix bayonets!!

I just checked the App Store and Final Cut Pro X currently has no reviews... That certainly is peculiar.

Apple has deleted hundreds of user reviews. The star-ratings are still there, but they have removed the text reviews.