Extremely Large Premiere CS6 Project Files – Over 1 Gigabyte?!

[Ivan Myles]

Does the 1.5GB include preview files?

[Errol Lazare]

Hello Ivan,

No, this is just the project file itself and of course each autosave file. Is this normal for premiere.
I am getting increasingly more disappointed with the performance and even though I have a 12-core mac with 24 gigs of ram and a Quadro 4000, the performance is very poor and seems worse than editing on final cut on my laptop. Not sure why but premiere feels like a very heavy program on this computer.

I cannot even get though a full 3 minute sequence with a few effects without the video becoming choppy and the audio cutting out.

Errol X. Lazare
EXL Films
http://www.exlfilms.com

[Pat Horridge]

Luckily premiere hasn’t really had any in roads on the post work we do you (mostly broadcast). But I’ve heard similar reports. Long form work seems to resulti memory leakage in the project. The temp cure seems to be creating a fresh project and copy the sequences etc across. But as you work the size will start to grow again.

Pat Horridge
Technical Director, Trainer, Avid Certified Instructor
VET
Production Editing Digital Media Design DVD
T +44 (0)20 7505 4701 | F +44 (0)20 7505 4800 | E pat@vet.co.uk |
http://www.vet.co.uk | Lux Building 2-4 Hoxton Square London N1 6US

[Joseph W. bourke]

A lot of people have weighed in on this issue, and I think that it’s really important that these things go on the Adobe bug report page:

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

They’re definitely listening. I have a number of colleagues who work in longform, who, over the years, have tried, then dropped Premiere due to sluggishness and poor media management (database) tools. I think AVID reigns king in that realm, especially since FCP7 is a fading memory, and FCPX is not quite there (or is different enough that most think it’s not quite there…

I use Premiere, and have for years, but never for anything over five minutes, and I find it bullet proof for that type of work.

Joe Bourke
Owner/Creative Director
Bourke Media
http://www.bourkemedia.com

[Jeff Pulera]

Hi Errol,

Do you have the Warp Stabilizer applied to multiple clips? My understanding is that it can cause the project size to rapidly bloat. My fix has been to export those clips, and replace stabilized clips with the new copies in the sequence.

Thanks

Jeff Pulera
Safe Harbor Computers

[Chris Borjis]

This sounds like a case where it’s prudent to log only
the footage you need with Prelude instead of bringing
in all 10 hours of footage imported.

That’s the way I would have done it.

I shutter at the amount of time it would take for
premiere to re-index all the footage should it
get moved to another edit system.

[David Mcgavran]

There was a known bug in CS 6.0 on this. Please update to 6.0.2 and open then save the project. It should get smaller. If not, let me know

Thanks!

Dave

———————————————————————————————————
David McGavran, Adobe Systems Incorporated
Senior Engineering Manager Adobe Premiere Pro
———————————————————————————————————

[David Mcgavran]

Not exactly true… Was with a customer recently who was cutting a massive project with 80,000 clips in it… If you are running into large project issues we would love bug reports reported to us.

Thanks!

Dave

———————————————————————————————————
David McGavran, Adobe Systems Incorporated
Senior Engineering Manager Adobe Premiere Pro
———————————————————————————————————

[Micha Mclain]

Maybe, but with FCP 7, I never had to worry about that. I’ve moved feature project files rom machine to machine that had equal to or more footage with zero problems. Simply close the file on one machine, open it up on another and you’re working.

The whole “indexing” files is still quite a mystery to me. No other edit platform does this, at least that is obvious. When I’m working on event type projects, I simply have to walk away for hours and sometimes even overnight before I can start an edit. That’s just simply not professional performance.

I think there’s a fundamental problem with how Premiere project files work. I mean, at it’s core, a project files is just a database filled with instructions. There is simply no reason for these files to get this big.

I would love to find a solution to bloated project files, slow performance during “indexing”, sluggish dynamic linking, etc, because I really do enjoy PP’s feature set. However, the performance is a serious issue for me.

I’m about to start a feature documentary, and at the moment, I just don’t think I can do it in PP without wasting tons of time.

-Micha
Founder • Editor • Tech Guru
https://www.multiversemediagroup.com

[Micha Mclain]

Maybe, but with FCP 7, I never had to worry about that. I’ve moved feature project files rom machine to machine that had equal to or more footage with zero problems. Simply close the file on one machine, open it up on another and you’re working.

The whole “indexing” files is still quite a mystery to me. No other edit platform does this, at least that is obvious. When I’m working on event type projects, I simply have to walk away for hours and sometimes even overnight before I can start an edit. That’s just simply not professional performance.

I think there’s a fundamental problem with how Premiere project files work. I mean, at it’s core, a project files is just a database filled with instructions. There is simply no reason for these files to get this big.

I would love to find a solution to bloated project files, slow performance during “indexing”, sluggish dynamic linking, etc, because I really do enjoy PP’s feature set. However, the performance is a serious issue for me.

I’m about to start a feature documentary, and at the moment, I just don’t think I can do it in PP without wasting tons of time.

-Micha
Founder • Editor • Tech Guru
https://www.multiversemediagroup.com