The 4.3.0 release of Apple Compressor was notable for the number of bugs it contained, including slow compression speeds, inability to burn DVDs and non-functioning watermarking.
Last week, Apple updated Compressor to version 4.3.1 specifically to address many of these issues, including:
SO, HOW’S THE NEW VERSION?
In a word – I’m not sure.
Watermarking, which worked great in all versions of Compressor prior to 4.3, is still broken. Since every video I compress is watermarked, this means that I need to reserve one system to run an older version of the software specifically so that I can create watermarks successfully.
NOTE: You can’t store different versions of Compressor on the same system. Updating Compressor, Motion or Final Cut erases the old version with the new one.
In the screen shot above, the left-hand image is from Compressor 4.2.1, the right-hand image is from Compressor 4.3.1 (which looks the same as Compressor 4.3.0).
As for DVD burning, I don’t burn DVDs on a regular basis anymore, so I’m not the best judge. However, I received almost twenty DVD complaints with the 4.3.0 release. So far, with 4.3.1, I’ve only had two.
If you are burning DVDs, let me know how well the new version (4.3.1) is working for you, in the comments below. If necessary, I’ll share them with people that need to know.
NOTE: One reader posted, just a few minutes ago, that: “I upgraded in the early hours of this morning [to Compressor 4.3.1], tested when I exported from Compressor 4.3.1 and the grainy effect is no longer appearing on the DVDs. It also appears to be exporting to DVD faster.” So this is good news.
For the last several years, I’ve been testing compression speeds of each new version of Apple Compressor and Adobe Media Encoder using the same suite of test files and settings.
In my previous tests, I assumed that whether I used an internal SSD or external hard drive, because compression speed was dependent upon the CPU, the speed of storage wouldn’t matter. I discovered this is not the case. The speed of the storage has a major impact on compression speed, as I illustrate below.
Also, in past tests, I compared compression speed using both an iMac and MacBook Pro. Because watermarking is still broken, I can’t upgrade my MacBook Pro because I need to use it for compressing all my videos. Once watermarking is fixed, I’ll update these tests with additional numbers.
In all cases, my tests used the default YouTube HD 720 setting that ships with Apple Compressor. This defaults to multi-pass compression with a data rate of 9,765 kbps using the H.264 codec. The only change I made during these tests was to compare single-pass compression vs. multi-pass to see how much it affected the speed. (Answer: a lot!)
NOTE: Only the H.264 codec in single-pass mode is hardware-accelerated. Other codecs and multi-pass compression are done exclusively in software, which is much slower. Youtube, and other social media, presets all output H.264.
SO, IS IT FASTER?
[Click here to see the full PDF with specific results and all my notes.]
The answer is: maybe; it depends upon the codec and storage speed.
In short, if you compress a variety of different source codecs, 4.3.1 is about the same speed as 4.2.1. If you export exclusively in ProRes 422, it should be faster.
NOTE: I don’t trust my results from the 4.2.1 multi-pass testing for ProRes 4444, which you can see in the PDF. I suspect I ran the 4.2.1 compression test in single-pass mode, which would speed the compression dramatically. Version 4.3.1 compresses about 3% percent faster than 4.1.2 when in multi-pass mode compressing ProRes 4444 files.
The speed of your storage makes a BIG difference in how fast files compress. For example, with ProRes 422 in multi-pass mode, which is the default setting:
For ProRes 4444 in multi-pass mode, which is the default setting:
I ran both these speed tests twice, because the differences were so dramatic. I was very surprised with these results.
Single-Pass vs. Multi-pass
Strangely, the default setting for YouTube compression uses multi-pass mode. At the bit rate Apple uses for YouTube (9,765 kbps) there’s no advantage to multi-pass. In fact:
This increase in file size contradicts what I used to believe: that multi-pass took longer but created smaller files with higher quality. Neither of these seem to be true. First, because single-pass mode uses hardware to accelerate compression, which is vastly faster than software compression alone. Second, the high bit rate of the YouTube setting yields great quality, regardless of single vs. multi mode.
If Apple is using multi-pass mode to improve image quality, changing the bit-rate to about 12,000 kbps, while setting compression to single-pass mode would generate files of about the same size in less than half the time, with equal or better image quality.
NOTE: You can change the default YouTube setting from multi-pass to single-pass in the Inspector, after selecting the compression setting applied to a clip.
WHAT SETTINGS SHOULD I USE?
For fastest performance with highest quality for YouTube (or any social media site accepting H.264 video), I recommend:
Data rates for personal websites should be set lower. In all cases, though, single-pass compression will be faster.
NOTE: If the master file is already stored externally on a RAID or SSD, you won’t gain any speed savings by copying the file to your internal drive, as it will take longer to copy than the time you save in compression.
I have mixed feelings about this update. Since Final Cut Pro X and Compressor use the same background compression process, upgrading your system to FCP X 10.3.x will automatically update the compression engine, even if you don’t own Compressor.
NOTE: The only way to run Compressor 4.2 is to use an different system that hasn’t been updated.
The speed improvements for some codecs are faster, but not in every case. The default YouTube settings generate unnecessarily larger files at speeds about 50% slower than they could be. The hardware you use to store source files will absolutely affect compression speed. While on-going problems with video watermarks mean that I, personally, can’t use the current version of Compressor to compress my videos.
NOTE: These compression issues do NOT affect image quality when sharing your project as a Master File out of Final Cut Pro X.
If Compressor works for you, great. If you are having problems, you’ll probably have the same problems compressing using either FCP X or Compressor. In which case, you’d be better off doing your media compression using different software.
At least until Apple releases Compressor 4.3.2.
27 Responses to Apple Compressor 4.3.1 – Still Not Perfect← Older Comments
When I open my FCPx 24p full HD Rec 709 project in compressor for outputting DVD & Blu-ray what is the best Colour space option to be used? Is it same 709 or NTSC ?
Thanks in advance..
DVDs are always standard def, so you’d use Rec. 601 (either NTSC or PAL). However the color space between 601 and 709 is virtually the same, so you could leave it at 709.
Either way, Compressor will handle the color space issue properly.
Compressor 4.3.1 introduced a headache in my workflow. My older version of Compressor loaded an MPEG2 file almost instantly but with the new version it takes at least 3 minutes for the file to load and allow me to change settings and begin the conversion process. It is a big pain. I use a MacPro 2013.
Thanks for letting us know. I’m still not entirely sold on this new version. Too many things are slower or awkward under the hood.
I hoping Apple cleans these up in the next major update.
I am disappointed in the latest version 4.3.2 of Compressor because of my need to produce high-quality DVD and Blu-ray versions. I have had to resort to iDVD for the purposes of making a DVD and am yet to find a way to produce a Blu-ray version. I am using an early 2013 MacBook Pro and a Pioneer BDR-XD05TB which purports to be Mac friendly. Of course I am also running FCP X 10.3.4 and Sierra. However, as I am not familaiar with Compressor I am wondering if the problems are due to that rather than shortcomings with the applications?
Apple has, at best, been lukewarm in its support for Blu-ray Discs. Sadly, they abandoned serious support for both DVD and Blu-ray years ago, except for its rudimentary efforts in FCP X and Compressor. Worse, Adobe canceled the best alternative – Encore – 3-4 years ago as well.
Aside from Roxio Toast, I don’t have a recommendation for good Blu-ray software.
Compressor is actually still part of my BluRay workflow. It still has settings for creating a great .264 video file and AC3 audio file, either stereo or surround, that I then pull into Encore (which you can still download as part of Adobe Creative Cloud) for the BluRay authoring to disc image.
One odd behavior I’ve noticed in the latest version of Compressor is when I set custom bit rates for H264 compressions, the results don’t match at all. For example I set it to 20000kpbs and it rendered out a monster file that was actually 77000kbps. Can’t figure out why it’s doing that. I’m guessing it’s a bug, because I”m using same settings as before and identical workflow, machine, drives, everything. Only diff is new Compressor version.
When i convert my footage (UHD) to upto4k youtube. My graphics edges seems to be pixelating. Any tips to solve that
Pixelation (stair-stepping) occurs when you take lower-resolution footage and up-res it to a larger frame size. It should not occur when you are compressing a 4K master file into a 4K compressed file. Most often, compression removes color data; there’s no reason for it to remove pixels when the frame size stays the same.
So, make SURE you are not up-rezing smaller frames to larger ones. If the problem persists, send me a screen shot via email and I’ll help if I can.