I’ve lost a lot of audio files from projects I’ve done. I didn’t understand why, until I thought a bit about it:
I start everything from the same template with the same project folder. Some ideas I throw away, some I continue on. What I do, is I save a project A, then let that same project evolve into something else, which I save under another name project B. Now, this project B I sometimes decide not to continue on, so I delete project B and ask Cubase to delete the project B files as well.
Now, what finally has striked me, is that both project A and B share the same pool! (Or to be precise, project B retains the pool of project A in addition to the new project B files.) So when I delete this project B, though it has a new name, and “it’s” audio files, it also deletes all the files from the previous project I was working on!
I don’t know if it’s to be called a bug, but obviously not super-intuitive. It’s not unnatural to let other types off computer files (like Word documents or Photoshop files) evolve into new files under another names. To think that deleting this new file and it’s associated files also would delete associated files from the previous project, can be… well, a far off thought in a creative process.
If Cubase had been REALLY smart, it had known that the files were associated with other projects as well, and should have given a warning about it or simply blocked them from being deleted. But I also see that this would impose practical difficulties to implement in the program.
Just wanted you to know if you should find yourself doing the same “error”, and I’ll make a gigantic Note To Self about this!