At a complexity setting of zero, the file took 39 seconds to encode, which jumped to 3:40 at a setting of five. When I compared the files, I definitely noticed better quality on the clip encoded at a setting of five. Unless you’re time-constrained, you should consider running all encoding runs at a complexity setting of five.

A/B Compare

Then it struck me: Rather than encoding separate files, why not try Expression Encoder’s A/B Compare to perform the same analysis? This mode is shown in Figure 6, with the key controls shown atop the Media Content Panel and on the player timeline and scrubber conrols. The theory is simple—you want to compare multiple encoding parameters before finalizing encoding parameters. So you choose your first set of parameters, then enter A/B Compare Mode by clicking the eponymous button. Then you drag the green markers in the timeline panel to the frames you’d like to compare, and click the Build Preview button.

After performing this action once, you have two items to compare: the original file and the encoded file, which has limited utility. However, if you change any encoding parameter, the Build Preview button becomes active, and you can click it to create another alternative to compare.

Figure 7 shows the display alternatives. You can display the two videos side-by-side or in a split screen view that works similarly to Apple’s Compressor. You choose which encoding alternative to display in each window (or on which side in the split screen display) with the A and B drop-down lists.

How do you keep track of which alternative is which? The encoding properties for the encoding run shown on the right (in the B list box) appear in