How do I reinstall Compressor 4.1 as I used app cleaner to delete the app in hopes of getting it to run. Any help would be great

Try this free app from Digital Rebellion to un-install Compressor:

http://www.digitalrebellion.com/fcsremover/

Restart your computer and see if you can re-download Compressor.

Yeah. The App Store see a stray file.

Not sure why App Cleaner has become so widely used. Like many others here, I've been successfully using the DIgital Rebellion app that David recommended for several years.

Russ

As Jan Ozer wrote on a review that David posted, people seem to either love it or hate 4.1.

I'm probably the exception to Ozer's observation in that my reaction is mixed. I had all sorts of issues when I first installed. But eventually they were sorted out. What I like is that some things go a lot faster. I'm not, however, in love with some of the new workflow.

You said that you finally got it to reinstall but it does not work. What does that mean? Do you get error message? Does it crash? Hang? Something else?

And what about trying a new user account?

As far as rolling back to an earlier version, it can be done if you have a back-up you can restore from. And I suppose there's no down-side to contacting Apple, or your local Apple Store. Otherwise, I'm afraid not.

Russ

Hello Bob, its simple to pull Compressor V4.1 out of the system and add it back in. No need for any 3rd party "fix 'em' utilities either!.. just use OSX.

1. quit compressor.app V4.1
2. copy | make another instance etc of the ~/Library/Application Support/Compressor/Settings and History and templates if you want them
3. remove | delete | purge | rename | move ~/Library/Application Support/Compressor directory
4. remove ~/Library/Logs/compressor folder if it's there. (just delete it)
5. remove /Applications/Compressor.app (it package) either by
   • The EASY WAY: launch Launchpad.app , search for Compressor.app, GEAR DOWN (RMbutton or cntl+click), click on the 'x' and remove it (like iOS!) or
   • or.... navigate to /Applications, select Compressor.app, and move it to the trash. Empty the trash
6. go to MAC App Store:
   • assume you're logged into store
   • click at Purchases TAB at top.
   • scroll down to Compressor V4.1 in purchases list
   • GEAR DOWN ((RMbutton or cntl+click) and select INSTALL
   • monitor the download
7. fire up compressor.app and then quit it.
8. optionally: reinstate your Settings and other goodies to ~/Library/Application Support/Compressor
9. re-launch compressor.app V4.1 - should be OK.

Lastly, I'm curious what your experience/observations when Compressor.app V4.1 "Compressor 4.1 does not work in any way, shape or fashion while everything else?"

Post your results for others to see.

Warwick

 Apple Certified ACTC

Hong Kong

Doing a complete uninstall using your method here and also using 3rd party software and reinstalling via the app store still doesn't fix the crashing issues for me.

Compressor opens but if I try to do anything it crashes.

/sigh 😟

Same problem here. On two computers. Two clean reinstalls did not help here.

Worrying with this rather low quality of software releases from Apple now and then.

Ah well, happy there is Handbrake..;)

My thought is that there are probably different issues for each of the users who've posted in this thread. See what happens if you try to run Compressor from a new user account.

Russ

Two clean installs of the app or OS?

Russ

Two clean stalls of the app. A clean install of the OS just to get compressor working does not seem reasonable.

I maintain two professional workstations meticulously and haven been doing this for a long time.

Can't remember ever buying a new pro app that required more than some basic tweaking and housekeeping to get working.

Ah well...

Jan Anderson wrote:

Two clean stalls of the app. A clean install of the OS just to get compressor working does not seem reasonable.

Hey Jan, Not saying I disagree. Just relating what seems to be a pattern. Some people are finding the pro apps on Mavericks to be great and others are running into a lot of frustration. People who know more than I do about it have tried to understand what's going on and note that – for whatever reason – those with clean OS installs seem to be having the better outcomes.

Best of luck,

Russ

Cool, I was not saying I disagree either 😉

Final Cut Pro X is installed and working without issues on same systems.

Also had Compressor 3 working with no issues what so ever. Ah well.

Hoping for a fix of some sort and using something else meanwhile...

My setup of compressor started working today.

Have not changed anything just a another day's rest. Something settled itself...odd.

But perhaps worth reporting was I did try a hint from a user on another thread:

The first time I opened the app, changed a few settings in preferences and then quit the app

-before trying to start a batch-

That could possible have been the fix but I can't verify it and don't have time for it.

Working now though..

FWIW, YMMV

Hi Jan, just saw this thread again and further to Russ post from 2014 Jan 10 , do you have ANY diagnostic information that report you issues?

I'd be surprised if there is none (no external error logging). I know that reinstalling the compressor.app V4.1 (or most other applications) won't really help (can be a needless exercise) unless the original library framework and modules, elements etc were corrupt.. and that would be unusual. Certainly many 3rd party utilities that perform "de-installations" also try and remove parameter and state information setting as well. This also has the added side benefit of removing the acual cause of the error. (assuming it's not the source material) .

Good advice from many forum posters for compressor.app is also to log into a different user and run your job/workflow with the same material to isolate the localised environment.

Thus it's more likely the good old state information and that as most of of know is simple to fix.

FWIW, I have noticed the ODD UI glitches in compressor.app V4.1 that cause misbehaviour and stale job from not working , the situation being further exacerbated by symptom dump (component abends).

Such a compressor.app V4.1 error doesn't exhibit any interaction in the UI however this message is buried in the system.log: EXAMPLE ONLY

Compressor[26541]: FAILURE: Job com.apple.CompressorHelper-1 is not loaded in launchd.

Feb 13 15:41:15 macpro-.local compressord[26556]: In 'CFPasteboardCopyDataReturn __CFPasteboardCopyData(CFPasteboardRef, CFIndex, CFIndex, CFStringRef, Boolean, Boolean)', file /SourceCache/CF/CF-855.11/AppServices.subproj/CFPasteboard.c, line 2953, during unlock, spin lock 0x264c5d8 has value 0x0, which is not locked. The memory has been smashed or the lock is being unlocked when not locked.

The above was very difficult to find straight away however it was caused by a corrupt COmpressor.ap V4.1 Customised Setting (user generated setting) used in the Compressor.app V4.1 UI... thus it was not due to the actual compressor.app V4.1 application being corrupt, instead a user manufactured parameter setting (mine to be precise). Required two different symptom dumps to find. Thus if I had UNINSTALLED and hacked and dug out Compressor.app V4.1 or other application out of the system I would have lost some of my settings, templates and ongoing jobs, my cluster setup and the issue at hand. The issue would have happened again. This is the usual thing for all types of issues.. nothing new here.

My point here is: if you were able to post some of these diagnostics I'm confident that the people on these forums can help you get Compressor/Qmaster working optimally. 🙂

FWIW

Warwick

Hong Kong