Compressor 3.5 still hangs. Sad.

[Jeremy Garchow]

A little more info on what exactly you’re trying to do and the steps you are taking might help to understand your problem.

[Erik Mickelson]

I don’t believe that “I” am having a problem. I think Compressor 3.5 is still a bit buggy. So is Qmaster for that matter.

If I want to stop a job in compressor, I should be able to do that and have it happen quickly and efficiently. Apple Compressor needs me to find some .plist files and delete them, then restart my machine and then, maybe Compressor will release the job. Sometimes it works, sometimes it does not.

Qmaster is still buggy as all H*ll. I have 4 instances in Qmaster and only 2 are showing up in my batch processing. I will probably have to reinstall Compressor again and then again when the bug pops up again. This has been going on for what 3-4 years now?

I am starting to seriously look other solutions.

MacPro Dual Core2Duo 3.0Ghz, 6GB ram, 4TB SATA Raid, Tiger 10.4.11, FCPStudio 2, QT 7.5.5

[Chris Borjis]

when I cancel a job it may take up to a minute for them to stop.
This is how it is. I wish it would quit instantly. hell I wish
the mac would instantly shut down when I tell it to, but it usually
takes about 20 seconds for it to quit all processes and shut down.

A lot of us use compressor daily with no issues at all.

I wonder if something else is up.

have you tried either of these?

https://www.digitalrebellion.com/compressor_repair.htm

https://www.digitalrebellion.com/blog/posts/how_to_reinstall_compressor_and_qmaster.html

[Erik Mickelson]

No help needed. Usually Compressor works fine for me for a while.

For some reason Compressor just goes bad for many, many people. There are intensive instructions on Apples website to “clear” the corrupt Compressor files and ultimately requires a delete/install procedure that will cost a few hours time at the maximum. This happens to a LOT of people on what machine? We don’t know. I bet Apple does. YMMV.

MacPro Dual Core2Duo 3.0Ghz, 6GB ram, 4TB SATA Raid, Snow Leopard 10.6, FCPStudio 3, QT X

[Jeremy Garchow]

[Erik Mickelson] “. I have 4 instances in Qmaster and only 2 are showing up in my batch processing.”

You still haven’t given us specifics about what kind of movies are you are compressing from and what kind of movies you are compressing to. Specifics help. There’s reasons why you are seeing two instances, one of them being from Long GOP sources. Are you trying to compress XDCam/HDV material?

Please, be as specific as possible, and I will try and help you.

Jeremy

[Erik Mickelson]

Jeremy may have a solution to the madness?

Why yes I am compressing XDCAM EX footage sometimes. This particular time I am compressing some DV material to H264.

MacPro Dual Core2Duo 3.0Ghz, 6GB ram, 4TB SATA Raid, Snow Leopard 10.6, FCPStudio 3, QT X

[Jeremy Garchow]

[Erik Mickelson] “This particular time I am compressing some DV material to H264. “

Great. Thanks for that.

Now, you have to make sure that ‘Allow Job segmenting’ is selected in the Encoder tab.

Also, are you using Qmaster or are you setting up a virtual cluster in the Qmaster prefs? There’s a difference.

Basically, are you trying to do this on one machine or do you have a network of machines?

Jeremy

[Erik Mickelson]

‘Allow Job segmenting’ is selected in the Encoder tab.
I am using a virtual cluster set up from the Qmaster prefs. This is on one machine.

I am compressing a reference DV movie (NOT self contained). I am now exporting the file self-contained and will try that out. It is only one movie that is hanging things up. The other 7 movies rendered out fine. There are NO effects on the footage.

MacPro Dual Core2Duo 3.0Ghz, 6GB ram, 4TB SATA Raid, Snow Leopard 10.6, FCPStudio 3, QT X

[Jeremy Garchow]

Also, there’s a ‘reset background process’ function in the ‘Compressor’ menu that helps to clear things up.

[Jeremy Garchow]

And I know this sounds silly, but you have to make sure that you select your cluster after hitting submit but before hitting submit again.

Jeremy