-
long from problem
I’ve been working with various Premiere packages for several years.
But most of those projects were 5-10 minutes, mostly short films. yes
the program was aggravating but survivable.When I began my first full length (90 min) indi I moved to CS3 and
basically rebuilt my computer and did clean installs of Windows XP and Adobe CS3, which installed with no problem at all. There’s nothing
on the computer but the CS3 package (and internet to register, of course)For the first 25 minutes of the timeline all was well.
At a fifty minute timeline I got an occasional “serious error” shutdown. Now at 82 minutes it’s turned into a nightmare with shutdown after shutdown.
So I got a tweak package recommended by PC computing and now my windows opens in a blink of the eye and so does premiere, although it takes forever to the project.
But I’ve still got the same problem working inside the timeline. I can export the entire sequence with no problem but I can’t really make edits anymore for an extended period of time.
I’m considering moving to FCP but that would really entail a re-edit of the entire movie but since I’m still finishing the assembly cut I might as well do that before moving into the sound work.
I’m just wondering if anyone out there has edited a ninety minute movie on Premiere and whether performance seemed to degrade as the timeline grew longer. Now this timeline is running with one video and one audio track (that is, no scoretrack, no sound effects, etc.) so it’s only going to get more complex.
Is there something happening I’m just not aware of? I’ve got everything in neat bins, clean the media cache, etc. etc. I’m starting to think Premiere is not the vehicle for long form projects. Any advice appreciated.
Thanks.
-
8 Replies
-
I have done multiple movies over 90 minutes long in Premiere. I have never had any of the slowdowns as you state you have. How much memory does your system have? If you run out of Ram Premiere can become unstable and crash, on a PC at least.
The last thing over 90 minutes I did was done on a system with 8GB of memory. When you run out of Ram in Windows it can cause chaos when editing because writing to the paging file is really slow.
-
Interesting. I thought I might have something to do with the paging.
I’m using a Pentium Dual Core 2.8 with 4 gigs ram. I thought 4 gigs was the max for a 16 bit system like XP.
Thanks.
David
-
I meant a 32 bit system can only access 4 gigs. Sorry. It’s been a long day.
-
Yeah you can only actually use 3 gigs of that 4 you have installed. I have a Dell XPS that I use to do video on before I got my Mac Pro and it only had 2GB of ram and if any movie went over an hour it would occasionally slow down.
Its also good to make sure that any video you are working with is compressed for what its going to end up on.
I had a Documentary that was an Hour long and the entire size of the project was 135gb because I saved all the video and animations as AVI’s in high quality. I just transferred the project to my Mac and converted the video to quicktime and now the entire project is only 5GB. It was only output on DVD so I didn’t need to save it as AVI.
-
I’ve heard a lot of users complain about long projects…I’ve worked on some timelines with 3 hour spans with 4 video tracks and 3 audio tracks (a presentation with graphics, a screen capture track and video as well as a PSD GFX layer) at a weird screen setting (1024×768 for computer playback) and it seemd OK. Encoding the timeline to Flash was a time-consuming process, but otherwise i didn’t really notice any big problems.
I’d like to know what type of footage you’re using and if you have any third party hardware (RT boards, that sort of thing…)
Also…what happens if you export an AAF file and import that into a new project? Once the project crashes a few times, it’s becoming gradually corrupted…and it will take longer to launch.
TimK,
Director, Consultant
Kolb Productions, -
TIm,
Just AVI from a canon GL2. Lots of stills, which apparently may be part of the problem because I learned I have them set at 300 DPi and they shouldn’t be above 72. No external capture boards or anything like that. NVIDIA 8800 with 512.
Yeah, I think I may have some corruption within the timeline. What I’ll do is import into a new project with the project manager and see what happens.
it’s good to know others have done very long projects which means there’s a solution somewhere.
David
-
Oh…stills…yes, sorry to say that stills are definitely an Achilles’ heel of Premiere Pro…
…reducing the size of the stills so they are only as large as you need them will certainly help…and getting them all to 72dpi might at least help them be interpreted correctly by the software.
I don’t suppose that loading the stills into After Effects and doing moves in there would help?
Also, I’ve had better luck with lots of Photoshop docs than say, TIFs or JPEGs.
TimK,
Director, Consultant
Kolb Productions, -
dave unfortunately theres a big hole in the package that affects long form editors, not really sure what it is.
but ive posted about it previously here : https://forums.creativecow.net/readpost/3/890834
adobe will deny theres an issue, and im starting to think they really dont have any idea about it
~Peter Berthet
Sydney, Australia
Reply to this Discussion! Login or Sign Up