@thephatmaster I ran into a similar problem years and years ago for a different application.
I found a program called “Visual Subst” that allows you to, visually, map a local folder to a drive letter.
You could setup both machines to use the same base Drive letter and build up from there. The program ran fine and I’ve never had any problems with it.
For archiving, yes, the weak link being that I’d likely forget to unite it with it its projectfolder on archive.
As to why - My understanding is that the .mlt file being in the “root” (of my video workflow set of folders) will keep the footage links working as they would be subfolders.
If I put the .mlt file in “projectfolder” the path to anything outside of that folder (e.g. titles, assets, audio that are used multiple times) will break (by being absolute).
As an aside, I really struggle to prevent myself creating nested project folders with Shotcut. I generate a “projectfolder” when I ingest / sift footage, creating the .mlt file later (which inevitably ends up in an identically named subfolder)
If you give Shotcut a “Project name” for a folder that already exists then it will reuse it without creating another sub-folder or complaining. You just need to ensure “Projects folder” is set correctly to the parent of where you keep projects.
I remember installing LinuxMint on a VM on my Windows machine. From the moment I started it up, I felt like Alice, having just fallen down the rabbit hole… Maybe one day I’ll try Linux again, but then again…
I had a similar workflow once. The multi-use assets were only a few megabytes, so I had them stored in a template folder, which I cloned for every new project. That way, the stock assets came with the template and did not need any external linkages. I don’t know if your file sizes make that practical. But if you’re wanting to do a full archive of all media, then it’s going to be the same final size either way.