Forums

Please run my Premiere Pro Benchmark PPBM4 (yes I know it was designred for CS4) but since Harm has run it sucessfully on CS5 it will tell us how well you machine/OS is tuned and/or configured.

If you follow this link and then continue to the second included link, there are a number of data requested, like Process Explorer and DXDIAG: Some suggestions...

If you post those as screenshots and attachment, we can have a look at what may be wrong.

QT 7.6.3 & 7.6.4 had issues with Adobe programs, just as 7.5.3 & 7.5.4 did. I had heard that 7.6.6 was a good version, but have to admit that for me, 7.5.5 was the "last known good." Wonder if 7.6.6 is following in the footsteps of its recent predecessors? Maybe try with a copy of 7.5.5.

Good luck,

Hunt

Thanks for reporting on the QT version requirement. Did not know that.

Sorry that it did not work either.

Good luck,

Hunt

Clean installation of Win7 x64.

Using NOD32.

Using Comodo firewall.

No other Apple apps.

No 3rd party codecs.

No other Adobe apps running.

BUT when I diable Firewall it works with no problem.

BUT I need Firewall.

What App or IP address I need to unblock in firewall to get CS5 and firewall running together?

Thanks!

EDIT: It seems I need to unblock Premiere and QT server.

But I'm little paranoid regarding internet attacks.

I would like to keep programs blocked in firewall while CS5 is working... but how?

Thanks again.

Along those lines, I am on a DSL connection, though behind a hardware firewall, between the connection and the workstation, and NOT within the workstation. In 15 years, I have never had one breech. Maybe I have just been fortunate, but also have zero Internet presence, while editing, and my guard (software) is down.

Just an observation,

Hunt

Those components are separate (necessary) processes that are part of the Adobe suite.  Adobe QT32 Server, in particular, is required for anything Quicktime related - since Apple hasn't upgraded Quicktime to 64 bit, we were forced to put Quicktime support routines in a 32 bit process.  Meanwhile, Premiere runs in a 64 bit native process.

In order for these processes to communicate with each other, they rely on TCP IP internally, communicating through 'localhost', which is your local machine.  I don't know why your firewall insists on blocking that port - as far as I'm concerned, it shouldn't.  Your firewall should be concerned about blocking incoming connections from outside ports, not what's going on locally in your machine.

Wil Renczes wrote:

 

...I don't know why your firewall insists on blocking that port - as far as I'm concerned, it shouldn't.  Your firewall should be concerned about blocking incoming connections from outside ports, not what's going on locally in your machine.

hey wil,
no, on the computer without internet connexion there is no firewall. so nothing is blocked. i noticed it on the "internet-computer" that comments any network activity over tcp/ip.
in the meantime i activated tcp/ip on the other computer, connected a lan-cable but nothing changed. it took about 5 minutes to start up premiere (encore, afterFX).
my question: what more windows services are needed? could there be any conflict, when cs5 is not installed at the windows system partition, but on my program partition? is there any .log written when i start premiere?
definitive there is problem with loading "C:\Program Files\Adobe\Adobe Premiere Pro CS5\Plug-ins\Common\ImporterQuickTime.prm". i watched the Plugin Loading.log of premiere, encore, afterFX. what's up there?

Over six minutes for Premiere and After Effects to load this morning.

Did you obtain the information that Harm asked for in post #6?  If not, please do so.  If so, please post it to help us help you.

Until you accomplish all of that, I have one thing for you to check.  I'm guessing blind here, but it's a reasonable guess: Do you have any real-time or full-time anitvirus scanners running?  If so, disable any scan-on-access type of setting and try launching again.

If that fails, then Harm's link is the way to proceed from here.

-Jeff

By any chance are your dual GTX 285 cards configured in SLI mode?

I'm getting a slow start-up too.. I uninstalled Production Premium CS4, installed CS5, and Premiere Pro takes a lot longer to open a Project - maybe a few seconds more to prompt for a Project, but 4 or 5 times longer to open a selected Project. Most of the time after selecting Project is a blank screen. I'm not technical but am interested if someone finds a reason thanks.

Monsieur_Hulot wrote:

 

GRATULATIONS!
got the same (or likely the same) results an my laptop - but not on my PC (win7, 64-bit).

Please follow Harm's suggestion in post number 6 and show us what you have running before you try starting to run Premiere.

@Bill Gehrke : I've tried starting with SLI enabled and disabled; no difference.

@Bill Hunt:  You're correct that the hang is on initialization....there is no tiny text showing modules loading.  All other Production Premium components I've tried start fine (AE, PS, AI ... Encore is disabled in the trial version).  All QT, video, audio drivers are up-to-date. Win7 has all patches installed.

I have CS4 Master Collection. Could that cause a problem?  The only case in which I thought CS4 might be in conflict is with Photoshop 64-bit. CS4 Premiere seems to be working fine.

As I mentioned my machine, with the exception of Visio, Lotus Notes, and AutoCad, is configured identically to 8 machines in a graphics lab.  I'm the fortunate tester for CS5.

Also...task manager shows dynamiclinkmanager.exe loaded using approximately 5500K memory; CS5 showing about 43,000K; CPU usage is 13 (which I'm sure must mean something is wrong

TIA for your help so far.

Norm

dear bill, i thank you very much for your help. but i can't see, how it helps me, when i find out my runnin' processes. i think it's a problem of permissions on folders or in the registry or something like that. for example:
in one of these endless installing/uninstalling procedures i decided to delete every adobe folder on my disks. although i used the flashplayerplugin_uninstall  utility (with admin rights) i still found the folder "macromed" in the "sysWOW64" folder. it was undeleted and i first had to take ownership before i was able to delete.
my solution: i will install a "fresh" windows and pray...

the_wine_snob wrote:

 

QT 7.6.3 & 7.6.4 had issues with Adobe programs, just as 7.5.3 & 7.5.4 did. I had heard that 7.6.6 was a good version, but have to admit that for me, 7.5.5 was the "last known good." Wonder if 7.6.6 is following in the footsteps of its recent predecessors? Maybe try with a copy of 7.5.5.

 

Good luck,

 

Hunt

FINALLY IT RUNS!
my solution was to install quicktime 7.6.6. thx to all the guys here!

Hey geoffwm, have you found the solution for your problem yet? if not here is my solution.

After i've been reading the event viewer on outpost pro and i've found out that you need to Allow All Activity for

premiere.exe and after effect.exe

dynamiclinkmanager.exe ===> 1 for premiere and 1 for after effect

Adobe QT32 Server.exe ====> 1 for premiere and 1 for after effect

for premiere and after effect to work. It worked for me and i hope it will solve your problem as well.

I hope that works for you, but if it does, that's a bug...

You should be able to run with UAC on -- i bet most users here do.

"I cannot comment officially in regards to Adobe Technical Support."

si conehead wrote:

 

I spent 3 hours with Adobe Tech Support and as usual they had no clue.

 

I finally figured out the answer myself.

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

My incident number with tech support is 181615319  if you are able to look at it.

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.