Premiere CS5 takes 5 minutes to start up
May 2, 2010 7:18 AM
-
-
-
Steve,
Adobe takes both the Bug Reports and the Feature Requests seriously. For the Bug Reports, the more detail that one can furnish, the easier it is to replicate the issue in the lab. Usually, unless more info is needed, there will likely be no direct contact, but work is being done.
As for T/S, Adobe has promised to make improvements. Going way back, Adobe T/S was almost the paradigm in the software industry. I had few issues, but those few were handled professionally, quickly and correctly. Over time, things changed, and apparently not for the better. I have not needed to use T/S in many years, but do read the horror stories. It does seem as though the people in the call center are not actual users of the products, and have a rather limited "script." This is from the myriad reports and NOT from first-hand experience.
As a change of the magnitude that I imagine, it would take some time and effort, all I can offer is "be patient, and let's hope that Adobe is planning on changing things in a positive way." I'd love to hear that Adobe T/S (and C/S) was back to the way it was in the "good old days." Until then, I feel that this forum (and the one for PS, AI, et al) are the better places to get T/S. We are also blessed to have an Adobe technical presence here, as that was not always the case. [Many of us spread rose petals at the feet of Jeremy, Dennis and Wil... ]
Good luck,
Hunt
| -
-
Steve,
That was the statement, to which I was referring. In the major corporate world, 9 mos. is the blink of an eye, especially when one has a large investment to try and recoup. Unfortunately stockholders might not be users with issues. I know that is not comforting to us users, but is an unfortunate fact of life nowadays.
I just hope that they can get things back on track - before I need to use T/S again...
Hunt
| -
-
-
-
I am pleased to say that I have categorically solved this problem (at least on my system).
It is indeed to do with the various components needing access to the local subnet.
My situation was as follows:
OS: Win7 Pro 64bit.
Firewall: Comodo Internet security 3.12
Premiere Pro CS5
Launching Premiere resulted in lengthy (5+ minutes) hang with splash dialogue showing the stall was on "Loading ExporterQuickTimeHost". This also happened with Adobe Media Encoder.
After reading this forum I looked in my firewall block/allow list for dynamiclinkmanager.exe and Adobe QT32 Server.exe but couldn't find them.
I had, however, blocked Premiere from accessing the internet (I don't need it to, so that's my default security policy) only it wasn't actually asking for access to the internet (I realise now) it was merely asking for access to the local subnet.
When I installed an update to Comodo Firewall, (4.1 - though this is'nt actually relevant) I realised what the problem had been as the security policies got wiped (forgot to back them up) and needed to be re-learned from scratch.
As I launched Premiere, Comodo popped up a dialogue saying that Premiere wanted access to the local subnet (I read it this time!) and I clicked 'Allow'.
Premiere's splash screen got to "Loading ExporterQuickTimeHost" and THEN dialogues popped up for Adobe QT32 Server.exe and dynamiclinkmanager.exe - both asking for the same local subnet access.
This had never happened before, because blocking Premiere itself from subnet access stopped these from also asking.
And 2 WHOLE SECONDS LATER ..... Premeier desktop was there awaiting my instructions!
I believe I may have uttered a "woo" and a "yay" at this point.
I trust you, dear reader and fellow sufferer, will also have the same joyous experience.
| -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 10 points awarded for Correct Answers
- 5 points awarded for
-
10,000+ points
-
1,001-10,000 points
-
501-1,000 points
-
5-500 points
-
