Hi.
I just created an extensive document outlining the problems I see with Cubase’s file management system at the moment.
I am not here to learn about workarounds, as I already have them for each of the points I address. I wouldn’t create this document though if the workarounds were easy and efficient.
Whenever I come up with feature requests, I try to respect the already existing Cubase workflows. If anything I suggest messes with your current workflow, please let me know in the comments.
And if you agree, please upvote this as it is quite near and dear to my heart and would drastically improve my Cubase workflow 
Three Issues I found with Cubase’s file management 23f641e068534a1381f6ac4153fe9b21.pdf (1.8 MB)
Hi,
Problem 1:
This is how is Cubase designed. If you don’t want to share the Audio files among multiple projects (even if they are backup projects), don’t do it. Don’t save a version of the project. Make a Back up Project instead.
I believe the argument is: It’s a poor design choice.
There are many ways Steinberg could keep track of what audio files are in use by a project.
It’s not always feasible to create copies of audio files every time one wishes to save a new version of a project.
1 Like
+1 This is exactly my point.
I understand that this is how Cubase is currently set up, but I think I did a good job explaining why it would be a good idea to change. I don’t see any upsides to the current system anyway, in which only one project at a time can be held up to date with the audio files 