-
The reason FCP is not 64-bit
Ars Technica has a very technical, in-depth review of Snow Leopard, in which Quicktime X is discussed. Essentially, Quicktime is only just now making the 64-bit transition, and Quicktime X has very limited functionality relative to Quicktime 7. The features of Quicktime that are used extensively by Final Cut Pro are not yet 64-bit, so it’s impossible for FCP to be a 64-bit application until Quicktime X is developed enough to fully support all of the features present in Quicktime 7. This isn’t likely to happen in the near future.
To quote the article:
“As anxious as developers may be for a full-featured, 64-bit successor to the QuickTime 7 engine, Apple itself is sitting on top of one of the largest QuickTime-riddled (and Carbon-addled, to boot) code bases in the industry: Final Cut Studio. Thus far, It remains stuck in 32-bit. To say that Apple is “highly motivated” to extend the capabilities of QuickTime X would be an understatement.”
For the full article, follow the link below:
https://arstechnica.com/apple/reviews/2009/08/mac-os-x-10-6.ars
This is one of the most comprehensive discussions of Quicktime and 64-bitness that I’ve come across. Hopefully it will address many of the questions from the editing community about why FCP isn’t yet a 64-bit application. It’s because Quicktime is undergoing a complete overhaul to become 64-bit capable, and since Quicktime is pervasive throughout FCP’s basic structure, FCP will share the same fate as Quicktime when it comes to its development pace.
Please link back to this post when this topic pops up again (and it will) on this forum.