[Jon Chappell]

Try some of these steps and see if they work for you:
https://www.digitalrebellion.com/blog/posts/compressor_error_unable_to_connect_to_background_process.html

My software:
FCS Maintenance Pack – Tools to keep Final Cut Studio running smoothly and fix problems when they arise
FCP Versioner – Backs up Final Cut Pro projects to XML and creates changelists for each revision
More tools…

[Jon Chappell]

I haven’t been able to spot a noticeable visual difference by exporting this way. You are introducing a significant loss of encoding speed for negligible benefit.

Exporting directly to Compressor is slow for two reasons:
1) Compressor has to request each frame from Final Cut Pro, which is much slower than reading the data directly from a file. This is particularly bad when using Frame Controls or doing multi-pass encoding.

2) You can’t take advantage of virtual clustering to better utilize your multi-core processor.

But having said that, Send to Compressor should still work. If you click the little “i” icon in Batch Monitor, what does it say about the failed batch?

My software:
FCS Maintenance Pack – Tools to keep Final Cut Studio running smoothly and fix problems when they arise
FCP Versioner – Backs up Final Cut Pro projects to XML and creates changelists for each revision
More tools…

[Jon Chappell]

This is caused when the ImageDescription extension of the file is incorrect, which means that the software you used to create the file didn’t output it correctly.

The reason Corrupt Clip Finder didn’t pick it up is because QuickTime ignores it – only Final Cut Pro crashes when it encounters it. This is an FCP bug.

I believe I know how to fix it. If you get in contact with me, I can send you a beta build of QT Repair that should be able to fix it – if the issue is what I suspect it to be. You’ll have to identify the problematic clips manually though.

You can contact me here:
https://www.digitalrebellion.com/contact.htm

My software:
FCS Maintenance Pack – Tools to keep Final Cut Studio running smoothly and fix problems when they arise
FCP Versioner – Backs up Final Cut Pro projects to XML and creates changelists for each revision
More tools…

[Jon Chappell]

I really don’t think extra RAM will make much difference. I can tell by the crash log that you’re putting a strain on the system by editing what looks like multiple HDV streams complete with filters. When Final Cut Pro can’t keep up with what you’re doing, it’s far more likely to crash, and this is the cause in this instance.

Consider a ProRes workflow – you won’t need to buy anything, it will be faster to composite and process your filters and it will solve your crashing issues.

[Jon Chappell]

The OP didn’t actually post the crashed thread so Crash Analyzer went with its best guess. This means that until the OP posts the crashed thread, we won’t know for sure if that is the issue or not.

But having over 100 simultaneous threads trying to process HDV data plus filters is a recipe for disaster. I would recommend converting the footage to ProRes or at least setting the sequence to render in ProRes.

[Jon Chappell]

Whitney, can you please open up the Terminal and type “ls /Library/Receipts” (without quotes) and then paste the information it produces here. It looks like a framework is being left behind, which is strange because I can’t replicate the issue on my computer. FCS2 reinstalls just fine after removing FCS3.

[Jon Chappell]

Which version of Compressor are you running? Did you run Compressor Repair on a non-administrator account?

[Jon Chappell]

Snow Leopard has some serious underlying file system problems. It is not ready for primetime at all. I’ve received a lot of crash logs from open / save dialogs in 10.6.1, but interestingly not 10.6.0. So on that anecdotal evidence, it might be worth downgrading to 10.6.0 to see if the problem goes away and if not, hope that 10.6.2 fixes it.

[Jon Chappell]

Just wanted to clarify – FCS Maintenance Pack has a fully functional trial so you can happily use it for 15 days as if it was the full version and then uninstall it and not have to pay a penny.

[Jon Chappell]

A lot of companies have poorly-written, confusing user manuals. Apple is not one of these companies. The reason why there are 4 or so manuals is because Apple literally gives you everything you could ever want to know.

See Appendix C: Working with 24p Video p.1900 and Ch. 20: Using Compressor with Final Cut Pro p.1762.

https://manuals.info.apple.com/en/Final_Cut_Pro_6_User_Manual.pdf