Copy link to clipboard
Copied
A couple days ago I spent all day editing a project. It's about 10 minutes long and consists of all iPhone videos - various frame rates and resolutions. It came out great and I closed the project for the night. The next day I came back and tried to open the project and after the loading bar completes, I get the error: An unknown error has occurred while opening the project. Other projects open normally. New projects open normally. But this one does not. I am so upset and frustrated about the lost work.
I went to my recent auto saves and they give me the same error. If I go way back in the auto saves, they will open normally but that was before many hours of additional work on the edit.
I made a new project and tried to import the old project and I get the error: The importer reported a generic error.
I used Media Browser to view the project and the window where I should see everything is blank, even after the loading bar finishes.
I used Project Repair from Digital Rebellion's Pro Maintenance Tools which thinks it has repaired the project, but I get the same error when trying to open it.
I used CS Repair from Digital Rebellion's Pro Maintenance Tools to trash Premiere preferences. No help either.
I googled the error message endlessly and although the same question has been asked, none of them got an answer.
Please advise.
Premiere 2017.0.1
macOS Sierra 10.12
2012 Mac Pro 12 core 2.4GHz
Nvidia GTX 780 6GB
32GB RAM
Copy link to clipboard
Copied
the fact that it's the end of the year and i suffered through the same is shamefull adobe
Copy link to clipboard
Copied
Adobe does not fix their bugs, plain and simple.
Let's recall what Adobe staff member, Kevin Monahan, has to say about it.
Kevin-Monahan wrote
Corrupt project files are a fairly common occurrence. Corrupt project files are generally not fixable by support.
Unfortunately, you're often times on your own when it comes to corrupt projects because we have limited engineering resources. We don't have the time to repair them.
Regards,
Kevin
Copy link to clipboard
Copied
I'm sorry to read this, but I've been working on Avid Media Composer and NewsCutter since 1991 ...
(and I also have a lot of experience on LightWork / HeavyWork / NewsWork as well as on QuickCutter)
and I have never, nerver, never experienced a project crash in this amount (maybe 2-3 over all those years only).
I am speaking as a former pro editor who has lost work due to corrupt projects from a variety of NLE software.
So there is a problem of stability at Adobe Premiere so that so many people suffer in this way!
Denying it or minimizing it is absolutely not acceptable on the part of this brand ...
And doing nothing to avoid it or correct it is even more.
Copy link to clipboard
Copied
Exactly!!!
I have same opinion about Edius pro
Copy link to clipboard
Copied
I am having the same problem, and I just got finished my conversation with Tech Support who simply said the project is corrupt!!
Mohsenagha! I need you
Copy link to clipboard
Copied
Did anyone try to delete the 'Video Previews' and 'Audio Previews' of that project ?
most of the times, from my own experience, these files cause such behaviors on Premiere
Copy link to clipboard
Copied
No this is not about previews or rendered files, plugins or any other
things like that. The problem is within the project file itself.
On Tue, May 8, 2018 at 1:14 AM, carlosz13485882 <forums_noreply@adobe.com>
Copy link to clipboard
Copied
Mohsenagha​ please do not confuse 'plugins' with 'video previews' and 'audio previews'
did I mention anything about 'plugins' ?
I had similar experiences before, deleted the 'video previews' in most of the cases and the
project opened normally.
It is just a suggestion to try it out because it is so simple, if it doesn't work, then follow along with your method
Copy link to clipboard
Copied
My friend I just wanted to say not only the audio and video previews in
this particular error have no effect nor plugins and so other things
outside of the project file. Sure base on my own experiences.
How ever I'm really appreciate your participation in this threat and maybe
your experience will help somebody in future. Thanks
On Tue, May 8, 2018 at 1:25 AM, carlosz13485882 <forums_noreply@adobe.com>
Copy link to clipboard
Copied
Hi Mohsenagha,
Thanks for all your advices.
I tried this
"1- make sure your project file is corrupted and cash files and hardware and ... is ok. (mainly this error means the problem is inside project file An unknown error occurred while opening the project )
2- open your project with a compressor software like Winrar
3- extract the file inside
4- open it with xml editor apps and fix the problematic parts.
5- convert to gzip
6- rename .prproj
7- scream loudly Adobe "
but I don't know what I have to looking for in step 4.
If you have some time, could you take a look on this?
Thanks again.
Copy link to clipboard
Copied
Yeah it needs some programming skills.
Ok I will check it for you​
On Tue, May 15, 2018 at 11:31 AM, stefanec554708 <forums_noreply@adobe.com>
Copy link to clipboard
Copied
send me the link as text like this : https://we.tr/sdfsd464
On Tue, May 15, 2018 at 11:31 AM, stefanec554708 <forums_noreply@adobe.com>
Copy link to clipboard
Copied
Copy link to clipboard
Copied
email me:
[email deleted by mod, forum policy] Use PM to post email adresses.
On Tue, May 15, 2018 at 11:56 AM, stefanec554708 <forums_noreply@adobe.com>
Copy link to clipboard
Copied
send me an email to send you the recovered project
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
I test this app on about 6 different broken projects with different reasons and God bless the digital rebellion none of those files recovered successfully even those who I recovered before and I was sure that they are recoverable.
Copy link to clipboard
Copied
yeah 100% I tried it myself as well...
I tried fixing annap's file using wrench but every time I reach
a broken line and fix it until i see the 'ok' you will see other
errors appearing from nowhere ... really really an arduous task !!!
I do not do coding and programming but I decided to try and experience
for these annoying errors to discover what all of that could be and what it is
all about. as you said, premiere needs every single line of code to be able
to open the file, from the thousands of codes in an xml file, even a bracket matters !!!
I don't know if paid software will fix that
thanks Mohsenagha​
Copy link to clipboard
Copied
Hi Mohsenagha,
Been reading all your many happy customers, and desperately need your help!
Broken Project For Repair.prproj - Google Drive
I blue screened out while editing and I really need to fix this project. My autosaves are not recent, I have lost hours of work. I've tried XML wrench and all other manner of fixes but no luck.
I plea for your assistance. Please let me know if you can do anything!
It would mean so much.
Thanks,
Mercer
Copy link to clipboard
Copied
I hope he will be able to fix your file, but for next time, try to develop the habit
of saving as many project files as you can, they won't take too much space,
I always have like 15 to 20 saves of my big projects and on more than one
hard drive, so after finishing a good deal of work, I collect my files and back
up everything on another drive, and keep doing this until I finish and deliver
the work and after the client is happy and pays
Copy link to clipboard
Copied
Yes I absolutely will start that as a habit. I've learnt my lesson about relying on auto save
Sometimes a start projects don't know where they're going so before I know it they've become something awesome but then I haven't done the necessary backups and saves! ah well. a good learning experience none the less!
Copy link to clipboard
Copied
So sorry my friend, there is no cure for death. Your project's XML is not
accessible.
Copy link to clipboard
Copied
Aw man you're joking me
Ah well, at least I have the accolade of having outdone the famous Mohsenagha, XML magician extraordinaire!
Thanks anyway!
Copy link to clipboard
Copied
My friend unfortunately your file won't let me to apply my magical power to it's XML. The problem is accessing the lovely XML not about repairing it.