I think you’re missing the point in that we are discussing this in the context of there being two projects and deleting in one, should not delete from the other - I know how ‘Remove Unused Media’ and ‘Empty Trash’ work and what the consequences of those actions are within a project. I think it should work exactly the same as ‘Back up Project’, where deleting files in the backup, does not delete them from the original and vice versa.
If I have a Project Template that I want to import tracks into from another project (in order to get the tracks into a templated workflow), any deleting/cleaning up I do in the new templated project, should not delete them from the original. That makes zero sense.
I suppose as the protocol is currently working, it treats ‘Import Track from Project’ as a referencing protocol, rather than a copying protocol. I think maybe the original thought process being, people who work in post/tv/film, may be using a lot of the same assets over and over and reference them all from one master project, pool/library. This hardly makes sense today though where hard-drive space is cheap, and it’s really not illustrated anywhere that this is how the protocol works.
There at the very least needs to be a clear warning, or better, an option in the ‘Import Tracks from Project’ dialogue where the user can decide between ‘Make New Copies’ or ‘Reference from Original Project’
I think I have over the 15 years or so, ran into this problematic protocol multiple times without realizing it - “huh, how did I f*** that up… uhhhm, why are all these events blank”.