Hello there,
I’m moving over from a 32g M2 machine to a new 64G M4 pro machine and spent the last couple days getting all the plugin’s installed and today was move the .gig file over. So my gig file is a bit complicated and it just crashes when I try to load it. A few more basic gigs will load but not the big 2. It appears maybe it’s global rackspace related? See attached crash report. I’ll try to upload the gig file as well.
Any thoughts?
Crash Report New Mini.pdf (7.2 MB)
Here is a like to the gig: https://drive.google.com/file/d/15lG6Kf-KAD-n7W8G_hzSTTK4xyoWb35S/view?usp=share_link
How exactly did you move everything over? Did you use the migration tool? Did GP on the new machine use the settings file from the old machine?
So I just installed GP and all the plugins and then moved my Gig Performer folder along with the lyrics sheets folder and a 3rd (from documents) that had all my samples, etc. on them. I am currently setting up the new Mac without an interface (plan on reusing the existing one once I have GP up and more or less running).
Did I screw up by bringing it over that way?
That gig file loaded fine on my machine, though of course I don’t have many of the plugins you have nor do I have any of those wave files.
However, there are multiple possibilities
You copied the old settings file over instead of creating a new one. That means that GP assumed all your plugins are already validated and some of them may not be. You should open Plugin Manager, delete EVERYTHING in it and rescan
I see there’s a plugin in your global rackspace that’s a sampler - are the samples in exactly the same folder as they were on your old machine and does the sampler “know” about the folder now or does it think it has some other folder and (maybe) is crashing
The interface shouldn’t matter
Okay, so I’m getting farther into the load before crashes and it’s appears to be that waves CR8 sampler each time. So what I’ve been doing is exporting the rackspace on the old machine, then deleting it and exporting that gig file. The weird thing is that every single one of the samples I am attempting to load/use is in the exact same path as the prior machine. Some load it seems, others do not (and thus crash). I’ll keep at it. The goal being a loaded gig file that I can then manually reload/reconnect to get back to business.
Okay, found the issue: In reinstalling plugins, that sampler (Waves CR8 Sampler) actually updated to a newer version and therefore it crashed on the VST3 versions I was running. The AU versions (which were a bit buggy in the last version) loaded okay which explains why I was getting the “some but not all” problem I described above.
Not sure I understand – did the new one crash or did the old one crash? The new version should have been able to support older versions in terms of state and I would consider that to be a bug in that plugin.
That said, this is a perfect example of what we tell people regarding updates – give yourself plenty of time for dealing with updates because even something as innocuous as a plugin update can break things.
So in my old gig file (the M2), I had a mix of vst3 and AU versions of CR8 in use. So when I tried to bring that gig file over, the load kept crashing. I would notice that it was always loading a Waves CR8 when it crashed, so I started removing those to see if I could progress. As it turned out, the vst3 versions GP was trying to load were causing crashes (assuming due to update to waves plugin) but the AU versions weren’t causing crashes. So I just removed all the VST3’s and got the gig file to load correctly. Now I’m just re-adding those plugins one at a time and pointing them to the samples needed.
Agree on the tread-carefully thing. I am running both machines side by side and won’t transition over until I have the M4 fully dialed in. I’ll tackle the interface and lights once I get the gig file dialed.
Thanks so much for the help, as always.
Don’t do that!
Yeah, I knew better but I had a working system so I didn’t mess with it. I started out with AU’s across the board but did have an issue where they would occasionally just stop sending sound. So I changed those particular ones to VST3’s. I didn’t mess with the ones that were working as intended. Since I use probably 50-60 total across the project, I didn’t want to chase down unbroken stuff. Now, with the new M4, I’m all AU.
I would be all VST - I’ve generally found them to be more reliable - mainly because they get tested on far more hosts than AUs, which are really only aimed at Logic Pro/MS/Garage Band.
Gah, I learn this right AFTER I spent hours redoing them all. I’ll let it roll for now and if I get issues, I’ll grind the switch back.
It seemed to be the fastest path to a successful load in the M4 so I’ll take the small victory.
Apart from reliability, the issue generally occurs when plugin developers use “global” data and don’t properly handle such things as a newer version (or different format) of a plugin saves some global information and an older version doesn’t properly handle data that is not valid for the older version.
I’m currently building out a large gigfile filled with 6 albums worth of songs. I’ve been pondering which plugin format to stick to. It would be a pain to have to change so many presets afterwards. I’m running Gig Performer on a mac.
Would you recommend starting out using the vst3 format for all plugins as a general approach? Or would it be wise to start out with vst? Or would the recommendation be different per plugin brand?
I read something about vst3 not responding well to PC messages but I don’t intend to have my plugins change presets mid song anyway so that wouldn’t be a issue.
Thanks
FWIW, I use VST3s (on a Windows laptop). But, not sure what the majority does.
I guess if you pick one, stick to it for future plugins unless you have a problem, then try the other?
For live performance, I’m still using a Macbook Pro from 2019 with macOS 10.14 and most of my plugins are the older VST versions. I only use VST3 plugins when VST versions are not around.
Thanks