Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Premiere Crashes are killing me!

  • Premiere Crashes are killing me!

    Posted by Joseph Russell on July 3, 2008 at 4:35 pm

    To anyone that can help,

    My situation is this:

    I am editing a 25min HDV project in Premiere pro 2 and the instabilty of the program is making it a nightmare. Everytime I open the project and edit for a while Premiere Crashes (Premiere’s memory usage at time of crash is usually around 1.2G)I think it is a memory leak but I just cannot find the source of the problem. I followed all of the Adobe suggestions to no avail, so I bought an entirely new system but the problem seems to have followed me to the new computer. I have tested my RAM and it is fine, Tested my HDDs, I have removed third party plug-ins, set my virtual memory correctly, started Premiere holding shift, copied the contents of one project to a new project, checked all my footage for corruptions, updated all drivers etc. etc. etc. but nothing seems to work. My project contains roughly 500 clips most of which are color corrected, some slowed to 50%, with a few titles and all in Cineform HDV Codec.
    For the last few months I have just worked with the constant crashing, but now that I have it complete, it is impossible to export to any format due to crashing and my deadline is fast appraoching. PLEASE HELP ME!!

    SYSTEM:
    Athlon 64X2 dual core 4600+
    ASUS M2N-sli DLX Motherboard
    2GB DDR
    GF 8500 GT Video Card
    Windows XP SP2
    Adobe Premiere Pro 2
    Cineform Aspect HD V5.3
    Magic Bullet Editors Plug-in

    Joseph Russell replied 17 years, 10 months ago 4 Members · 4 Replies
  • 4 Replies
  • Tim Kolb

    July 3, 2008 at 7:50 pm

    Please try this:

    Uninstall CineForm Aspect/Prospect

    Download the CineForm NEO playback utility (free) and install it.

    Create a project with custom settings at the proper framesize, etc (you could check your current project settings and note all of the specs other than the codec/compression type), but set compression to ‘none’.

    Open the new project and import your existing CineForm project into it. It will show that the material needs to be rendered, but you should be able to work with it albeit a bit more slowly.

    See if you can’t get some run time out of this arrangement at least to finish your project.

    TimK,
    Director, Consultant
    Kolb Productions,

    CPO, Digieffects

  • Mike Velte

    July 3, 2008 at 8:42 pm
  • Lance Bauerfeind

    July 3, 2008 at 9:02 pm

    I trust this is not too late for you.

    I have had all the issues you are talking about a couple of years ago, so it was using 1.5.

    The problem I found was that it is premiere. The general rule is to keep your project to below 50mb. If you have 2 gig ram then 1.2 will certainly max it out. Colour correction increases file size.

    The solution that worked for me was to break it right down in to a number of smaller projects export those as avi’s then have a master project which has the avi’s only. Each one should be about 10 min max in length.

    In the archives would be a thread regarding this whole issue. I haven’t read or heared that Adobe have solved this issue as yet.

    Lance

  • Joseph Russell

    July 4, 2008 at 3:48 pm

    Thankyou Tim, Mike and Lance for your suggestions. I have taken them all on board and along with some suggestions from other forums I have come up with an acceptable work around. It is as follows:

    I cleared out all unused clips and timelines from the bin to reduce the size of the project dramatically,

    Deleted the Magic Bullet plugin and all reference to it.

    Rendered slow motion effects and titles in After effects to take some of the load off premiere

    And I installed Mem turbo RAM Mangament utility (I will also try the one you suggested Mike)

    So far these this has enabled me to render out my project successfully and with any luck I will be crash free on the next episode.

    Thanks again,
    Joe

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