Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Premier Pro problems Plulling my hear out

  • Premier Pro problems Plulling my hear out

    Posted by Charles Rudolph on March 23, 2012 at 2:48 pm

    Hi all im a PC user and im having a tuff time with Premiere Pro 5.5,I edit HDDSLR footage from a 7D and im having constant crashes and poor performance. I have read every forum and blog I could have I have did many clean installs and still nothing. Using my footage natively is worst and transcoding to avid DNxHD is better but still slow I know its a better way. Im posting my Pc specs in pics: GTX 285, SSD,raptor,core I7

    Al Bergstein replied 14 years, 5 months ago 3 Members · 7 Replies
  • 7 Replies
  • Angelo Lorenzo

    March 23, 2012 at 5:56 pm

    Interesting, I have relatively similar specs to you but beefed up to an i7 2600 running at 3.8gHz and 32gigs of RAM (overkill for Premiere but I use AE a lot) and I’m working on 4K footage without a hiccup. My previous system ran under your spec a good bit (AMD Phenom quadcore and 8 gigs of ram) but I was editing 5D and 7D footage all day long.

    In Premiere, go to Preferences > Media. Is your media cache set to your SSD? If you’re hitting against low space issues, this would be my next guess.

    What do you have going on as far as background processes? Are you running any resource aggressive programs like Norton AV?

  • Charles Rudolph

    March 23, 2012 at 10:43 pm

    Thanks for the reply..I followed a video 2 brain workshop on After Effects & Premiere Pro Performance Workshop and made sure I had three fast hard drives. I know my computer is up to par and all people can say is I should be using a mac which I think is bull. What GPU do you use?

  • Angelo Lorenzo

    March 23, 2012 at 11:05 pm

    I use an overclocked GTX560 with 2gigs of DDR5 from EVGA. Not officially supported but it works through the text file hack and it’s stable performance-wise.

  • Charles Rudolph

    March 23, 2012 at 11:14 pm

    PC or hackintosh and what do you transcode to?

  • Al Bergstein

    March 24, 2012 at 1:31 pm

    Charles, I too use Pr in a similar configuration on W7 (and also run on a Mac Pro at times), I shoot on a 7D and have not had any problems with crashing under the 7D footage. I just edited a 12 minute video that was over 2 hours of raw footage. I suspect something with the hardware not the footage, though you could try transcoding as mentioned above and see if things change.

    When you say you are ‘crashing’ does that mean that you are having a Blue Screen of death or is Pr simply crashing on you and you can restart the project? As you might know, BSOD’s are usually hardware related these days. Occasionally they are graphics card software. I’ve found problems with latest versions of nVidea drivers. I didn’t see if you were running dual monitors on that one card, but if you are, fall back to one monitor and see if it helps. I’ve come to the conclusion, through trial and error, that dual monitors on one lower end card, leads to more problems than it’s worth (that was through troubleshooting Sony Vegas installations, not Pr). I recommend to friends that they get two cards for two monitors, if they aren’t running high end cards.

    The only crash I’ve experienced on W7 under Pr in the last few months, was when I was using a couple of video players open at once, (viewing clips outside of Pr while working on other stuff inside Pr), something didn’t work together well. Have had more problems on my Mac Pro (G).

    I too would recommend that you look at your antivirus software. After troubleshooting numerous problems for friends and seeing Norton cause them, I’ve gone over to Microsoft’s antivirus Security Essentials. It seems to do the job with the least amount of grief. Check out what services are running to see if something odd is in the background processes.

    I also assume you have your footage on one of the external drives and your program on your SSD along with your OS. Make sure that you don’t have some kind of hard drive ‘sleep’ program (common on newer ‘green’ drives), as I think that drives coming out of sleep may be causing some problems for video editing.

    No need to go the Mac, though I’m a fan of it as well at times, but Pr seems to be the most rock solid package I’ve used on Windows. Wonderful to see all the cores cooking away when rendering, etc. And there are plenty of issues with the Mac too, as other posts on these forums show…

    Al

  • Charles Rudolph

    March 24, 2012 at 11:31 pm

    Thank you for your reply. When I say it crashes i mean when I hit enter to render it freezes, and say for instance I use a MB plug-in like Colorista it freezes. I hear a lot of people say they can edit natively .mov in Pr but I have had this computer for 2 years and always seem to be sluggish or had to turn playback to 1/2. I like living on the edge so I don’t have any antivirus other than Microsoft’s antivirus Security Essentials thur windows update and I dont have any thing running other than Pr. Looks like a long weekend at the drawing board 🙁

  • Al Bergstein

    March 25, 2012 at 12:45 am

    Ok. Got it. So to be clear, you can *edit* the footage ok, but when you go to *render* it freezes? Do you mean when you render it without sending it out to be queued? Has it *ever* worked right? Where are you rendering to, which drive? I always use an empty drive other than the one that holds the footage, and the program (i.e. if the program is on C, and the footage on D then I render on different drive).

    Have you tried rendering anything other than MOV files? Is it just MOV?

    Has any of this started since you added the SSD?

    Do you have RAM settings changed, or somehow different than *normal*?

    Does it freeze when you are just working on editing?

    And when you say it freezes, it just doesn’t go into a long running process, but it actually freezes the computer entirely???

    Sorry for the questions, but just trying to help you isolate the problem.

    Make sure you have plenty of disk space on the drive you are rendering to.

    Since so many of us are working fine with a similar configuration, I personally would start by taking a spare drive, cloning the SSD drive (your OS drive) via a cheap eSata dock, and replacing the SSD with the cloned *non SSD* drive. That would eliminate the OS drive as the cause, with minimal fuss.

    Good luck!

    Al

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy