All of sudden Compressor 4.1 isn't working...

Question

Everything was hunky dorry with Compressor 4.1 on my Mavericks (Imac with 16gb) but today something happpened.
Now whenever I open Compressor 4.1 and load a file, it doesn't list it in the Current Window. 
And it won't allow me to add settings.
I've tried reinstalling Compressor but that isn't fixing the problem. Maybe I'm not reinstalling it properly?  But then I can't seem to find anything about how to reinstall on Mavericks.
What to do?

Answer 1

Hi Seth I agree with Russ. You really need to provide readers in the forums with some diagnostic information so that they can offer you some FREE experienced and professional help  regardless of what is recommended to assist ya .
To add to Russ's advice, Russ may have also omitted that  that you might consider the use APPZAPPER.app http://www.appzapper.com to remove all the associated objects  with the application.It does a fair job and rips most applications out by their roots! .. good to have in your tool bag.
Some additional ideas:
do you have any symptom dumps (crashreporter dumps) in /var/logs (check the console.app)? If so it's highly likely that the cause is related to the data objects / structures your are passing to Compressor (+i or for SEND TO COMPRESSOR). Worth a look and report back. These events are reported usually.
If the compressor.app V4.1 fails when you launch it then this is more likely the state information - yes purge that and usually in Compressors.app V4.1 case its will be the usual left overs in our old mates in ~/library/application support/ etc etc .. as  and its saved information in ~/library/saved application state/com.apple.compressor.nnnnn
Lastly if that application fails in LAUNCH and there's a dump (crash) then you MIGHT want to consider looking as a very last resort to an install and this would be the case where a component (framework or data (image etc) suddenly became corrupt or was missing and the app HAD to have it.
there's a lt more however I hope you get the idea.
FWIW, most of the recent Apple apps such as the pro-apps DO have many of the components REPLICATEd between them. If you examine the packages you will see that Motion, FCPX, Logic PRO, Compressor, iMovie etc all all have some common components. These components utilise lower level components in Mavericks etc.... no surprise here..
So there's a likelihood that in the worst case some  lower level GOODIE had been smacked about and is corrupt OFcourse if you could find it you could restore/reinstate it. Unfortunately this required a little bit of OS knowledge and most of us don't have the itme nor the inclination to bother since we are earning a living producing creative work - not attempting an apprenticeship in I.T.
There are some very clever people that post on these forums who are willing to assis!
Thus.. if you can, would you provide them with some detail of the incident? In doing so would you be able to restrict the information so it only relates to the issue at hand (i.e. not 100's of lines of log). You might consider the use of the FILTER in the upper right hand corner of the console.app
.... (eyes not rolling around .. LOL Russ!)
Post your results for others to see.
Warwick
Hong Kong