Skip navigation
(Michael_Neborak)
Currently Being Moderated

Adobe Premiere Pro CS4 Hangs On Startup

Feb 13, 2009 5:19 PM

I have been working on a project in Premiere on a Mac with OSX (16GB RAM, Eight-Core Processors at 3.0gHz, 1TB storage) for multiple weeks now and I was just about to render. I replaced some of the lower quality video files (R3D files from the Red One converted to mov files) with the higher resolution version. When I tried to open up the project in Premiere after that, the progress bar got to 95% and then the entire program stalled. I could cancel the loading of the project, but I still had to Force Quit the program as Premiere became entirely unresponsive. I tried creating a new project and importing the old one, but I get the same results. Please help as this needs to be done soon and I don't have time to re-do all my hours of editing.

Best Regards,
MLN
 
Replies
  • Currently Being Moderated
    Feb 13, 2009 5:27 PM   in reply to (Michael_Neborak)
    Try creating a new project and importing the old one into it.
     
    |
    Mark as:
  • Currently Being Moderated
    Feb 13, 2009 6:11 PM   in reply to (Michael_Neborak)
    Walk away for about five or ten minutes then come back and see if it is still stalled. I've seen this happen sometimes when Premiere is relinking files that were offlined.
     
    |
    Mark as:
  • Currently Being Moderated
    Feb 13, 2009 8:03 PM   in reply to (Michael_Neborak)
    Run the activity monitor and see which app is locking up. There are several separate ones which together comprise PPro.
     
    |
    Mark as:
  • Currently Being Moderated
    Feb 17, 2010 6:37 PM   in reply to Bob Ramage

    Thanks Bob,

     

    From the activity monitor it looks like ImporterProcessServer is hogging 99% of the memory but not necessarily locking up - it's not red. Does that help? Do you want a screen shot?

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 17, 2010 6:54 PM   in reply to tim_0000

    Have not seen Bob around for a bit, but hopefully he's still around. He's got an X-platform shop, as I recall, so knows "both sides of the street." I could have suggested similar, but it's ONLY on the PC. Glad you found this one, as I now have learned a bit more about Mac's. Sh-h-h, don't tell the PC-community.

     

    Now, there are many threads, both here and on the Creative Cow, about ImporterProcessServer. IIRC, it has been a bit of culprit for PS, PrPro and AE too. Hope that there are some useful tid-bits in there, or that Bob stops back by.

     

    Good luck,

     

    Hunt

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 17, 2010 7:29 PM   in reply to Bill Hunt

    Fixed but not solved.....

     


    Thanks to Bill and Bob - I searched for ImporterProcessServer posts and found one that said that turning off and on your machine usually solves any issues. Yeah, I know it's tech support 101 but hey sometimes the most obvious answers! So seeing as it was the simplest solution I tried it and VIOLA!

     

    So yes Premiere is working again! I was able to open the project I was working on - so no corruption with the original file.

     

    So I guess the question is what the hell happened??? Why did premiere crash out of nowhere and then refuse to open???

     

    I guess the answer lies in the mysteries of the ImporterProcessServer....

     

    So big thanks to Bill and Bob!

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 27, 2010 5:32 PM   in reply to tim_0000

    I'm having the same problem with premiere pro it will load up to about 95% and stop, it dosen't shut down though. I have a deadline fast approaching I looked at my activity monitor but I'm not sure what im looking for and what to do to get this program back up and running...... can anyone help?!!

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 11, 2010 7:02 AM   in reply to noptra

    I found a fix for my similar problem.  PProCS4 would load but freeze ("Not Responding") when loading any project.

    Through weeks of trial and error, I discovered it was a background program loading in the 'startup' section of MSCONFIG.EXE that was conflicting.

    In my case it was OmniPageSE2.0.  Disabling that in MSCONFIG allowed PremierPro and Encore CS4 to work for me again.

    Maybe you have a different program interferring with PPRO.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)