[Dave LaRonde] “If all these edit timelines use the same codec, it would be easy — and fairly fast — to export reference (i.e. not self-contained) files, then drag ’em into Compressor and batch export a bunch of H.264’s.”
This is exactly the workflow I would recommend. Use FCP’s batch export feature to export reference (i.e. not self-contained) Quicktime movies of all of your sequences, then bring those reference movies into Compressor to create h.264 Quicktime movies.
As for specifics about Compressor:
1. Set up a virtual cluster on your computer. Search this forum for “Qmaster” or “vrtual cluster” for step-by-step instructions. Note that the “sweet spot’ for the number of instances to assign Compressor in the Qmaster preferences will vary depending on the number of cores in your computer. On an 8-core machine, the sweet spot seems to be 6 cores.
2. Create a custom encoding profile in Compressor by starting with an h.264 preset, then switch on Frame Controls in the Inspector tab and select Best for the resize filter. Make sure to set the frame size and pixel aspect to your required specs, then save the custom preset.
3. Open the Quicktime reference movies that you batch exported form FCP and apply the custom encoding preset that you created in step 2.
4. Instead of submitting the job to “local computer,” choose the virtual cluster that you created in Qadministrator in step 1. This will ensure that Compressor will make full use of the optimum number of cores for processing.
Note that the “send to Compressor” feature in FCP unfortunately cannot utilize virtual clusters:
https://support.apple.com/kb/TS3079
This makes it necessary to manually batch export from FCP and then process the exported reference movies in Compressor in order to make the most efficient use of multicore processing on the computer.
Ideally, the “send to Compressor” feature should be updated in a future version to support job submission to clusters. I think that the feature is pretty weak in its current implementation.