Uli Plank wrote:Maybe it was considered dangerous, since you'd delete the original sources, and BM wanted to leave the responsibility to you?
And then, newer MacOS versions would ask you to allow such manipulations of files by a program.
That's one perspective, although "leaving the responsibility to you" is hard when (a) the underlying structure of the file storage is not clear enough that it's easy to delete parts of the raw data sources without making a mistake and (b) that wouldn't cover trimmed media.
I'd say it's more likely to result in an error by having users poking about in the data storage, than to let the program organise what media is trimmed and deleted. The argument about responsibility is taken when the user hits "yes, trim this project" for the second time having been told to take a backup in the warning dialogues a couple of times.
This is a useful facility that saved users hours of time and a lot of disk space once projects have been finished and many of us would like to see it back.
I use another mac product, ActivePresenter for online learning systems and this does exactly this function still. "Shrink project" trims all the input media and recordings to the content used, so when I've finished a piece of work, I can take my project file size down from GB to MB by removing all the content no longer needed.
That's not feasible to do without damaging something by poking around in application storage file structures and temp directories that it's hard for users to get their head around.