@kirschkematthias

The main reason is that you cannot cover all circumstances. If your goal is to collect only the media that is actually used — and not everything stored in the media bin — Isadora can be used differently compared to other software. See this post:
https://community.troikatronix.com/topic/8601/moving-media/10?_=1767347158370

Best Michel

@dusx

Hi there,

I would prefere a solution like Reaper: when you save the first time Isadora should create a folder, and inside a media folder (Or two for folms and picture), the Isadora show, an undo file or folder and a backup folder. In the prefs you could allow to move, or copy the files.

All this should be easy to put into Isadora, and I wonder why it is not yet implemented?!?

many greetings Matth

many greetings

Matthias

@bonemap said:

I did note that the pathnames to the assets did not change in the newly saved version

 No, The project file and Isadora need to be re-opened, facilitating the Media Search. After this search (it should find the local files) it will save the new paths when saved. I was just suggesting, making a backup of the file before re-opening the project with Isadora, since it would be easy to save and lose the remote filepaths.  I'm working on another process right now for filepaths embedded in the project file. It won't be possible to get everything, especially for advanced Pythoner projects (shouldn't need to, if they follow best practices). Right now I can find, DataArray files, Top Level Python linked files, Files linked in Javascript via read() and include(), and I am able to expand this still. I will add .oni next and try to get a complete scan.  I think I will have this script output a report, that is human readable, and can be edited by hand. Specifically, per found file, an 'Include' setting, so that specific files can be excluded from the next step of collecting, which will be handled by another script.