Skip to main content
just edit
Known Participant
November 16, 2013
Answered

Premiere Pro CC project takes 1 hour to open !

  • November 16, 2013
  • 4 replies
  • 24690 views

Hi everybody,

After a Premiere Pro CC 7.1 crash, I tried to reopen my last project and the loading of this project took 1 hour to reopen normally. The yellow loading progression bar is freezing approximatively at 30 % of full load. 1 hour later, my project is open without any problems. If i save the project again, quit Premiere and reopen my project, it loads in a few seconds...

I tried many things before waiting the hour :

  • Kill Premiere during the load, reopen a backup of my project : same problem > load is very long and seems to be frozen
  • Shutdown computer and restart then reload the project : same problem > load is very long and seems to be frozen
  • Open the crashed project in another computer (Mac) without the media attached : same problem > load is very long and seems to be frozen
  • Delete all the media cache folder and empy trash.

This happend several times on a big project (lots of media, multi cameras) usually after many CTRL-Z action that are (I think...) too fast.

My footage are clean and on a Raid 0 disk

It's not really dramatic but when it happens when a director is arround me, and we spend 1 hour to wait for a simple project load... that's really not cool 😕😕

Anyone got an idea ?

My configuration : Windows 8.1, Premiere Pro CC 7.1, 32 GB Ram, Bi Intel Xeon E5-2630 2.3 GHz

Thanks !

noar

PS : I happened for the first time a few days ago. I've posted this thread : http://forums.adobe.com/message/5838103#5838103

Since, it happend 3 times in two days...

This topic has been closed for replies.
Correct answer Mark Mapes

Hehe I'm pretty proud of this trick in fact The nerd part of me can't bear being beaten by a software... 1 week digging to find this one !

I'm very interrested to know where does this bug come from, just for my own curiosity. Feel free to contact me or post here to explain this issue when you'll have an answeart from Adobe.

Cheers !

noar


This bug has been isolated and is fixed in the version that we're currently working on. I'm not at all familiar with the bug report, exactly when it was discovered, or what's known about the cause.

Great job figuring out what was wrong with the project, noar, and of course how to remedy the problem. The details you provided made it possible for us to figure out that the issue you were experiencing mapped to a known bug.

4 replies

Participating Frequently
November 22, 2013

Three cheers to noar! Mark, maybe you should offer him a job at adobe!

Many thanks for the help. will look forward to the update.

Kevin J. Monahan Jr.
Community Manager
Community Manager
November 22, 2013

All right Noar!! The community thanks you!!

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Sandeep Singh
Participating Frequently
November 16, 2013

Hi noarprodz ,

Thanks for posting on adobe forums,

Please tell us, what type of footage you are using ?

What are the effects you have applied ?

what is the duration of the project ?

Are you using any third party plugins e.g. Magic bullets ?

Any 3rd party hardware e.g. blackmagic ?

You can try one thing, try to import whole project in After Effects, then export that as as new premiere pro project..

try to open new project.

one more thing you can try, open the project inthe premiere pro and export as FCP XML.

Now open a new premiere pro blank project, import FCP xml file in the premiere pro.

Hope these will work for you , crossing my fingers

Happy Editing,

Sandeep

just edit
just editAuthor
Known Participant
November 16, 2013

Please tell us, what type of footage you are using ?

  • Quicktime H264 from Canon 5D Mark III, few Go Pro clips (5 ou 6 in 2 hours) and some AVCHD clips (drone shots)

What are the effects you have applied ?

  • None except size and position of one camera to make a pip and see my both cam during my prework

what is the duration of the project ?

  • 1 "long" timeline with a 2 hours length

Are you using any third party plugins e.g. Magic bullets ?

  • no

Any 3rd party hardware e.g. blackmagic ?

  • no. Only one graphic card (Geforce 680, 4 GB) with 3 displays attached

You can try one thing, try to import whole project in After Effects, then export that as as new premiere pro project..

  • When I import the project in After Effects, same thing : the load is very long ! ...

