CS4 Premiere Pro really super slow?

[Jason Harris]

OK

I tried to hold my tongue and I DO AGREE he has WAY TOO MANY things running (as for the AE stuff dont sue it so dont know yet on that) but a BASIC encode out of PPro of a 3 minute file (WMV,FLV,AVI whatever) shouldn’t take 20 minutes PER FILE

i know if a pc has slow software and not just adobe its the pc not the program, im in IT so that’s a no brainer

but adobe is slow and clunky, check google for “CS4 slow” and you’ll see the community as a whole believes this!

I know its not constructive to bitch but im hoping adobe will sit up and FIX the issue

CS5 anyone lol

[Tim Kolb]

[Jason Harris] “but a BASIC encode out of PPro of a 3 minute file (WMV,FLV,AVI whatever) shouldn’t take 20 minutes PER FILE”

That’s the point Jason…if you have complex unrendered AE comps on the timeline, it’s a long way from a “BASIC” encode…that AE stuff needs to be rendered. Nobody would think twice about it if AE takes a while to render something complex, but when that same comp is dynamic linked to the Premiere Pro timeline, for some reason some people forget that that rendering still needs to be done.

TimK,
Director, Consultant
Kolb Productions,

[Jason Harris]

tim i know that

I WAS referring to a project we were doing, is a simple series of clips, with some basic PREMIERE transitions, no fancy dynamic links, im sure if adobe chokes on something like that it probably ROLLS OVER DEAD for any complex dynamic linked stuff, tryed the dynamic links ourselves and its very buggy to say the least, we have backordered a copy of CS3 from our vendor, i hope it speeds things up!

[Mr Ed]

And let me add… it had at least 7 dynamic links AND one of the links had some major 3d going on… with tons of layers, levels, plugins and the whole sha bang…

I love ADOBE products… I hope the sponsor me someday! =) Anyway, It was a computer issue I believe and not a software issue.

Here is the final if your interested: https://www.massmediamail.com/wyd/new – There was ONE LITTLE glitch at the end but I have to make some edits anyway and that can be re rendered. =)

Thanks for all your comments.

[Tim Kolb]

[Jason Harris] “I WAS referring to a project we were doing, is a simple series of clips, with some basic PREMIERE transitions, no fancy dynamic links”

Can you describe the sequence in detail? …and also the steps you’re taking when you render/export? Maybe there’s a way to solve the issue.

Also…I noticed you mentioned XP… technically of course, XP64 is not supported. I’m told there is no real reason it shouldn’t work, it’s just that it isn’t tested.

XP32 will be a bottleneck with CS4 without question as the RAM limitations are pretty restraining. I’m actually adding another system drive to my machine and adding a Vista boot partition so I can access more RAM. Adobe has two major intolerances: 1. Running out of RAM; and 2. Data starvation (slow drives, corrupt media, etc.)

Vista 64 may be a pain for a variety of reasons, but with the added access to RAM, Adobe CS4 (and even CS3) do run better in my experience.

TimK,
Director, Consultant
Kolb Productions,

[Mr Ed]

I am having major issues with my computer so its not adobe. I don’t know whats going on. Maybe I have a viurs or something. Even as I type this can’t keep up with my fingers and all I have is firefox open and runing a viurs scan.

I hope to fix this asap. Any thoughts on what might cause this? Quade Core…12 gigs of ram… it should not be this way. =(

[Jim Leonard]

“it had at least 7 dynamic links AND one of the links had some major 3d going on… with tons of layers, levels, plugins and the whole sha bang… “

Yes, that is the problem. Any incredibly complex sequence probably should be rendered so that you’re not re-rendering it all the time. Dynamic Link is good for sequences that your computer can handle — it is not meant to be used for everything.

[Fred Grasset]

Hi,

It turns out that PPro Cs4 is the culprit for the slow slow render. I imported some MXF files into cs4, like I do twice or three times a week and I wanted to render from 720 24p mxf to 360X640 h.264 mpeg4. Everything seems pretty banal to this point, I know that the render would take 15 to 35 minutes for a five minute clip. So I happily added to the Media Encoder a queue of 8 – 5 minutes clips. I Left the computer alone and went shopping. Come back two hours later and check on my render queue….Gosh it says 8 hours and 35 minutes to render the first clip of 8. I immediately stop the rendering. Bouhou! My machine is broken. After defragging, hours trying to remove all the non-essential processes for winbdow XP -Yes the CPU was going 100 % all the time , relocating all the file on my internal HD, it done on me to check the similarity between this week rendering and last week rendering. Bingo! I use the color correction RGB in the premiere pro effect bin for the latest rendering. This was my bad boy and now that I have removed this effect I can happily render ever after in 20 minutes or less because of everything I learned thru your fabulous website. Software can be a problem. Beware.

[Bill Gorman]

My Adobe Premiere Pro CS4 is playing about one frame every ten seconds and saves the same way, my videos play just fine with any other program. Running on WIN 7 with 16 GB RAM, Intel Quad Core i7. No excuses other than Adobe caters to Apple and does not give a dam about their Windows customers. I will never buy another Expensive Adobe product is this is how they show their appreciation for buying their crappy products. If I need a new editing program I will go with Corel. All update are installed and all drivers are up to date. Only thing I can figure is the last update intentionally sabotaged the software in an attempt to force CS4 users to upgrade, but then, I see others with CS5 & CS6 complaining of the same issue.