Exporting Gig Performer Setups/Cross Platform Sharing

@npudar suggested I make this thread

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.

What should I be doing here exactly?

Maybe look at how Narfsounds has handled similar issues?

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).

Take a look at this community article: Dropbox Backup And Workflow

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

Yes, symbolic links should work: When your files are in different places on different machines - Gig Performer®

How do I get things to point to the correct folders, or what folder structure should I create to make this as sensible as possible?

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.

Can you offer any advice?

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.)

Only this one: [blog] Gig Performer Maintenance: Save, Export, and Backup

@npudar symbolic links (or anything else I have tried) do not seem to work for the Audio File Player, but seem to work fine for the Streaming Audio File Player

Is there anything I can try?

Or, is there any reason not to use the streaming audio file player for samples? I have maybe 4 of them. One per song. Streaming Audio File Player is happy to look in multiple paths across platforms where Audio File Player doesn’t seem to

For SAFP, you can use this: 8x sample player using the internal SAFP (GP 4.82 and later)

thank you!
I think I need some big time help now, I thought the point of aliases in rig manager is so I could change hardware and still have things work. I make the aliases, but they cannot control widgets no matter what I do. I am at a loss. I’d try doing those with MIDI Control Alias on the right side of the rig manager screen, but I have two pedals that do a long press. Both the mac and windows computers are using a MIDI Captain controller running the same configuration page

Do you know this?

Cany you export your rig manager settings and upload it?

Maybe this compilation can help: Rig Manager [resources]

Thank you, this mostly worked but I have some long press functions and without an editor, I can’t map to the MIDI control aliases

OK, so the first Message sent from the controller is learned in Rig Manager?
And learning a widget is not a problem as you can manually edit the MIDI message, right?

My pedal has a short press value and a long press value. I I try to learn it in rig manager, it can only ever get the short press value and there is no editor available to enter the number in manually…I think I’m answering what you are asking but I’m really over my depth here