-
My update on PPro2 / Hardware blues
I’ve moved back to PPro 1.5 for the present.
About a month ago, I reported some strange issues related to PPro2 and glitchy video. Any scroll or even a lower third overlay would cause the rendered video in that overlaid area to be jumpy. The scroll would jerk around, even after rendering. The AVI file created as a result of the edit would be jumpy as well.
I went to Adobe for support and they had me re-install PPro2. No change. They then instructed me to re-install XP. They said that if I did everything as instructed and still had a problem, it was a hardware issue.
I located a usable 80gig drive and installed XP and the production suite. I figured that the 30 day leeway before registration of both products would give me ample time to test things out. Guess what, no change. Even on the new install of XP AND Production Suite with PPro2, the same results occurred. So I gave up assuming my video card, RAM, or CPU was faulty.
I figured I’d use the computer upstairs with Premiere 1.5 to meet my deadlines while saving my pennies for a new video card (which I thought was the most likely candidate.) The upstairs PC worked fine and after bringing the TV show back to life in PPro 1.5, I was able to meet my deadlines.
On my main computer downstairs, I had removed the temporary XP/Production suite 80gig and was back to my regular system, unable though to use PPro2. In the process of doing the show and other projects, I ended up putting things together in PPro 1.5 downstairs, thinking I would end up rendering upstairs on the computer that worked. So I’m working away and turn out the show. Everything is fine. Then it hit me. I had both created and rendered the project on my downstairs computer in PPro 1.5 – AND IT WORKED. Now don’t ask me why I didn’t try that before. I’d be forced to make up an answer that didn’t make me look as stupid as I felt when I figured out the obvious stuff I should have tried but didn’t.
So it boils down to this. On the same computer that gave me jumpy, unusable videos when overlaying titles or basically any segment that had to be rendered in PPro 2, things worked great when produced on Premiere Pro 1.5. Same computer, same everything. Premiere Pro 2 is broken, Premiere Pro 1.5 isn’t.
I’m not sure this would qualify as an educated guess but let’s just call it a plain old ordinary guess, here goes.
I think that PPro 2 uses the video card in the render process where 1.5 doesn’t. If I could figure out how to turn it off, I would. But the fact is that I don’t really know this is happening anyway, I’m just guessing. If true, then a swap out of my video card would likely fix PPro 2. Since 1.5 works, I don’t think RAM or CPU are the problem. If it wasn’t getting close to Christmas, a new video card would have already made it into the computer.
Now, to anyone that’s had the stamina to read to this point in the post, I would be very interested to hear (1) your insights to my dilema and (2) how to get this to Adobe without spending the time and money it takes to get their attention. (By this I mean that they don’t have to provide free support, and I don’t want to invest more money and time just to get their attention.)
Thanks, I’m listening.
Ron from Maui -
3 Replies
-
Why don’t you list your system specs? CPU/MoBo/videocard/soundcard/harddrives and their configurations/Perifs/other software/other uses/ etc…etc.
-
I would suggest the video card plays a big part in PremPro 2 and may have even be documented. There is definitely the option to use GPU acclerared effects or two other options. A top end video card is advantageous in PremPro and many of the plugins are written for them. eg MAgic Bullets
Is your card on the approved/tested hardware list?
I am not sure what your original issue was but try using PremPro with playback settings as Compatible (not GPU Accelerated) using your current card.
Craig Howard
Shooter Film Company
Auckland
New ZealandPremiere Pro 2.0
-
Your jumpy video could be that premiere is confused about which FIELD it is sampling first, this sounds like a similar problem i have but my work around is to open the capture window then close it back and that usally fixes the problem.
Reply to this Discussion! Login or Sign Up