The corrupt project behaves really strangely & slowly on my machine. Beachballs for ages when doing anything.
It has hundreds of items with 0 length, 0 playrate, 0 volume in the RPP itself.
The original converted RPP contains nothing suspicious looking.
When reaper reads a project file it fills in missing values or nonsensical values with a default - usually 0. It is very tolerant of crap in the file.
I took the uncorrupted original RPP and changed an item's length for a stupid value. REAPER opened it fine with no complaints but the length was now 0.
<ITEM
POSITION 2797.3089267826203
SNAPOFFS 0
LENGTH rubbish
I've never had reaper save a bad file but it's possible. However, I think it's unlikely that lots of people wouldn't also notice.
It could be file system problems, backup system problems.
Although it's also possible you did something accidentally in reaper that applied to lots of items when you thought it was only one item, changing length or playrate to 0 is unlikely to do even as a mistake.
It's hard to know what is the cause or what to do without being able to replicate the problem.
My guess is something is very wrong with your system. When reaper saved a file something happened to the file. I doubt reaper would miss out or change those values when saving.
It is also possible that a drive is slowly dying. I recently had a few corrupt files on an internal drive and turned out that disk was dying and gradually gaining errors. I think the drive had overheated and damaged it somehow. I had to do a block level clone of the drive with Gnu DDRescue because even the OS diskutility clone tool would not copy it when it hit a bad sector. This was an extra headache because TimeMachine (the backup utility) had copied the bad files as empty files, so even my backups were corrupt. I didn't expect that. I thought TimeMachine would warn if it found a bad file, not assume it was empty!
Last edited by mrlimbic; 11-06-2018 at 09:25 AM.
|