Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Premiere Pro CC project takes 1 hour to open !

Contributor ,
Nov 15, 2013 Nov 15, 2013

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

24.7K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Nov 22, 2013 Nov 22, 2013

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.

Translate
New Here ,
Nov 21, 2013 Nov 21, 2013

Hi,

I have the same problem with one particular project. It won't open at all or sometimes after a very long time. The program crashes when pressing cmd z as well. I did use the warp stabilizer a couple of times. The sequence isn't longer than 5 min. I've tried different things like exporting an xml and importing the sequence into a new project. The xml doesn't open at all and when in a new project it takes a very long time to open the project in the media browser.

So now when the project finally opens (fingers crossed) I have to avoid pressing cmd z.

I think it is a premiere pro thing, but I anyone knows what the problem might be please help.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Nov 21, 2013 Nov 21, 2013

Hi Annie,

Try the following next time it hangs on load :

  • Force quit Premiere
  • duplicate your PRPROJ file
  • change .prproj extension to .zip
  • unzip your project
  • add .xml to the extracted file
  • open in a text editor or xml editor
  • search for lines like : "<Link Index="NNNN" ObjectRef="NNNNN"/>" in your project (NNNN are numbers of course)"
  • In my case I had more than 4 millions of theses lines...
  • Delete theses lines and keep only the 10 first one.
  • Save your xml file.
  • Change .xml extension back to .prproj
  • Open in Premiere
  • Tadddamm....

I'll be interrested to know if this trick works on your project...

Here is my other thread to this bug : http://forums.adobe.com/message/5837375#5837375

Bye !

noar

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 21, 2013 Nov 21, 2013

Hi Noar,

The trick works! Thank you!

Bye!

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Nov 21, 2013 Nov 21, 2013

Yeah ! That's a good news for me too This trick is very fresh... Found this solution early this morning (France time) after a 6 hours (yes you heard it...) wait to load my 22 MB project...

After the trick and a new save as prproj, my project is 4 MB !

Glad to hear that it worked for you too. Have a nice day

noar

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 21, 2013 Nov 21, 2013

It does still crash when pressing cmd z.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 22, 2014 Jan 22, 2014

I'm having this same issue and your solution looks promising. What did you use to unzip the project once you changed the extension? When I use the default windows unzip too and 7-zip they both say the file is empty and then fail.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Jan 23, 2014 Jan 23, 2014

Hi Willsinator38. I used WinRAR to unzip the project file. Before unzipping, remind you must change the ".prproj" extension to ".zip". Then you obtain a xml file without extension. Add ".xml" extension to this extracted file then you can edit it. Good luck.

As Mark Mapes said this bug is corrected in the new 7.2.1 Premiere Pro CC update.

Peace

noar

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Nov 22, 2013 Nov 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.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Nov 22, 2013 Nov 22, 2013

All right Noar!! The community thanks you!!

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
Nov 22, 2013 Nov 22, 2013

Good idea Dave. A job as technical consultant at Adobe to dig all the bugs in Premiere or the functions that I'd love to see in it. I've got plenty of wishes

Otherwise simply few months free to my CC subscription... I'll take it too

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines