Default patch in GP trial has audio problems after modifying

Hello. Longtime Camelot user, who somehow just became aware of Gig Performer. Primarily a guitarist, and the wiring interface of Gig Performer is very similar to what I use in the Fractal Axe FX III, so it appeals to me and I downloaded the software and activated the free trial. Opened it, selected the key board template, and it worked great immediatly. Piano sounded pretty nice. So I changed the input from “omni” to my Keylab 88. Everything still good at this point. Now I added another input (Keylab 66) with a different VST (tried a few Arturia plugins) and made the connections to the same outputs as the piano. Remarkably quick and easy, just like all of the YouTube videos I watched! Except that I don’t get any sound out of the Keylab 66/Arturia signal chain, and now the original, default piano chain is just putting out short bursts of very staticy sound. Removing the second signal chain doesn’t help. Closing, restarting the Mac, and reopening doesn’t help. I had initially saved the modified rack under a new name, but can’t seem to find the default one to start over.

Any suggestions would be appreciated. I’ve got 14 days to convince myself that this is a better alternative to Camelot. I’m reasonably adept with midi/pc’s/signal processing, etc., but a fairly weak keyboard player!

What version of MacOS? If M1, are you running GP natively or under Rosetta? If natively, are you using any Intel based AU plugins that require Apple to run them under Rosetta? What audio interface? What sample rate and buffer size?

For what it’s worth, many of our customers are guitarists and I don’t think we have heard of any glitches like this.

Getting static after adding a plugin sounds like it could be audio processing overload. This is impacted by your buffer size and sample rate. Also look in GP’s CPU meter in the top-right corner. On my Intel MacBook, I can’t go above 50% in GP’s CPU meter before hearing static.

I run guitar plugins, and use 64 samples and 48kHz. From what I’ve seen here, most keyboard players run much higher buffers (e.g. 256 or 512 samples).

Thanks much for the reply. I’m running Sonoma 14.0 on a MacBook Pro, with 32 Gb of RAM and a 2.3 GHz 8-core Intel Core i9 processer. Full disclosure; I’m still getting comfortable with Macs. Historically more of a PC guy.
After seeing your reply, I went to check my system to get this information, and to my surprise found that everything is working fine. I was able to modify several of the default racks, changing the “omni” input to my specific keyboards, and altering the vst instruments selected. Seems to work great! Not sure what was going on before, as I had restarted the whole system 2-3 times with the same result.

So, I am greatly encouraged! Again, thanks for taking the time to reply to my issue.

Best support community anywhere!

1 Like

On my 2017 Intel MacBook Pro, I have observed that the second/backup graphics card (which gets used when you have low battery) can cause clicks/pops. It is a very underpowered graphics chip. I have disabled the switching to this card in the Mac system preferences: