ive noticed recently (after trying to play around with h265 encoding) that now every time i start up my mac compressors background instances fire up and stay active even though they aren't working a job. The only thing that makes it go away is starting compressor and then quitting. I have already tried removing user compressor folder, found qmaster in the main library removed that as well. Any ideas? Thanks!
There's nothing wrong with those background tasks running, they won't slow anything down if they're not doing anything. And they're used by other apps, too.
Two things to try. First, inside Compressor go to Preferences > Advanced > Reset Queue. You'll do this twice. The first time Cancel Jobs and the second time Repair Compressor.
If that doesn't do it and you really want them gone, download the freeware app FCX Remover from Digital Rebellion (dot com) to totally remove Compressor, reboot your Mac, launch the App Store, go to the Purchased section, and Install the latest version of Compressor.
There's nothing wrong with those background tasks running, they won't slow anything down if they're not doing anything. And they're used by other apps, too.
Two things to try. First, inside Compressor go to Preferences > Advanced > Reset Queue. You'll do this twice. The first time Cancel Jobs and the second time Repair Compressor.
If that doesn't do it and you really want them gone, download the freeware app FCX Remover from Digital Rebellion (dot com) to totally remove Compressor, reboot your Mac, launch the App Store, go to the Purchased section, and Install the latest version of Compressor.
thanks for the reply 🙂 i did manage to clear it out somehow but forgot how i did it. i know that they normally fire up when you first start up but usually they go away pretty quickly, anyway they weren't doing that which creates a GPU dependency as well.
Not just sitting idly in the background, no, they don't.
i use istat menus i can tell when the discrete graphics is active and which processes are activating it. That's actually how i noticed it. 🙂
Compressor instances starting up for no reason…
