Compressor 4.1 slow and unreliable on one rMBP but not the other

I'm looking for the some suggestions on how to fix Compressor 4.1 on my laptop.

I use two rMBP to balance still photograph/video editing at office or on location, yet Compressor 4.1 is running slow and worse, sometimes just hangs on one of the computers but not the other. Any suggestions?

On the "good" laptop, an 18 minute "master file/ProRes 422 encodes to a 2000 kbps mp4 file in seven minutes. On the "bad" laptop, 17 minutes, if it completes the job at all. Doing a "flip for mac" job doesn't work at all.

I've erased and reinstalled Compressor using FCS Remover, cleaned the install with Compressor Repair (both from Digital Rebellion).

Note this behavior is isolated to working from Compressor alone, not from invoking "Send to Compressor" from within FCPX.

Final observation: the good rMBP has FCPX 10.1 installed; the bad one, FXPX 10.1.1.

Any clues? Gotta job next week where I will be editing on site; would like to know what the heck is going on, and if upgrading FCPX on the "good" machine will cause the same risk to performance.

Also, the encode settings are exactly the same, including single pass.

Many thanks,

Tom

Can we confirm that the MBP's have identical specs – including CPU and RAM?

If that's indeed the case, see if the encoding settings for the faster one aren't possibly single pass. If you choose single pass H.264, you should also enable hardware acceleration.

Russ

Thanks for the reply. The laptops and the encoding configurations are absolutely identical. I'm embarrassed to say how long it took me to finally isolate the problem: repairing permissions in Disk Utility. After I did that, encoding speeds were almost identical.

It's curious however, because I repaired permissions only a week ago; then there was much to "repair," this time, Disk Utility reported something about a printer error. In that week however, I've been doing a lot of crunching on the machine.

Tom

I have been receiving a printer error #80 for my HP laser jet when repairing permissions ever since the upgrade to Mavericks. It corrects and doesn't seem to cause any issues but it is always there on permission repair. I think this is an OS bug as it happened in the previous Lion OS then disappeared with Mountain Lion. Now it's back.