HI, I just upgraded to GP4 and certain plugins aren’t happy working at a 96K sample rate. Arturia SEM causes the main audio output to be distorted ( a bit like bit-crusher) and this still happens even with a large buffer size. This causes the CPU to spike at 100%.
Also reveal sound Spire steps it’s filter cutoff when moved or automated. GP4 has also crashed when changing buffer size. I have the crash report if anyones interested.
This doesn’t happen in Mainstage (v 3.5.3) or if I have the same set of plug in inside of Logic pro (1.5.1)
Mac OS 10.15.7 with a Mac Pro (2013) with a 12 core processor and 64 GB Ram. RME UFX+ interface.
Any ideas?
Do they work with the Same samplerate in GP 3?
Can you upload the crash report?
Are you using AU plugins in GP4?
I’m just about to try that
Yes, I’m using AU’s in GP4.
GP3 has the same issue with Arturia’s SEM.
Crash report below
GP4 crash report.zip (39.4 KB)
No, it’s the same
When you take a look at the crash report, do you see that a plugin is crashing?
Keep in mind that GP demands more from a plugin than for example logic.
The crash report is gobbeldygook to me I’m aftraid.
The Arturia plugin crashed
Thread 0 Crashed:: HotFudge Dispatch queue: com.apple.main-thread
0 com.arturia.component.SEM-V2 0x0000000121d02e08 0x121cfa000 + 36360
What happens if you use VSTs?
Most performers use 44.1k, perhaps 48k — curious as to why are you running at 96k?
I’m the MD for a poplular electronic pop duo who are about to embark on an Arena and festival tour of Europe and then North America. We use Digico desks and run a MADI system for all audio, and this is at 96K
I think you should contact Arthuria Support.
They know Gig Performer and will help, I am sure.
I can contact Arturia support, but the issue happens only with GP.
It works fine in Mainstage…
I’m trying to get away from mainstage which is why I’ve purchased GP4. But, as I’ve said, this issue only happens in GP
Ok, I try to reproduce with RME audio interface.
Thank you. I’ve just contacted Arturia support as you suggested.
Try loading an empty gig - then switch the buffer size and quit.
Then try loading your gigfile again — some plugins just don’t properly handle requests to change their sample rate and/or they do some funky GUI stuff when they shouldn’t. The fact that that works with MainStage doesn’t really prove anything…
This is what I did
Started GP
Set Samplereate to 96kHZ
Loaded Arturia Sem V2 AU
No issue when playing
Ok, I did the same, loaded an empty GP session, and I can load the patch on the SEM V2 and it plays fine.
But, if I load the rackspace from my concert. It glitches as I described above.
Is this because
1: It originated in GP3?
2: This rackspace has somehomw become corrupt?
How old is the gig?
Did you update Arturia?
What happens when you export a rackspace in GP3 and import it into GP4?
What else is in the rackspace? How many rackspaces do you have?
Try this:
Deactivate Arturia Sem in plugin Manager and then load your gig.
Then activate sem in plugin manger and replace the sem plugin in the writing view by the sem plugin.
This is just to see, if the plugin state of sem stored in the gig file is maybe the root cause. Das