Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Adobe Premiere Pro CS3 crashing when exporting to MP2

  • Adobe Premiere Pro CS3 crashing when exporting to MP2

    Posted by Jeremy Paterson on June 23, 2008 at 1:43 am

    MY PROJECT:

    26 hours of HD footage captured from Canon XH-A1. My system/project specs are:
    – Intel Quad Core Q6600 2.4Ghz CPU
    – 2Gb RAM
    – 4 X 500gb SATA 2 Drives
    – At least 80 GIGS of head room on each drive
    – Windows XP
    – 25P
    – Project located on C:
    – Media Cache files located on D:
    – Project video files located on K:

    I am trying to export my 96 minute project to XP 2. It generally reaches Phase 2, but then either:

    a) Crashes with generic error message “has encountered and error and will have to shut down”
    b) Shuts down without an error message
    c) Freezes

    I have spent literally days of my life waiting around for this, and yes it has reaches as far as 80% on phase 2 (which took approximately 7 hours or so to occur) and then the program crashes.

    Any suggestions? I have made a new account for Windows hoping this may help.

    Cheers,
    Jeremy.

    Tim Kolb replied 18 years, 2 months ago 5 Members · 8 Replies
  • 8 Replies
  • Jon Barrie

    June 23, 2008 at 4:33 am

    If you are trying to use the noise filter with export it’s so not worth it you will be waiting a lifetime and then it might crash. 96 minutes on a Quad Core shouldn’t take days. Plus 96 minutes should fit onto a single layer disc at a CBR rate only needing to render through once. Look online for an MPEG2 calculator. I’d say 7Mbps would work.
    Also do you have any images in the edit? They might be too high res causing problems.
    Worst case export AVIs broken up and put them back together in a new project then export that for MPEG2 should be about RT then.
    – Jon 😉

    How many editors does it take to change a light bulb?
    http://www.jonbarrie.net

  • Vince Becquiot

    June 23, 2008 at 4:47 am

    While I can’t tell you the cause of the issue, I can tell you I would pick a different route instead of pulling whatever hair I have remaining.

    Try an uncompressed export instead (AVI or QT animation). Then re-import to a clean timeline and try the mpeg2 again, or use AE if you own a copy. You could also take the uncompressed file directly to Encore or whatever application you use to burn to DVD.

    It couls alo be a corrupt file, or heck, how about a clean OS install ?

    And if none of that works, well I hope you are close to retirement…

    Vince

  • Jeremy Paterson

    June 23, 2008 at 9:35 pm

    Hi, sorry how do I go about doing this without losing quality in the final MP2 file? What specs should the project be that I import the AVI files into?

    Cheers…

  • Vince Becquiot

    June 23, 2008 at 11:06 pm

    You will not lose quality as long as you use a lossless codec. I would recommend Quicktime Animation at 100%, as it will yield to a smaller file size than AVI. The specs should be the same as your project all throughout.

    Vince

  • Dan Asselin

    June 24, 2008 at 2:30 am

    It only takes 1 editor to change a lightbulb…..IF…..he can get the darn producer to make up his mind as to what bulb has “the right look”

  • Dan Asselin

    June 24, 2008 at 2:33 am

    Try these 2 items which have worked for me in PP3

    Make sure you pre-render on the timeline (I know that’s a no-brainer but sometimes we forget.

    Render the Audio separately from the video. I don’t know why the second one works but it does.

    Good Luck;

    Dan

  • Jeremy Paterson

    June 24, 2008 at 2:49 am

    Thanks Jon, Dan, and Vince, they are all great suggestions and I will give them a go…

    Fingers crossed!

  • Tim Kolb

    June 25, 2008 at 4:56 pm

    I think you want to try to export shorter and shorter ranges from the timeline and try to zero in on just what point might be causing this…

    Often, PPro chokes on trying to buffer up a really huge still on the timeline…or you could have one particular piece of media causing the issue. these types of crashes do happen under such circumstances.

    I’d look there first if it was me…

    TimK,
    Director, Consultant
    Kolb Productions,

    CPO, Digieffects

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