Optimising Videos in Final Cut Pro X
Apple's recent release of Last Cut Pro X (FCPX) has caused quite a lttle bit 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. Final Cut Pro X Effects
More mature versions of ultimate Lower Pro were built using the Carbon application development interface (API), which limited programs to 32-bit, therefore limiting available memory to 4GB. In a time where base MacBook Positives include 4GB of storage and dual-core, 64-bit cpus, this is a serious limitation. Apple's latest API, called Cacao, allows the use of 64-bit architecture, eliminating recollection bottlenecks, which necessitated a complete rewrite of ultimate Cut Pro. Because FCPX is a complete spinning using Cocoa, it's able to operate much faster on current hardware and takes good thing about multi-core cpus. FCPX Plugins
Judging by the assortment of professional features conspicuously absent, FCPX was probably written generally for speed with plans to add more features down the road. 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 job 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 lot of video formats, including XDCAM and Red, do not yet have support; due to complete rewrite, support for every single video format should be completely rewritten. Updates adding lacking features ought showing up soon, but many professional video editors are, obviously, worried that they'll be left in the bend.