Have you updated PrPro CS5 yet? What version are you running?
If not, do so, as the recent update fixes many issues, and I think that this is one.
The update function tells me my applications are up-to-date, and the PPro version shows as Version 5.0.3.
I've already tried uninstalling and reinstalling but no luck
> I also cannot get Analyze content to work - this is not something I need but it would be nice.
This is very often because you don't have write permission for the source files or the folder in which the files reside. The feature that analyzes speech and converts it to text works by injecting XMP metadata back into the source files or by writing the XMP metadata to an XMP sidecar file alongside the source files. If the source files or the folder that they're in are read-only, then the Analyze button is greyed out.
Regarding your other issue:
What operating system?
What exact version of Premiere Pro? 5.0.3?
Yes I have 5.0.3. Analyze Content is not greyed-out: the problem is that when I use it, Media Encoder starts up but there is nothing in the input queue. This is the same for face detection and speech recognition.
The OS is Win 7 Ultimate N (64 bit of course)
Just looking at the process with process explorer I find that after the exit, there is only one thread running (but it's churning away sucking up CPU time)
In fact looking at the stack for this process, it seems to be in the ATI driver most of the time. I'll have a look for an updated driver for my graphics card (it's an ATI Radeon HD 3800)
I've fixed it! Updating the ATI driver software has fixed both the "no exit" problem and the "analyze content" problem.
Thanks for the replies anyway
Great news. I started to suggest that, as it helped with a similar issues in PrE, but did not recall hearing of it regarding PrPro.
Thanks for reporting your success,
Oops. I find that, although Analyze Content is now working, PPro still hangs around
after exit. When I attempt to look at the process properties with procexp, PPro exits. It still hangs around if I just leave it alone. Not sure how to revert this question back to "unanswered".
I have the same problem. PR, AE, EN all remain running after I quit them. I keep Task Manager running in the task tray so I can quickly end the processes when necessary. Not a huge problem, except when I need the RAM back from AE or PR.
Do you have an ATI video card?
No, Nvidia GTX 470
I have the same problem and I also have a Dell XPS but a 435MT in my case with an ATI Radeon 4800 video card.
I have tried to fix this problem in the past by updating the video card, and I also thought it went away but I have not used Premiere in a while and it seems the problem is back.
Will try to update the video drivers yet again and see.
Installed the latest ATI drivers 10.12
Reset my PrPro preferences
The problem does not happen if you just click on Exit on the Welcome Dialog so I created a blank project with all Default settings and even left it named Untitled but even loading that project the problem persists.
I even tried closing the project and then clicking Exit.
By the way, my version of Premiere Pro CS5 is 5.0.3 (MC:218798)
Any ideas anyone?
Another bit of info that may be important.
I had CS4 installed in this computer. Disabled it, Uninstalled it and ran the Clean Utility.
I also manually removed as many CS4 folders as I could find.
Then installed CS5.
When I try to analyze PPro with process explorer when it's in a hung state, it exits. But Encore still hangs around, and process explorer shows one thread with the following stack:
The bottom dll is part of the ati video driver, so it seems (at least on my machine) that the latest driver still has problems with Encore at least.
In my PC. When PrPro hangs it shows the following in the Process Explorer thread stack
They are clearly different problems - do you have only one thread left? Are you checking the stack multiple times? (Each time you examine the stack you are getting a snapshot - it might be different each time).
I don't know why I'm asking these questions - I can't fix it! If an Adobe developer looks here, perhaps it might give him some clues. I can provide a crash dump of a hung process if someone asks.