-
FCP Launches on its own – Compressor
I posted this one on Apple’s FCP forum. No responses. I guess I should really just come here first:
Very spooky.
I sent a sequence to Compressor and started a compression for a dvd. After a couple of hours, it became obvious it was hanging on the last little bit. Compressor was still showing activity, but the time remaining kept wavering between 11 and 14 minutes. I quit Compressor and then had to force quit FCP.
I then went to Activity Monitor and quit CompressorJobController and force quit CompressorTranscoder, neither of which were responding.
Then FCP launched again all on its own. Bwaa Ha Ha!
I tried to quit in the conventional fashion and got this message:
“You cannot quit Final Cut Pro while rendering a job for Compressor. Cancel or allow the job to finish, and then quit Final Cut Pro.”
Compressor isn’t running and FCP opened in a new empty project not in the one from which I was trying to export. The Activity Monitor shows CompressorJobController and CompressorTranscoder not responding, but no other evidence of Compressor running. I quit and force quit these respectively again and after a minute or two FCP launched again.
The third time I forced quit, FCP stayed down. But those two Compressor files keep mounting and then stop responding.
Anyone know what’s going on? I’m having other issues and I’m wondering if CompressorJobController and CompressorTranscoder have anything to do with them.
Martin
2 x 2.26 Ghz Quad-Core Intel Xeon
6 GB RAM
OS 10.5.8
FCP 7.0.1
Color 1.5.1
Quicktime 7.6.4
Avid Media Composer 4.0.2.20 -
5 Replies
-
Hey Martin–
Not sure exactly what is happening, but the same thing happened when we upgraded our systems to FCP 7 late last year. I left it to the IT department, but I believe it was associated to shared clusters (Q-master maybe??). When my FCP ghost launched the program, I tracked it back to an unrelated system on the network. I think maybe the upgrade just got the cluster set-up out of whack. Not sure if you’ve got that set up, but if you do it might be a place to start.
Josh
-
Thanks Josh,
That’s what the literature floating around the net would suggest (and it’s amazing how few exact hits come up for “CompressorJobController (not responding)”), but my computer is all by its lonesome. I did launch Compressor since posting and discovered it was still trying to finish the job it had been hanging on when last I quit. Apparently it was still trying to work earlier today even after I had quit. Nothing showed to that effect in the Activity Monitor except those to “Not Responding” events.
Martin
2 x 2.26 Ghz Quad-Core Intel Xeon
6 GB RAM
OS 10.5.8
FCP 7.0.1
Color 1.5.1
Quicktime 7.6.4
Avid Media Composer 4.0.2.20 -
Open Batch Monitor and quit the job.
-
My problem was similar: with a job i sent from FCP to compressor, compressor would “stick” and I had failures on some of the segments in the job. Clicking the ‘x’ to cancel the job has no effect and compressor keeps “running” (@idle). I could quit Compressor even though the process never canceled properly however, I could not quit Final Cut (and force-quitting is usually NOT an option!)
The steps i took:
1) Opened QMaster in sysprefs and turned off services (Qmaster has to quit first before you can open the panel…accept it.)
2) re-opened Compressor and from the Compressor menu -> Reset Background Processing
3) Quit Compressor (you still won’t be able to quit FCP until you quit compressor!)
4) I could then quit *normally* out of FCP(5) turned qmaster services back on…
these were the steps I just now took to be able to quit FCP — I don’t know if all of them are necessary other than steps 2 and 3 above… and I don’t care — this worked.
Hope this helps and is actually repeatable!
fox
-
You took some steps I haven’t tried, Fox. The problem still happens occasionally. I’ll try this the next time it comes up. Thanks.
Martin
Martin
2 x 2.26 Ghz Quad-Core Intel Xeon
6 GB RAM
OS 10.5.8
FCP 7.0.1
Color 1.5.1
Quicktime 7.6.4
Avid Media Composer 4.0.2.20
Reply to this Discussion! Login or Sign Up