Quote:
Originally Posted by bogo
Ok this one has the parsing error but looks readable into notepad.
I did a lot of takes. I'm wondering what are all those TAKE NULL.
Reaper was in autosave (15 minutes). I can open the .bkp but it's a big mess. Missing files and a lot of empty takes.
Next time I will reopen the session after closing it before leaving the place and see if it plays fine.
|
This file at least looks like a real rpp, but it is not the full file, there is a part missing at the end. The last "<TRACK" has no ending ">".
I don't know about those "TAKE NULL" but I guess those are just empty takes, sometimes Reaper generates those. No, I definitely think that the problem with this file is that it is cut off, there should be at least two ">" at the end, one to finish the "<TRACK" tag, and one to finish the "<REAPER PROJECT" tag, both of those are missing, and maybe more (the last track has no source file associated with it).
One thing you could try with this particular file is to add those missing end tags ">", see if Reaper can parse it.
But that does not solve the problem of *why* these files get corrupted, or how to avoid it.
Do you have W10 on all computers that you share this drive between?
And on one of then the OS is 32-bit, but on the others it is 64-bit, I guess. I do not think that either Reaper v5 and v6 nor 32-bit/64-bit Reaper would cause this. To me it seems more like some kind of OS issue.
For sharing drives between computers, I would use FAT32. Of course, that limits file sizes to 4GB, but with audio that is typically not a problem.