what causes projects to become damaged? at DVinfo.net

David J. Payne · August 29th, 2007, 10:45 AM

Hi i notice recently I keep getting PP2.0 projects becomming damaged and Im being told it can not be open. If like on this occasion there is no file in the auto save folder I lose a lot of work as I'm sure many of you have..

It seems to happen more often when using my external hard drive attempting to edit onto a different pc.. which i know is ok as i do it all the time.. but occasionally i get the error.

Does anyone know any way of recovering damaged files or more importantly preventing this from happening?!

Kevin Janisch · August 29th, 2007, 04:31 PM

Can't comment on why or how, but will say to just save copies as you go. I usually will backup and save a copy after each editing session. Like most, I learned this the hard way and lost significant changes to a corrupt project.

Mark Yang · August 31st, 2007, 09:45 PM

Bad mojo. Not talking gently enough to premiere pro.

Steve Wolla · September 1st, 2007, 10:23 AM

Do you get a red screen in the project moniter? Is that the problem you are having? Is it asking you to tell it where .avi files are? Can uou give a little more detail please.

I have tried to copy my jobs to an external HD before so I could take it with me and hook it up to my laptop at home and keep on working. This generally does not work for me, and it has I think, to do with how .avi files are saved.

Matthew Nayman · September 1st, 2007, 11:11 AM

usually has to do with mixing incompatible formats on the same timeline.

Bill Engeler · September 3rd, 2007, 12:09 AM

I was having similar problems, and it appears that it was a faulty 1GB memory module. After swapping it for a new one, I haven't had the problem (knock on wood). There are some programs you can download to test your RAM. I can't suggest a specific one, but you might want to try it.

I was sometimes able to repair the file manually, using XMLWrench, which was free to download on a trial basis. On some occasions, the entire problem was caused by one garbled character in the XML text (!!!). Other times half the file was missing. In any case, make frequent backups. The .prprog file is really quite small.

August 29th, 2007, 10:45 AM	#1
David J. Payne Major Player Join Date: Oct 2005 Location: Southend-On-Sea, England Posts: 368	what causes projects to become damaged? Hi i notice recently I keep getting PP2.0 projects becomming damaged and Im being told it can not be open. If like on this occasion there is no file in the auto save folder I lose a lot of work as I'm sure many of you have.. It seems to happen more often when using my external hard drive attempting to edit onto a different pc.. which i know is ok as i do it all the time.. but occasionally i get the error. Does anyone know any way of recovering damaged files or more importantly preventing this from happening?!

August 29th, 2007, 04:31 PM	#2
Kevin Janisch Major Player Join Date: Jan 2004 Location: Monterey, CA Posts: 406	Can't comment on why or how, but will say to just save copies as you go. I usually will backup and save a copy after each editing session. Like most, I learned this the hard way and lost significant changes to a corrupt project.

August 31st, 2007, 09:45 PM	#3
Mark Yang Regular Crew Join Date: May 2007 Location: Huntington Beach, CA Posts: 41	Bad mojo. Not talking gently enough to premiere pro.

September 1st, 2007, 10:23 AM	#4
Steve Wolla Major Player Join Date: Nov 2005 Posts: 477	Do you get a red screen in the project moniter? Is that the problem you are having? Is it asking you to tell it where .avi files are? Can uou give a little more detail please. I have tried to copy my jobs to an external HD before so I could take it with me and hook it up to my laptop at home and keep on working. This generally does not work for me, and it has I think, to do with how .avi files are saved.

September 1st, 2007, 11:11 AM	#5
Matthew Nayman Major Player Join Date: Feb 2005 Location: Toronto Posts: 917	usually has to do with mixing incompatible formats on the same timeline.

September 3rd, 2007, 12:09 AM	#6
Bill Engeler Regular Crew Join Date: Aug 2006 Location: Brussels, Belgium Posts: 162	I was having similar problems, and it appears that it was a faulty 1GB memory module. After swapping it for a new one, I haven't had the problem (knock on wood). There are some programs you can download to test your RAM. I can't suggest a specific one, but you might want to try it. I was sometimes able to repair the file manually, using XMLWrench, which was free to download on a trial basis. On some occasions, the entire problem was caused by one garbled character in the XML text (!!!). Other times half the file was missing. In any case, make frequent backups. The .prprog file is really quite small.