In not making Compressor 64-bit, Apple preserves the program’s compatibility with a wide range of current third-party 32-bit QuickTime codecs, thus making the transition to FCP X easier for some current users. In fact, multi-threading and network rendering can save more time than just having Compressor at 64-bit. Why did Apple do this? Because simply making Compressor a 64-bit application would not solve the problem of codecs that are optimized for 32-bit, or which are not multi-threaded. Exporting directly from within FCP X uses 64-bit processing to handle rendering of complex video and audio, while the encoding is handled at 32-bit. This version offers users both power and speed, while quietly residing in the background until needed.Ĭomplex rendering benefits from a 64-bit application, as more of the processing can be handled within the memory buffer at one time. Like FCP X and Motion 5, Compressor 4 offers accelerated 64-bit processing of codecs like ProRes and H.264, but maintains legacy support for older 32-bit codecs still in use.
This lets a majority of users access the power of multi-core or multi-machine compression and transcoding directly, without having to launch Compressor. Most of the updates to Compressor 4 are buried deep under the hood, but the most remarkable of them is the seamless integration with FCP X. HTTP Live Streaming is immune to this problem because it uses port 80 over the HTTP protocol, just like a standard web page. Typical video streaming methods may fail to work when behind certain firewalls or proxy servers if sockets required by the stream are blocked.
#Compressor 4.4 hardware acceleration download
This HTTP Live stream offers the added advantage of moving freely without being blocked as often by firewalls or proxy servers in the same manner as a typical download would be. Compressor offers six pre-configured options-Broadband at 5Mbps and 2.5Mbps, Wi-Fi High/Low at 1.25Mbps and 750Kbps, and Cellular High/Low at 500Kbps and 220Kbps.
0 kommentar(er)
