I tried to search for this but didn’t have too good of an answer. I’m still having some issues using symbolic links and google drive cross platform. I wonder if there is some way to export a gig and have all of its scripts (even if you use the include command for including other scripts in your local and global script files) included in a zip or something. This would be great for backup and sharing as well
This issue applies to scripting as well as referenced audio files, sheet music, etc.
It probably wouldn’t be terribly difficult to build an “export” function that sticks all the referenced files in an archive of some sort, but how would you want the use of that export to work?
Specifically, if somebody else were to import it, where should those included files be placed?
It’s kind of a similar problem to packing up code with /include files that reside outside of the tree for the code you’re distributing. It’s easy enough to stick them in a tar file, but whoever un-tars it may not want them in the same place, or the same directory structure may not exist, so what do you do with them?
Creating a script of some sort that locates and copies into an archive all the referenced scripts and external files for a given gigfile probably isn’t difficult. It’s what to do with them when un-archiving on a different system that’s tricky.
Ahh good point. I suppose if there were a default unarchive structure, that could be a good one for putting your setup onto a new rig quickly.
I guess if I could figure how to make symbolic links work more easily and reliably it wouldn’t be such a big deal but I figure in an emergency, it would be great to have a way to be able to pull everything you needed at once
maybe this could actually create the proper structure on the new computer as well when importing?
In my setup my sheet music and audio files are stored on a fileserver. If my fileserver is down all that stuff fails to load. Same would be true if it was on a portable drive, or if it was in the cloud.
How would the importer choose what path to create for drives that are not accessible? And if it did create paths it would have to adjust the reference paths in the gigfile to have it looks there. So in your case the import process would have to change your script to have it look in a different location.
This is all possible, of course. I’m just not sure if it should be a built in gigperformer function. If it were to be a built in function I think in order for it to work consistently it would probably have to make a decision like “all referenced files will be placed in the GigPerformer/whatever” folder and have to adjust the file paths in the gigfile accordingly when exporting.