CS4 – Dynamic Link is Slow and other joys

[Tim Kolb]

[ninetto makavejev] “It is hard to determine just what Adobe was refering to with the “8-12% performance gain” with 64-bit comparison, since there is no 64-bit version for Mac.”

I agree with that…though I don’t believe the Windows version of CS4 is 64 bit either…and that is precisely my point. We’re talking about two different things here, regardless of the Mac/Windows hardware similarities, Adobe is talking about whether or not CS4 takes advantage of Mac’s 64 bit architecture, and we’re talking about OS’s…

Your system may be very possibly seeing 3.5 Gigs, but on XP 32 that is a hack…there is a line of code you can change to get it to do that. My system integrator didn’t have a lot of confidence in that hack after they messed around with it, so I’m staying safe.

Vista is a can of worms, and I’m still hesitant, but on the Mac side, you can have 16 GBs of RAM and use it all. CS4’s performance with multiple apps open will improve markedly with a seriously large RAM availability.

So the RAM aspect of the conversation is what keeps me torn between XP…Vista…and just getting another Mac.

TimK,
Director, Consultant
Kolb Productions,

[Mike Cohen]

does XP’s virtual memory add any punch to CS4? I let Windows manage the page file on the system drive only.

Mike Cohen

[Mike Cohen]

the conforming of HDV files seems slower than in CS3 also – can’t do much of anything while this is brewing

[Alex Udell]

Hi Guys…

Modifying the Boot.ini file in XP is pretty standard fare for a lot of Editing systems that run on Windows. In fact, Matrox actually automates the process as part of their standard install, so I wouldn’t let that scare you too much.

As far as I know…

Under a 64 bit Vista, PPro (even CS4) will still be a 32 bit application, meaning that it won’t address any more than the 3.5 available to it. The benefit comes in the fact that if you have more ram installed, each of the apps, like AE for example can access their OWN banks of 3.5 GB, so they are not competing with each other and having to use the Swap file. So it should make things run a lot more smoothly with the integration.

We are awaiting Matrox to release the drivers for RT.X2 over here before we move forward to either CS4 or Vista. I may download a trial or two to starting learning new features prior to deployment, so we can hit the ground running.

Hope that perspective helps a bit.

Alex Udell
Editing, Motion Graphics, and Visual FX
Younversity TV
http://www.youniversity.tv

[Tim Kolb]

[Alex Udell] “Under a 64 bit Vista, PPro (even CS4) will still be a 32 bit application, meaning that it won’t address any more than the 3.5 available to it. The benefit comes in the fact that if you have more ram installed, each of the apps, like AE for example can access their OWN banks of 3.5 GB, so they are not competing with each other and having to use the Swap file.”

As far as I understand it, this is exactly the case…

Looks like Jan Ozer did some comparisons and the difference for some tasks is relatively significant.

https://digitalcontentproducer.com/affordablehd/newsletter/cs4_64bit_1208/

TimK,
Director, Consultant
Kolb Productions,

[Ninetto Makavejev]

Dear Tim Kolb,
thanks much for the reference to Jan Ozer’s article, this should really be required reading!

64-bit, here I come, but I think it will have to be a Mac. I have no desire to wade thru the jungle of Vista-drivers out there.

regards, ninetto

[Tim Kolb]

[ninetto makavejev] “64-bit, here I come, but I think it will have to be a Mac. I have no desire to wade thru the jungle of Vista-drivers out there.”

Yeah…something tells me you’re not alone…

TimK,
Director, Consultant
Kolb Productions,

[Ciro Coleman]

Hi Tim,

Hope you can help me? I’ve just got Adobe Premiere CS4 and am having the error message “PProheadless.exe” failed when I go to render a sequence. The Media Encoder works fine on its own but will not import a saved sequence even from within the sequence’s own folder. (as mentioned in your thread)

I’d uninstalled my other Adobe products, flushed the registry etc, updated DirectX and .Netframework as some others had advised before reinstalling and trying again.

I’ve been to an Adobe Forum and most of the answers are, well, no answers as they seem to be shooting into the dark on a trial and error basis. My question is:- how does one fix the problem? Why is it happening? Is there something missing or something impacting the system so the link is not being made? Is the file corrupt? If so, how can you find out?

I’m looking for a cogent answer that tells me . . . you have to do this or having such and such a program is interfering with PProheadless.exe that then causes it to crash and you need to do X, y and Z to remedy the problem or . . . etc etc?

Any sound advice will be greatly appreciated

thanks

Ciro Coleman (UK)

[Tim Kolb]

That specific issue is new to me… But I know in my case, I was running Panda AntiVirus and that had some simply insurmountable conflict with PPro CS4 and I had to get rid of it…

What are your machine specs?

Is this one sequence, or have you tried with a fresh PPro project and a simple one clip sequence just to confirm that the problem is not related to the one sequence?

What is running on your machine when you start up? I had to axe QT updater (which spontaneously saps 40% of your processing power whenever it feels like it) and the AntiVirus… There may be others that create some sort of problem.

TimK,
Director, Consultant
Kolb Productions,

[Ciro Coleman]

Hi Tim,

Thanks for your response. I have, fingers crossed, seemingly fixed the problem.

In the Windows’ Error report I clicked the ‘details’ button and found that it pointed to – nvoglnt.dll, which, after some ‘googling’ pointed to Nvidia graphics drivers. I downloaded a nvoglnt.dll file, and replaced the one I had in Windows\system32. The one I had originally was just over 3 megs and the one I replaced it with just over 300 kilobytes. I loaded Premiere and waited with baited breath whilst Media Encoder loaded. No warnings came up and I rendered the sequence successfully. Hoorah!! I also opened Media Importer on its own and imported a sequence and voila, it, too, rendered.

I would probably guess that any others who have the same problem may be able to do the same thing and replace/update whatever file the Error report points to albeit may not be just Nvidia.

Whether this is the only cure would be a matter of having a totally ‘clean’ computer and adding and testing one thing at a time starting off with the updated file in the Error report. Hope this a help to any others seeking a better explanation to the solution of how to fix the PProheadless.exe problem.

regards

Ciro