x264Encoder vs the Apple Codec

If you’re looking for the highest quality H.264 output, and encode on the Apple platform, you should try the x264Encoder encoder, which you can download here. This article contains comparison images that accompany my comparison review for Digital Content Producer (link to come).

This review debuts a new streaming test video comprised of clips from stock footage company Artbeats and from independent producer Connie Simmons of SimmonsArt, from her award wining PBS Series Landscapes through Time with David Dunlop. My old test tape was comprised of DV, HDV and AVCDH footage, and the footage was often shot under less than ideal conditions. I wanted to step up the quality of my starting point, and thank both Artbeats and Ms. Simmons for supplying their high quality clips. Since some of the source clips lacked audio, I filled in the blanks with a track from the always handy SmartSound collection.

You can view the clips themselves at http://www.doceo.com/h264comps/Main.html. As you’ll see, there are about 25 clips in the test file; on this page, I’ll display four or five of the scenes most representative of the quality disparity between the two codecs.

640×360@750 kbps

This was the easiest configuration that I tested; in low motion sequences, the difference between the Apple and x264 codec is minor; once the motion or scene complexity picks up, x264 pulls far head. In this talking head shot, the two codecs are close.

SD_David1.jpg

x264 starts to pull ahead in the higher motion barrel roll event.

SD_barrel.jpg

This is a simulated flyover of Bagdad; lots of motion and high detail. Again, the Apple codec shows the strain.

SD_bagdad.jpg

This is a time lapse shot; lots of detail and motion. Again, the difference is very noticeable.

SD_timelapse.jpg

720p@800 kbps

I encoded my previous 720p test file at 800 kbps, but there’s much more motion in this one so I bumped the data rate 1.5 mbps. Still, even at 800kbps, x264 can produce presentable quality at many clips, while the Apple codec completely falls apart.

720p_800_david2.jpg

720p_800_intro.jpg

720p@1500 kbps

Enough pain. Now let’s look at some comparisons at 1.5 mbps. Let’s start with a relatively low motion clip that the Apple codec clearly couldn’t stomach.

720p_1500_sizzle.jpg

This was a slow zoom into a beautiful garden in France, and the Apple codec didn’t fare any better on a vegetarian diet (on a roll here).

720p_1500_zoom.jpg

Blocking is desirable in football; not so much when encoding football games.

720p_1500_tackle.jpg

To be fair, if motion was low, the Apple codec was credible. The overall point, though, is this. If you’re encoding with the Apple codec in Compressor, you should start with a clean slate and try the x264Encoder.

720p_1500_pond.jpg

About Jan Ozer

Avatar photo
I help companies train new technical hires in streaming media-related positions; I also help companies optimize their codec selections and encoding stacks and evaluate new encoders and codecs. I am a contributing editor to Streaming Media Magazine, writing about codecs and encoding tools. I have written multiple authoritative books on video encoding, including Video Encoding by the Numbers: Eliminate the Guesswork from your Streaming Video (https://amzn.to/3kV6R1j) and Learn to Produce Video with FFmpeg: In Thirty Minutes or Less (https://amzn.to/3ZJih7e). I have multiple courses relating to streaming media production, all available at https://bit.ly/slc_courses. I currently work as www.netint.com as a Senior Director in Marketing.

Check Also

Why That Amazon Product Follows You Everywhere: A Look at Behavioral Tracking

We’ve all experienced it—you check out a product on Amazon, and before you know it, …

How GPAC Technology is Shaping the Future of Streaming: Key Insights from Fred Dawson

In a recent interview available on YouTube, Jan Ozer sat down with Fred Dawson, an …

The Reality of Codec Adoption in Six Pictures

Most people reading this post want new codecs to succeed as soon as possible, and …

Leave a Reply

Your email address will not be published. Required fields are marked *