Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro a rotten project

  • a rotten project

    Posted by Ayala Sharot on July 7, 2011 at 11:13 am

    Hi Guys,

    Once again, I need your advice.
    I’m working on an animatic for an animation film. My computer is powerful (i7 CPU Q740 @1.73 RHz, 6GB RAM with a 64bit Operating system) and the files I’m using are rather light (lots’a jpgs, and some widescreen PAL, no heavy HD footage or anything of the sort).
    The work is incredibly slow as any simple command takes more than a couple of minutes. There’s no problem with my other premiere projects.

    I tried to re-save it, I collected the files to a new location but it didn’t solve the problem.

    The project’s files are rather messy: it’s got many sub-folders and other projects I imported. could this be the cause?

    Does anyone have an idea about how to fix it or find a way around it? I’m rather desperate, I’m even considering switching to final cut (btw – is there a way to convert a CS5 premiere project to fc?)

    Will be happy to supply more info about the settings, just tell me what should I check 🙂

    Thanks a lot,
    Ayala

    David Dobson replied 14 years, 10 months ago 2 Members · 5 Replies
  • 5 Replies
  • David Dobson

    July 7, 2011 at 5:08 pm

    Yikes!
    If there are lot of really big files, 300dpi @ more than 3000 pixles, that can really slow things down. Sometimes even one can be a problem. Resize in photoshop to 72dpi (and adjust the pixel size back to something bigger than you need.
    Also, i have found that Premiere really dislikes CYMK files, so remove those and/or replace them with RBG versions.
    Maybe that will help. But if other projects are working fine, then it’s definitely a source file. And it doesn’t even have to be in the timeline to cause problems. Might also be a good idea to go through all the photos and see if any are damaged

  • Ayala Sharot

    July 8, 2011 at 9:23 am

    Thanks, I’ll give it a try.
    I don’t have any big files and I think there aren’t any CMYK files but it would be good to eliminate the option that there’s something wrong with one of them.

    If that doesn’t work, are you familiar with a way to export some sort of a log file and try to re-build the a new project based on my old edit?

  • David Dobson

    July 8, 2011 at 2:42 pm

    First you can try to open the project from within a new project. So if there is something wrong with the project file, this may ignore that. You could also export an XML, then import that into a new project and then relink only what you need. You could also try consolidating the project and see if that one runs better.

  • Ayala Sharot

    July 9, 2011 at 5:50 pm

    Thanks!
    I’v etried consolidating and also tried to open it from a new project but both were just as slow. But exporting the XML sounds promising. I’ll give it a try.

  • David Dobson

    July 9, 2011 at 6:52 pm

    Sounds like a memory leak. I had a project (one I am still working on) where sometimes the system was really slow. CTRL-ALT-DEL to check on system resources and ALL of the memory is being used up (but Premier is only using 3MB). Eventually, it stopped happening. This project had dynamic links to AE.

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