one more thing you can try, open the project inthe premiere pro and export as FCP XML.

Now open a new premiere pro blank project, import FCP xml file in the premiere pro.

  • I can't do that when it bugs because to export as FCP XML, I have to load the original project... and that's the problem ! I tried to unzip the PRPROJ file (that's a Gzip file...) and parse de XML in it with and xml validator. Everything seems to be ok in my project. So I think the problem comes from the medias or the database ? ... But that's completely weird that when I try to open it on another computer (without the medias, with another database) I've got the exact same problem... So It's really the project that is corrupted.

Next time it will bug (sure it will...) this is what I'll do :

  • Copy my crashed project on desktop and keep it. After 1 hour of opening, I'll save the project with a new name and compare de 2 file size. Just to confirm that my crashed project and my good project are different. If they have the same size, maybe It's more Premiere than the project itself. If they are different, I'll compare them to see what changed between the crashed and the good one.
  • Writing in this forum I'm thinking about a new lead : Since PRPRO CC, the prproj files are gzip files (that's why the file size are so small compared to old version). So when PRPRO crash, maybe it corrupt the gzip compression of the project ? That's weird because a software like winrar can unzip the crashed project a reveal the xml file in it. So I'll try to extract the XML file in the crashed project and re-gzip it and rename it .prproj ?
  • Feel free to write some ideas or tests that could help me to understand this bug and how to resolve or quickly repair the damaged caused...

Hope these will work for you , crossing my fingers

  • Hope to. 3 crash with the director behind me that's not really cool when you're a freelance with your own machine...

THANKS EVERYBODY FOR YOUR PRECIOUS HELP AND THE TIME YOU SPEND TO READ MY PROBLEMS !!

just edit
just editAuthor
Known Participant
November 18, 2013

New day, new crash... many crashes in fact... :-(

My project is getting bigger everyday. My last tests returned the following results :

  • Crashes often happend after CTRL-Z command. Not everytime but this is the major cause of Premiere Pro CC 7.1 getting freezed.
  • The problem is no doubt the project file itself. A crashed project takes long time to open even on another machine with different media cache, different OS and no media attached (only the project and no source)
  • The problem is more frequent on big project file (1h timeline with many audio and video clips
  • The problem happens in a project without any third party plugin
  • The problem is not caused by warp stabilizer
  • The broken project file can be restored by simply waiting (a very long moment...) on the load (orange loading project bar)
  • The broken project can't be open by AME, After Effects
  • The broken project can't be import in a new empty one on Premiere (long wait also)
  • The autosaves created every minutes (for my test...) are also very long to open, just as the crashed project (I've tested the 30 last autosaves... so 30 minutes back in time)
Here are few leads that nead to be follow :
  • A broken project (after the crash) and the restored project (restored by waiting 1 hour to load it, and resave with new name) have different file size !! In my case, the crashed one is 5 795 Ko and the restored one is 3 355 ko
  • The XML file obtained by unzipping the 2 prproj files with winrar have also 2 different sizes : crashed one is 97 535 Ko and restored one is 76 073 Ko

So I think the crash is link with some autosave feature or history feature maybe saved in the project file ? I really don't know how the new prproj files are organized...

My next step :

  • compare the two project files : crashed and restore (prproj and extracted xml from these prproj files) with an file comparison software and examine what are the differences between the two files. The problem is that these are huge files (97 mo...) for a file comparison software...

Anybody got a suggestion ? Adobers please help !!!!

Thank you...

noar

Inspiring
November 16, 2013

Does your project happen to have stabilization applied to any clips?  Or, lots of keyframe animation?

just edit
just editAuthor
Known Participant
November 16, 2013

My project don't have any stabilization effect.

It has 8-10 timelines

It has one "long"' timeline -> approximatively 2 hours with 3 videos tracks and 11 audio tracks

Participant
November 16, 2013

It sounds like your media is re-conforming? Do you have any really long clips?

just edit
just editAuthor
Known Participant
November 16, 2013

No the longest clip is approximatively 5 ou 6 minutes long.