-
Premiere crashes constantly
Hi,
I got massive problems working with Premiere Pro 1.51 and BM Decklink Extreme. The Project File is pretty big now, I have got a lot of material (BM 10bit) in there and something like 40 sequences (actually its diefferent versions of about 20 sequences). The Sequences are between 1 minute and 4 minutes long and should be put together later for a TV programme. Each sequence has 2 stereo tracks, 3 5.1 tracks, 2 mono submixes and 1 stereo master track.
Now I have to to make a DVD of alls sequences to give away for voice over-Later more material will be addes before the project will finally be put to tape.
Today I tried to create a master sequence for the DVD, consisting of something like 12 sequences with 45 minutes in total. After a few minutes working in the sequence at best, Premiere crashes. The programm has been unstable all the time, but now I am totally stuck.
I tried not to put the sequences in the master sequence for DVD as sequences, but to copy the content of the sequences (all clips, all tracks) into the master sequnece. Like that I could get the export to DVD started. But after about 40 minutes of encoding (transcoding is finished by then) it stops and says “not enough RAM” [actually it says it in German so I am not sure about the correct wording].
Now I will try to render all sequences to clips, but this will take hours and is no solution in the long run.
Has anybody any idea, how I could get this done?
Thanks Michael
I am not sure about the system specs, cause I did not setup the syste. Anyway its wndows XP SP2, A Tyan Board (S2676?) and 2 Gig RAM.
-
3 Replies
-
Had this problem before and what I did was delete all the unneccesary sequences and clips that werent needed in my final sequence. This helped in making the project file significantly smaller and lighter for PrePro to process. Hope that helps.
-
Hi Adrian,
thanks for the reply. I think that is a good idea. The project file had become very big (21 MB), now I tidied up a bit and brought it down to some 8 MB. Hope it will be running more stable now.
Cheers
Michael
-
PPro, according to one of their techs I talked with recently regarding the issue you are dealing with (and I am dealing with), can only “address” so many “records”, like large numbers of clips in bins, sequences made up of many shots, thumbnails, etc. Doesn’t matter how much physical RAM you have over 2gigs. I have 3 and was considering bringing it up to 4, but the PPro tech guy said it won’t make any difference.
Apparently this horrendous shortcoming has something to do with it being a 32-bit app. Whenever PPro becomes 64-bit (along with all the hardware, drivers, OS, etc.), then those of us working in long form will longer have to put up with these issues.
So, if you’re approaching PPro’s infamous 1.8 or 1.9 gigs of pagefile or ram use or whatever the hell’s going on, the grit-your-teeth slowdowns, crashing, white interfaces, etc. begins. Meanwhile, I believe the workarounds that Adrian suggests are unfortunately the best you can do.
Surely, PPro v2 will be a 64-bit app if Adobe wants to continue marketing it as a truly professional-level editing solution.
Bill Buchanan
Buchanan Film Co.
Reply to this Discussion! Login or Sign Up