Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro CS4 large HDV project on Vista loading problems

  • Mahmud Lund

    July 18, 2009 at 9:05 am

    Eric, hello,
    I am not sure what you mean by closing sequences.
    In the original project which ultimately got corrupted I had many sequences on the timeline, maybe 30 to 35. I thought I could have all the material for the project on hand, given the system specs, i7 cpu, 12 Gb RAM, multiple drives for project, video, previews, etc. That failed.
    I couldn’t afford to waste any more time trying to get that way of editing to work and shifted to selectively importing just those files I needed. I still have five or six sequences on the timeline.
    So, how do you close a sequence?

  • Peter Berthet

    July 20, 2009 at 12:50 am

    unfortunately thats the method id recommend going with too,
    on large projects ive often had to selectively edit small amounts of media rather than bring everthing in (which i prefer) and doing it all at once

    it (CS4) just seems to hit a brick wall when you have loads of media and sequences in one project 🙁

    ~Peter Berthet
    Sydney, Australia

  • Tuncay Erol

    July 20, 2009 at 12:51 pm

    did you try the one of the auto save files.
    in the “Adobe Premiere Pro Auto-Save” folder

  • Mahmud Lund

    July 28, 2009 at 9:36 am

    Tuncay,
    Thank you for the suggestion.
    I was not seeing the forest for the trees. I followed your idea.
    That worked for me, in that I could at least recover the settings for the trailer by selecting offline all the auto save file loaded, i.e. with no actual files but the accurate editing details.
    From there I could load the necessary HDVSplit captured files one by one and get back to where I had been.
    In the meantime, I am slowly learning to work with CS4.
    As others have mentioned I find the forced detour through AME truly disappointing for such as audio, stills and avi generation instead of the old combo keys alt+M, etc.

  • Gedas Shulcas

    October 3, 2009 at 1:35 pm

    Hello, i have got quite the same problem i think… Two weeks ago i have started my documentary film project in premiere cs4. everythings goes well… but one day i try to start my project (save) and loading of proj lasts 5-10x longer… proj opens but then need to wait when all data will be uploaded, and in this time premiere goes very slowly too and finaly stops working. i tryed open 1-4days old proj save – its the same…
    I try to open other projects’ save , they work normaly….
    Tryed to import sequances to now project, its dont work too. PR working rly slowly and come notresponding….
    now i am doing disc defragmentation (got some advice ;D )
    Can u give me some adive, solution?

  • Mahmud Lund

    October 4, 2009 at 12:40 pm

    Well, the way I am working with CS4 now is not what I consider the way it should work. But the time lost in trying to do things that are seemingly destined to finally crash is better spent doing successful work-arounds. In this case, one forum suggestion that seems to help is to immediately close timeline sequence panels when you are not actively working them.

    Break your project up into a number of sequences and keep open only the ones you are using.

    I have some 35 HDV tapes which I keep each one in its own sequence timeline. That way I can open the HDV files as required. Trying to have too many sequences opened leads to the kinds of things you are experiencing.

    In order to close the sequence I think the the command is: panel close [my email computer is not my editing computer and therefore I can’t remember the exact English menu command] but rightclicking on the sequence timeline tab opens up the options and you should figure it out from there.

    My CS4 is running on a pretty powerful i7 system with 12 Gb of RAM (but since Premiere Pro CS4 is still 32-bit it only uses 2Gb) and large 1 or 1.5 Gb dedicated SATA harddisks for program, project, video and previews. I still suffer from white screens, and other unexplained periods where CS4 simply stops responding. I now just wait the seconds or sometimes a minute for the problem to resolve itself. It causes less headaches for me at the moment.

    CS4 also fails to hold video and audio in synchronisation over long time lengths with *.m2t HDV captures so I use shorter HDVsplit captured files. Even then without any explanation every so often when CS4 imports the file it sets the 100 frame per second flag on a particular capture, even when the exact same file will play back correctly as 25 frame per second (I am in PAL land) using VLC or even Premiere Pro 2.0 !!! Proving that the anomaly is within CS4. Where this flag gets erroneously set and how I don’t know.

    I hope this has been understandable to you and some sort of help.

  • Gedas Shulcas

    October 4, 2009 at 2:49 pm

    plus minus i had known about this stuff. This info realy can help make faster your work-flow. But the problem is, that i cant start my project, i cant make any changes in project (delete sequances or other unnecessary stuff) to make PR work faster with project. PR just stop working in the way of starting (loading / uploading all data files). Tomorrow i will reinstal PR and delete all cashes files and let PR to rebuild project. What u guys think about it?
    I have some unfinished project too, can this reinstalling make influence of my others projects? Actualy it shouldnt . yes? But as i know PR as unstable program so i keep in my minds that there can be few percents that reinstalling can influence .

  • Mahmud Lund

    October 5, 2009 at 12:32 pm

    The only two suggestions I could offer, which it isn’t clear to me whether you’ve already tried them or not, are:
    1. go to the Premiere Auto-Save folder and try to recover your project from the project files automatically saved there. Auto-saved projects are in a folder located where your project files are also located.
    2. open a new project with the same properties, i.e. format, etc. and then import the original project. You are given the option of importing the whole project or just sequences. Also, you could use this importing option with an auto-saved project file, work backwards if necessary from the most recent to find out where the project file corruption began.

    Once you are able to either recover or re-open your original project, even if it means you lost some work, save it with a new name and you might try the method mentioned in the previous post, i.e. closing sequence panels to limit the amount of material that premiere is dealing with.

    Hope that helps. Let us know how it works.

  • Gedas Shulcas

    October 6, 2009 at 9:13 am

    i had been tryed this before. it didnt help. Now with that pc (and problem), there is working other man. I’ll inform u later if we’ll find any solution…

  • Gedas Shulcas

    October 12, 2009 at 7:51 am

    well… windows and premiere reinstalling helped for me in this situation. maybe it’s enought just reinstal premiere, but we need to change our OS to 64bit, so we did it too… And after, premiere rebuilt project and now i can finish it ;]

Page 2 of 2

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