Compressor wont cancel

Open System Preferences and Qmaster. Click on Stop Sharing.

If you are sending from fcp to compressor, I don't think you should ever use a cluster. Just use "this computer." Don't think it makes things happen any faster, and you often have this sort of problem.

If you used "this computer" rather than a cluster and can't stop it in the history window, you can go into the task manager (in the appllications: utilities folder) and stop the process. Not sure which one it is, but it is one of the ones with compressor in the name.

sorry "activites monitor" not task manager

Click on start, and then if it changes to stop, close Qmaster and relaunch Compressor to see whether it jarred it into cancelling. Also go to Reset Background Processing in the Compressor menu and click that.

if he's not using a cluster, I don't think this will make a difference.

Michael, Maybe not. I know that he's not using a cluster. I found a thread on another FCP forum where it apparently worked a guy who couldn't get his process canceled. So I figured, why not…no harm either way.

Russ

yeah, it never hurts to throw something out there. I've thrown ideas out that were real long shots and every once in a while, it'll work.

Glad it's working for you.

But for others reading this, what did you do to get it to cancel?

Russ

Russ, I've used your technique successfully when I've used a cluster when sending from fcp and I've also used activity monitor but often after using either technique I've had a system freeze and had to do a forced restart. Could be just a coincidence...

Hi Michael.

Resetting the Qmaster share prefs was kind of a Hail Mary idea that I borrowed from someone else.

My Compressor/Qmaster experience over three versions has actually been outstanding compared to other pro apps – very stable – and I typically can't reproduce many of the problems that some users report on these boards. Of course everyone has a somewhat different systems configuration, different plug-ins etc which probably account for 95% of the reasons why some "bugs" exist for some and not for others.

But just a few times I have had jobs that refused to cancel, regardless of what buttons I "pushed". Even rebooting the machine didn't seem to phase Qmaster…it resumed doing whatever it was doing after I relaunched. I frankly cannot now remember how those were resolved…a random click perhaps.

I still hope the OP will post what it was that worked for him.

Russ