Activity › Forums › Apple Final Cut Pro Legacy › Remove a job from Compressor’s batch window
-
Remove a job from Compressor’s batch window
Posted by Chris Poisson on June 6, 2007 at 11:12 pmHow the F do you do this? The cancel button will not work, and control clicking or deleting does nothing. How do you just get rid of a job?
Chris Poisson replied 18 years, 11 months ago 3 Members · 5 Replies -
5 Replies
-
Richard Martz
June 7, 2007 at 10:33 amI would love to know this as well. It is a frustrating lack of functionality.
Richard Martz
MagicMartz MediaFinal Cut Pro HD
Kona LH
After Effects
PhotoShop
Illustrator
Lots of other Fun Stuff! -
Chris Poisson
June 7, 2007 at 11:40 amYes, what happened with me yesterday is that a job which had been encoding for a while would not respond to the cancel or pause commands. I even went so far as to quit everything and trash Compressor’s and Batch Monitor’s prefs, and the job was STILL encoding. And it would not quit until it was done, thereby blocking any other work I wanted to get done.
A simple delete would do the trick.
-
Richard Martz
June 7, 2007 at 3:30 pmI understand. That has happened to me as well on a couple of occasions. I know there is a way to remove a line from the compressor’s taks listing because I think I remember doing that a couple of times. But I forgot the process since I rarely use this function.
Richard Martz
MagicMartz MediaFinal Cut Pro HD
Kona LH
After Effects
PhotoShop
Illustrator
Lots of other Fun Stuff! -
John Pale
June 7, 2007 at 6:57 pmThe cancel and pause buttons are supposed to work (an usually do for me). They may not work instantly though…sometimes theres a bit of a long delay.
Once or twice, I had this problem and used Activity Monitor (Utilities folder) to cancel all Compressor related processes.
-
Chris Poisson
June 8, 2007 at 11:54 amHi John,
Duly noted, the Activity monitor. Heck, tossing prefs didn’t work. Just dreading a time when a client will be sitting here waiting for his encode to start, and some job I’m trying to cancel won’t. Ouch, really bad, Apple!
Reply to this Discussion! Login or Sign Up