Frage von Kai86:
Hello,
I have the following problem. I have been cut eternity s.einem film (determined 200 hours) and now Premiere Pro shows me when to open this project, that this was probably damaged.
I have been synonymous following attempts:
- In a copy of the project, "" instead of "." wanted
Premierefix.exe-used
Old-Project in a new import.
Adobe re-install
Nothing like working unfortunately. In google, or in the forum, unfortunately I think only these 3 options and, unfortunately, because I only have backup Ancient (ICH IDIOT) and strangely of me Autosave has been disabled, I hope now only that you can help me! Wär echt super and see this story synonymous as an opening of a collection of problem-solving this not so rare error.
Ah yes, the last thing I have done s.Project was the dubbing with a mp3.
Thank you for your efforts,
Kai
Antwort von ami842:
- In a copy of the project, "" instead of "." wanted
Only "Wanted" or equivalent "replaced"?
hm, so even if
Old-Project in a new import.
no longer works, unfortunately, because I see black. What is the error message because exactly?
This will help you now, not next, but I do not understand how one of such a big project to more than
a daily, hourly, if not make a backup. It takes less than 10 seconds!
viel erfolg
Antwort von ami842:
Hi,
sought help and replaced .... nothing ..... I was just convinced that the automatic backup s.sei, but that she was not.
I think that somehow the end of the file is destroyed, because it ends with:
<IsTimeVarying> True </ IsTimeVarying>
</ AudioComponentParam>
<AudioClipTrackItem>
<ID> 4e8c1d54-acdf-402e-9b92-1b92004e31a9 </ I The exact error message reads: The Project is apparently damaged. It can not be opened.
It must be but somehow save it!
Thank you, Kai gruß
Antwort von ami842:
Oh yes, I'm a bit of progress - from bad to worse and although I have a backup Uralt after the end of my damaged file searched, this place completely copied and inserted into the broken.
Now the following will happen: It no longer breaks after half s.with the above message before but very briefly with the final message:
It is a fatal error. Adobe Premiere Pro needs to close. It tries to save the Project.
Bring me something because now, or should I s.der original version next start, or abandon it entirely?
Gruß Kai
Antwort von nico:
Even though I constantly repeat:
Move the temp times. Preview files or rename them, so that Premiere has to render all things new. Your project should then be ok again.
Antwort von ami842:
Nico Thanks for the tip, but unfortunately nothing has helped :-(
I think the fault lies in the project file.
gruß Kai
Antwort von ami842:
Also the import of my "new file" in a new project does not seem to work .... a half hour since it is still at 0%
It's like bewitches .... it may actually not be so difficult in the project file these silly errors found ..... hab now synonymous times after trying to search for mp3, which I have inserted as the last (in the project file ) and where this is mentioned anywhere and then have them synonymous vereinselt and once synonymous throughout herausgelöscht, but nothing has been synonymous slowly :-(.... I do not know more next .... please help, if it still goes .
Thx, Gruß Kai
Antwort von Wiro:
Hmmm - is always so ne thing, if you built the project backups off.
On the website of the premiere experts Steven Gotz I found the following notice:
If you have a corrupt project file in Premiere Pro, XML Wrench try downloading and using it to fix the problem. Under tools, select Check Well Formed.
http://www.stevengotz.com/premierepro.htm
Have not even tried yet, but maybe takes you next.
Good luck.
Gruss Wiro
Antwort von ami842:
Thanks Wiro,
with the tool can be very beautifully arranged File open .... now I'm curious times, if I said the error in the eye jumps.
Thx Kai
Antwort von cutterfeld:
So, now synonymous nor did I test the new version of Adobe Premiere Pro fetched (2.0), but broke with 2 of my 3 test files from exactly the same.
The third was then:
[devstingray ackendsrccore ode.cpp-186] as an error, but will probably get nothing more synonymous, right?
Thanks for the nice so far, extensive assistance,
Gruß Kai
Antwort von Sess:
Is there something vll. wia "media offline"? Doer sop ..
Vll. The partition on which everything was just a different drive letter and get Preimie find nothing more?
Antwort von Blackeagle123:
On the website of the premiere experts Steven Gotz I found the following notice:
If you have a corrupt project file in Premiere Pro, XML Wrench try downloading and using it to fix the problem. Under tools, select Check Well Formed.
http://www.stevengotz.com/premierepro.htm Fat! :)
I just wanted my project away and start again in front of, since I "by hand" in the XML file've seen no errors. Since I've downloaded the tool. And then looking for errors. Indeed, he has found an error in the statement (and I translate times) "File Name is Clara X [symbol]" (; this [symbol] was incorrect and has in the xml file a bug. After deleting this little icon does the file back correctly.
Thank you!
Kleiner Tip: Simply save and now I create "by hand" fuses, which read: "Project 1 copy", "Project 1 copy 2".
This move me to another (; physically separate hard drive). Although I have on the safety SATA disks that are mirrored. But if an error or Premiere, the synonymous written to both disks ;-)
Many greetings,
Constantin
Antwort von ardenhart:
Hmmm - is always so ne thing, if you built the project backups off.
On the website of the premiere experts Steven Gotz I found the following notice:
If you have a corrupt project file in Premiere Pro, XML Wrench try downloading and using it to fix the problem. Under tools, select Check Well Formed.
http://www.stevengotz.com/premierepro.htm
Have not even tried yet, but maybe takes you next.
Good luck.
Gruss Wiro The tool works great !!!!! DANKE DANKE DANKE
Just the project file in XML Wrench Open (; Warning: file only under "any files" button), then under Tools, check well formed "- and the problematic line is displayed. For me it was a problem with a Clipumbenennung - I just deleted the characters, which looked strange.
Antwort von Wiro:
Additional Information:
Faulty project files, experience in most cases by the fact that when you Benamsung spaces, accents or special characters are used.
That should be feasible to leave.
The XML engine, responded because it is very sensitive.
Greeting Wiro
Antwort von Blackeagle123:
That sounds somewhat strange, but true fact. ;-) The special thing about it is even that the XML file only partially reacted. That means in a specific case with me: I was the Project 3 times to open and edit. The fourth time was an error! Why this is so, understand, probably not even the programmers.
You should avoid: ö, ä, ü, special characters (like _,!,%, &, Etc.).
Officially you should even capital letters and avoid spacebar, which has for me but still no problems.
Many greetings,
Constantin
