So you should be able to move a project damaged like this on a Mac to w Windows (or Linux) mahine, repair it ther and then move the repaired project back to the Mac.
Yes. I recall some forum posts where that definitely appeared to be the case, though it was less common. I suspect that the reason that pre-3.0 projects were less susceptible to such problems is to do with file time stamps.
I recall one case in which a cloud drive was shared, and two people tried to work on the same project, from the same cloud drive, at the same time. Audacity 2.x went to great lengths to ensure that only one Audacity instance at a time could modify a project, but cloud storage bypassed those restrictions. Both users ended up with unrecoverable corruption.
A bit off-topic, but possibly useful for readers of this thread: One way of sharing projects among multiple users that seems to work safely, is to use a versioning system, such as SVN or Git.
I don’t think there’s any reliable way that an app can tell if a drive is “normal” or a cloud drive
I don’t think a drive competency test is the way to go. I think a real time “Did It Get There OK” test might be helpful. Programs shovel data to a drive system, dust off their hands, and go home, depending on the drive system to take care of everything.
That may need to stop.
Nobody is going to sit for the system to play back a long show to make sure it’s OK, but there’s a note from the paleolithic where a recording was spot-checked before you pack up. Many of the current failures have no show to play back and a spot check will fail immediately.
Audacity already does that, but that does not help if the cloud services decides to “update” the data that Audacity has written. (The 4th little piggy built his house upon a cloud, which was not pretty when the big bad wolf started huffing and puffing!)
Would anyone be available to try to recover my “failed to read from a file?” I’m using Monterey and Audacity 3.1.3 that I just re-uploaded in case there was a recent fix. Like everyone else, podcast I spent forever editing, saved, can’t open file.
Unfortunately, in this case there was severe damage to your project. The repair program said, “database disk image is malformed; Database is badly broken. Running recovery…”
I have uploaded what was recovered which is about 5 minutes of audio in a 1GB file. I have sent you a link via PM.
…and a way to prevent it from happening in the future?
And/or details on how you fixed it? Sorry to be such a “Producer” about this, but as the team member who writes the checks, if we need a new computer, I need to know.
Yes - you are right - sorry I was so abrupt. You didn’t bother to say you tried anything, and honestly, as a lowly volunteer, I simply do not have the time to do this for people anymore.
If you have done this yourself and it didn’t work, it is unlikely that anything I could do could fix it. At what step did it fail, and what error message did you receive ?
Jademan, if you see this, I have a similar problem and don’t have access to a windows computer. Ive made a post about it, it’s the only post on my profile.
{update} I see from newer posts that you no longer do this. I can appreciate that. But if you find it in your heart to help me I’ve attactched a link to my google drive folder containing the AUP the War and the shm