GP5 Loading Issue

Hey everyone! I’m having an issue with GP5 opening yet not launching, it’s starts to load up to 7% then it’s just closes on me.

I’ve tried using other daws to see if it’s a certain plug in but the others don’t give me issues.

If anyone can help I’d appreciate it :pray:t2:

I’m guessing that it is trying to load the last saved gig file, and there’s an issue with a plugin in one (or more) of the rackspaces.

Try holding down the Shift key while loading GP until you get the Temporary Startup Options screen, then de-select Load last gig file and press OK. This will load a new, blank gig.

That’s probably the best idea.

You can try to load the corrupt GigFile and you’ll probably be able to see which Rackspace GigPerfomer closes when it loads.

Then you can load the gigfile (a copy…) with a text editor, delete this one rackspace, save the file and load. If only this rackspace is corrupted, it should work.

Thank you guys! What would be the reason that other daws are opening up the exact plug in’s I’m using though?

  1. Are you on a Windows or a Mac?
  2. If Mac, is it Intel or Apple Silicon?
  3. If Apple Silicon are you using Rosetta?

Further:

  1. When this problem started happening?
  2. Can you trace what happened so the problem arised? Driver update, plugin update, OS update, …

If your gig file worked well and now it doesn’t I suspect it is a plugin issue.

The Temporary Startup Options has a logging feature. If Gig Performer starts loading plugins and then unexpectedly quits, that log will show what is the last plugin that GP tried to load.

So, disable that plugin and try to load GP. If it works, you’ve found yourself the culprit.

Mac, intel, yesterday night,

I actually hadn’t updated anything until I got the issue thinking that would fix it. So I updated after the issue

Because most DAWs don’t use as much of the functionality of the plugin API as GP does and so if GP uses functionality that wasn’t tested by the plugin developer, it can be broken.

Then there must be a crash report - please post it here.

I’ll post asap

Translated Report (Full Report Below)

Process: GigPerformer5 [1289]
Path: /Applications/GigPerformer5.app/Contents/MacOS/GigPerformer5
Identifier: com.deskew.gigperformer5
Version: 5.0.9 (5.0.9)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2024-08-16 17:56:22.0982 -0700
OS Version: macOS 14.6.1 (23G93)
Report Version: 12
Bridge OS Version: 8.6 (21P6074)
Anonymous UUID: BC4CF6FA-8337-E244-D03C-9033558674AA

Time Awake Since Boot: 880 seconds

System Integrity Protection: disabled

Crashed Thread: 0 HotFudge Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008
Exception Codes: 0x0000000000000001, 0x0000000000000008

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [1289]

VM Region Info: 0x8 is not in any region. Bytes before following region: 4380684280
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
—>
__TEXT 1051bf000-108f4b000 [ 61.5M] r-x/r-x SM=COW /Applications/GigPerformer5.app/Contents/MacOS/GigPerformer5

Thread 0 Crashed:: HotFudge Dispatch queue: com.apple.main-thread
0 UVIWorkstationAU 0x11545f194 uvi::ParameterInfo::Get(uvi::Element const&) const + 4
1 UVIWorkstationAU 0x115226774 uvi::ExportedPluginParameter::GetNormalizedParameter() const + 148

Your UVI Workstation crashed — you might want to pass that information on to UVI.

Also, try using the VST version rather than the AU version

why does it not crash in other daws?? lol im just curious

This is just wild to me cause I made a new Gig and used all the same VST’s but now there’s no issue lol

I’m
Pretty positive it’s a bug with GP

If you look around this forum, you’ll see similar threads with newer users. 99% of the time the issue is with the plugin not being written properly.

As @dhj explained:

Plugin developers rarely write and test plugins for live applications, and as a result they can sometimes shortcut in certain areas of the technical specifications because those areas don’t tend to appear in most DAW’s. However, GP will often expose those areas because it is utilizing more of the plugin specifications.

It’s not – the crash report (of which you only included the beginning but that was enough) explicitly implicates the AU version of UVI Workstation

Thread 0 Crashed:: HotFudge Dispatch queue: com.apple.main-thread
0 UVIWorkstationAU 0x11545f194 uvi::ParameterInfo::Get(uvi::Element const&) const + 4
1 UVIWorkstationAU 0x115226774 uvi::ExportedPluginParameter::GetNormalizedParameter()

2 Likes

The UVI plugin was not a VST - it was an AU

I try to avoid AUs at all costs.