Premiere Pro CC project takes 1 hour to open !

[just edit]

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...

[tstormSierra]

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

[just edit]

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

[Jim Curtis]

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

[just edit]

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

[sankalpjena]

It happened with me and I have lots of animation. What I can do to make it fast? Premiere is trying to read media.

[Sandeep Singh]

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]

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]

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

[just edit]

Hello,

I've posted many threads these last days related to several crashes and an anormal time to load big project (between 30 mins to more than 1 hour...). No responses on this forum so I did a lot of tests myself to understand where does it come from.

Here is the situation :

• Working on a large project file (tv show more than an hour, many footage, source DSLR and audio recorder)
• Absolutely no effects
• Timeline more than 1 hour
• Premiere Pro CC 7.1 under Windows 8.1 x64
• Modern PC (bi-xeon E5, 32 Go Ram, Raid 0 stripe, etc.)

Sometimes (often after an undo command) Premiere crashes. When I try to reopen the project, it freeze at the orange loading bar. Then wait between 30 minutes to 1 hour (!!!) and my project is back as it should. When my project is finally loaded, I save it under a new name and notice that the file size of this new project (exactly the same as the one that open during 1 hour) is smaller ! In my case : 7 MB for the crashed one and 3.5 for the new one !!After many tests, it seems that it's an undo problem :

• I noticed (by checking regulary the project file size during my work) that each time I do a CTRL-Z to undo an action, my project file is getting suddenly bigger (500 KB or more...). Since this moment, if I quit Premiere regulary and reopen my project, I'll have to wait 30-60 mins to load it.

I'm feeling alone with this problem and no one at Adobe staff is decided to answear me. PLEASE ADOBE contact me and give me a solution !!!

Thank you !

noar

[excited_Genie16B8]

This is not something I'm experiencing on my own Windows 8.1 machine, nor have I seen others reporting the same issue.  It's likely a problem with that project, or if happening to more than one project, with your system in general.

Have you tried resetting Preferences?  Have you tried importing the project into a new one?

[excited_Genie16B8]

[Please keep only one thread per issue.  I've deleted the new thread.]

[daveinsacto-RL]

noar,

I have completely flushed my machine of all things adobe, including flash and acrobat. I first followed this page for the cleaner tool, which I have used before:  http://helpx.adobe.com/creative-suite/kb/cs5-cleaner-tool-installation-problems.html  

Choose clean everything for all adobe products.

I also used (for mac):    http://helpx.adobe.com/flash-player/kb/uninstall-flash-player-windows.html    to remove flash player...not certain if that was necessary, but I figured there are likely some shared directories that I would be deleting, so I let the adobe product do the job before I did it manually.

From there, I went as far as removing all adobe system/user libraries. I first copied those files to a seperate drive prior to deleting them.  I also copied the media cache files prior to deletion so that my footage would not need to re-conform on reopening the project files. I am osx, so the paths will differ, but I believe from memory, that the adobe library filestructure is very much the same on both platforms.

From there, I ran a disk utility (defrag), recycled my machine, re-installed creative cloud, then premiere, after effects, photoshop, bridge, extention manager, and audition.

After the full re-install, my saved project files (pre-'undo' crash, or reopened from crash and saved) opened much faster than before, peak files and conform files ran much faster. The software is much more responsive.  I have not experienced an 'undo' issue as of yet and i will certainly update if I do. However, the Adobe QT32 Server is still on lockdown, so that will take further involvement with the adobe engineers to understand what that issue causes or doesn't. Also, the copy I had saved of a 'crashed' file tried to open just the same, so I'm considering that file corrupt and have removed it from my system, as well as all associated autosaves.

Hopefully you are back to editing! What's your show called?

Cheers.

Dave O'

[daveinsacto-RL]

back up any presets, effects/media encoder etc...

[Jim Curtis]

FYI, using the Adobe Cleaner Tool does NOT flush "all things Adobe" from your drive.  Last time I ran it, I ran EasyFind, searching for "Adobe," and it found over 300 files with Adobe in the name.  If you want to truly start fresh, you need to remove those items manually.

[daveinsacto-RL]

Yes Jim, you are correct, which is where deleting all user/system library items comes to play as described.

[just edit]

Dave,

That's good to know that a fresh reinstall speed up the load of the "crashed" projects but you also know that in the real life, we can't afford reinstalling the system everyday Anyway that's maybe a lead for Adobe's developpers...

I'm back in buisness. My trick seems to work great (did two times since this morning) and Annie's post confirmed that it worked for her too. Glad to have a solution now, and glad to share it and avoid other people to waste 1 week with this bug.

Jim : you're right. Adobe Cleaner Tool does not flush everything. You need to flush the lasts files manually.

Dave : I'm working on a pilot for a new french TV show. This is called "Viens dans mon jardin" (please come in my garden). Idea is simple : a family with a very bad garden calls the show and a professionnal gardener comes to their house and give them advices and works with the family to get the garden better. It's a kind of "kitchen's nightmare" in a garden... French version... so soft one

[daveinsacto-RL]

noar,

update, re-installing did not permanently solve the issue, and I thank you extremely for your <Link Index= trick...worked splendidly. That one's severely over my head! And to clarify, this machine desperately needed an adobe cleanup. There were remnants of CS3 still here. You are correct in mentioning that production cannot stall on a daily basis.  This is a strange issue, and I imagine we will see more of this popping up in discussion. I'll reach out to these guys out here in SF to see what they can dig up. The show sounds like a great project! thanks for sharing!

cheers!

[just edit]

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

[Mark Mapes · Accepted solution]

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.

[cornelius_3]

When will this version be released?  This just started happening to me an Noar's workflow didn't work. 

[Mark Mapes]

I was referring to CC7.2, which was released in mid-December. CC7.2.1 followed shortly thereafter.

What exactly do you mean when you say "this just started happening..." What I'm getting at is how sure you are that the problem you're encountering is exactly the same issue that Noar and others hit.

[cornelius_3]

Mark,

   I started recieving problems loading premiere pro cc projects after saving them and re-opening them.  I repeat.  I cannot re-open a project even after it has been saved.  I have been forced to create a new project and import the previous one to continue editing.  When I boot premiere and load a previous project it locks up and fails to load.  I get the beach ball of death and I must force quit and create a new project.  This just started happening after the most recent update from Creative Cloud.

[Mark Mapes]

It sounds like you're having a completely different problem than Noar and the others on this old thread, so I advise starting a new thread. In their cases, only some projects were affected, whereas I gather that every project you save ends up being unloadable. Plus, if you're on 7.2.1, then the bug that caused the problem that Noar found a workaround for is no longer present. By the way, it helps to report the exact version that you have, after double-checking what's reported in the About box. Occasionally we find that customers are not actually on the current version. Regardless, it makes the thread clearer for people who come across it in the future after a newer version is out.

[daniele42024393]

It seems like I'm having this same issue in the latest version of Premiere. I'm on a late 2020 iMac. Projects started taking forever to load, and now it crashes if I click on the wrong bin.