Optimizing Video clips in Final Cut Pro X
Apple's recent release of Last Cut Pro X (FCPX) has caused quite somewhat of controversy. Many new features and speed advancements have been added, but many more features are conspicuously missing. Further, this latest release is not backward compatible with any previous versions. Why is it so different and what is Apple's strategy? Here's the scoop. FCPX Plugins
Old versions of ultimate Slice Pro were built using the Carbon application encoding interface (API), which limited programs to 32-bit, therefore limiting available memory to 4GB. In a time where base MacBook Positives feature 4GB of recollection and dual-core, 64-bit cpus, it really is a serious limitation. Apple's latest API, called Cacao, allows the use of 64-bit architecture, eliminating storage bottlenecks, which necessitated a complete rewrite of ultimate Cut Pro. Because FCPX is a complete spinner using Cocoa, it's able to operate much faster on current hardware and takes good thing about multi-core cpus. Final Cut Pro X Effects
Judging by the variety of professional features conspicuously absent, FCPX was probably written generally for speed with plans to add more features down the line. It at the moment does not support OMF output, which is usually used to import audio tracks into ProTools for mixing, or Edit Decision List (EDL) data, a feature used to move a task into another program for the finishing stage. Multi-cam support and output to tape, a format still employed by many professionals, is also missing. Furthermore, there appear to be no plans to release a new version of Last Cut Server, which is employed to allow multiple users to work on a remotely-stored project simultaneously. A number of video formats, including XDCAM and Red, do not yet have support; due to complete rewrite, support for each and every video format must be completely rewritten. Updates adding absent features ought showing up soon, but many professional video editors are, no surpise, worried that they'll be left in the bend.
