A few clips say "file missing", today. Everything was fine, yesterday.

[Watchful]

I'm wondering if this is a OneDrive trying to helpful issue, and moving the file to the cloud and leaving only a pointer behind in the original folder.

[Ally007]

Thank you, Pough and Dysjoint. Your suggestions are helpful. I will take heed of them. In this instance, I managed to rebuild the missing clips from the recordings files. I'm not sure if they were the actual files that were missing or not. But they were close enough. It took me over 6 hours, this time, so I hope I can figure out what causes the issue. I'll have to get the habit of naming all recorded clips with a more explicit name, as Dysjoint suggested. Then I'll be better able to determine whether the files are missing or whatever. Anyway, now that I have a complete edit, I have archived it. I hope this means I can get that complete edit back, even if something happens to the recorded clip files in the "recorded" subdirectory of the project folder. What do you think?

Are the files there? Are they not there? Are they somewhere else? Are they in the trash?

I couldn't really say. I went through all the recorded files in the project folder, one by one and found ones that were close enough, after playing back the likely ones, from start to finish. It took ages.

Rename every good take with a unique name (project name, instrument, take number etc) and set Waveform to also 'rename source file if it is in the project folder'.

And, I geuss, set the 'Renaming mode' to 'always rename source file' (i.e., even if it's not in the project folder), I guess, so that you can search the entire computer for it (if you can remember part of the file name). Would you agree?

[Ally007]

I'm wondering if this is a OneDrive trying to helpful issue, and moving the file to the cloud and leaving only a pointer behind in the original folder.

I uninstalled OneDrive a couple of weeks ago, as I never use it, but it could have caused the problem prior to that, for all I know.

[dysjoint]

And, I geuss, set the 'Renaming mode' to 'always rename source file' (i.e., even if it's not in the project folder), I guess, so that you can search the entire computer for it (if you can remember part of the file name). Would you agree?

For me? Caution! No, never, it would break my setup. I often drag and drop samples from a large sample collection and I have the setting to 'always import into the project'. THEN I am free to rename the source file (it's a distinct copy inside the project now) If I didn't import and renamed the file regardless I might end up with the dreaded 'missing file' in older projects that also use that sound, from back when I wasn't so organised.


So it would work for your recordings but I'd be careful about setting and forgetting that particular option in case you reuse some files in future projects or edits.

File: recorded into the correct project folder (or imported in) with a unique name and the entire project backed up. A triple failsafe, you shouldn't go wrong.

[Peter Widdicombe]

I've always been a little leery about using OneDrive. It has caused me grief before - it perpetually tries to back up files with changes. Sounds like a good thing, but when a file is continually updated and potentially large, it can cause OneDrive to get backed up and corrupt things.

I normally work on file areas specifically excluded from One drive; and periodically copy what I want there for archiving. So my Python and .WAV files that get logs and regular updates don't get unexpected updates.

Plus, that OneDrive "files are deleted everywhere..." concerns me.

[Ally007]

I've always been a little leery about using OneDrive.

Me too, and that's why I've never intentionally used it. My own leeriness is mainly because I don't like putting my data into the hands of some other party, and hoping they won't destroy it or misuse it.