This has earlier been discussed concerning MainStage 3.0.2.
If I open a Mainstage concert, do a few edits and press cmd-S, Mainstage copies all samples used in the concert into the concert file package.
Has anybody else this problem?
In my case, the concert file goes from 3.4 MB to 714 MB.
In my workflow changes in concerts are frequent but only rarely include changes in my sampling library. So backing up to a memory stick is quick, with the concert file being small – the full sampling library of several GB is only rarely copied.
In some cases it's ideal that samples are embedded, but it should be respect user's choice ,and the application should still default to save in same structure as the concert was originally? Right?
If I choose 'Save as…' the option "Copy sampler data into concert" is defaulted on. If option is deselected a 'slim' concert is saved, but still any samples used in the new "Quick sampler" plug-in are embedded. File in my case goes from 3.4 to 12 MB
However any regular save operation after that, still stuffs the full 714 MB into the file.
Workaround is to never press cmd-S, always "save as…". Deselect "Copy sampler data into concert" (program will then stillsave some samples) Aggravating.
Workaround 2 after closing concert: Right click "Show package content" on concert file and remove "Sampler instruments" and "Sampler files" folders. Only use if you're 100% certain the removed content is present elsewhere on the machine. It works for me, although I think Mainstage will then scan for the files when the concert is reopened as it probably has moved the concert's path pointer to the embedded…