I am creating a few complete Gig Performer setups and need to be able to easily share them with the confidence that an end user can easily download the setup and open it on their own particular computer.
Sometimes this will be MacOS, sometimes it will be Windows. I might make changes on a windows machine and want it to be reflected on the Mac as well and vice versa.
I tried to make a new folder in Options/Locations and put everything in there, but it only partially worked
I want to include the gig files themselves (with all the wiring and racks that entails), extensions, scripts (some of the scripts use #includes to make things cleaner), and audio utility files for setting levels, as well as triggered samples.
How should I set up my folders to make this the smartest, most pain free transfer possible?
I was planning on making the folder on google drive, and realize that even then, Windows and MacOS are going to treat the same google drive as different entities when it comes to paths.
Only thing that comes to my mind is Dropbox and GDrive or some other service, but that may be dangerous. Whatever service you try, it must be configured to keep and use offline copies. Otherwise, loading gig files and other files will case crashes (unused files are pushed to cloud and only a some kind of a “shortcut” is kept).
Its not so much about the cloud service (or even sneakernet), but knowing that all the paths ae corect, like what sort of folder structue should I create? I tried some symbolic link stuff and it works, but still very unclear
You have to define symbolic links are whatever the correct wording is and then use this to include your resources as audio or MIDI files in Gig Performer.
@npudar I’m finally revisiting this topic as our products are nearing market and I’ve decided on the initial hardware we’ll be recommending.
I am hoping there is a comprehensive and updated best practices for sharing entire setups between computers for everything we’ll need to do a restore from backup or transfer to a new computer.
Lets assume all the computers will be Windows, running Windows 11. I’ll need the gig performer files, all the script files and any utility files to be able to share and/or restore from on a new or newly formatted system. I’m still not super thrilled with symbolic links, hoping there’s a simpler and seemingly more robust way to deal with auxiliary files like scripts.
I’ll wait for someone who knows what they’re talking about (not me!)
But, if you are not dealing with samples, I would think you could just create the default file structure to work properly on the user’s C drive. (Samples might be better on a separate SSI drive). I wouldn’t think symbolic links would be necessary.
I would think you’d have a separate default file structure for Macs (but do you have to worry about Rosetta, Intel Macs, Tahoe, etc ? I have no idea.)