I know, I should get in the habit of saving regularly, and I’m generally pretty good about it. But when I get in a good workflow I tend to not think about it, and that’s always when GP seems to crash on me.
For the record, not trying to imply anything negative about Gig Performer. GP is definitely one of the more stable DAWs I’ve used, but crashes inevitably happen setting up complex project files and songs, and I would really appreciate an option to autosave every 10 or so minutes just so I’m not losing work or having to retrace my steps.
It’s in the works — more of a version save so you have history — but we can’t say when it will happen.
More importantly, if you’re seeing crashes that are GP related (as opposed to plugin crashes), please report them (with information on how to reproduce) so we can address them as necessary.
Sure, I looked on the website and it looks like the tech support seems to be for more specific tech issues related to gig performer. Are the forums the preferred way to report a crash? Couldn’t find a dedicated section and don’t want to crowd the general thread. I’m happy to provide info however.
It depends — at this point, the vast majority of issues we see are plugin related, and often such crashes are fixed by updating to the latest version of the plugin. If it’s a Gig Performer 4 crash (or you’re not sure) and you bought it from us directly then you can report it through our ticketing system along with steps to reproduce and you should include a crash report if possible.
We will respond to the ticket in one of several ways:
It’s a plugin - go beat up the plugin developer
It’s a user error or a problem more suited to community forums - visit tech support forum for help
It’s a GP error - we will thank you and will do our best to get it fixed ASAP
If you bought GP somewhere else, then you should reach out to their tech support and let them determine whether it’s a reproducible GP bug at which point they will reach out to us.
ahh ok yeah unfortunately I bought it from Plugin Alliance and their customer support isn’t very responsive from past experience. I am using the latest version (that PA offers - not sure if they lag behind you guys update-wise) and the crash does seem to be a GP error given the circumstances under which the crashes occur. However, I did recently update to Windows 11 a few weeks ago so maybe it’s just a matter of waiting for future Windows updates to be released to provide more stability.
I wish I would’ve known the way that the software support is handled is separate depending on where it’s purchased. Not blaming anyone besides myself for not reading the fine print ahead of time, it’s just rare that you come across developers and a community that is so responsive and open to feedback so I would’ve definitely purchased from Deskew directly had I the opportunity again. Oh well, lesson learned for the future.
I’ll try my luck with PA and keep my eyes peeled for any updates. Thanks for the response!
There was no crash report, I went looking for an unsent error log but the folder inside appdata/local doesn’t even exist. Appdata/roaming has a gig performer folder but only contains my settings file. I already looked in my general options settings to make sure that I didn’t have it set to not make an error report but the option is unchecked. Here’s what happened on the most recent crash: (crashes have happened a few other times as well performing similar program-only functions, but I can’t recall the exact function, so I’ll leave those out).
I have a setlist with three songs. 1 has 3 rackspaces, song 2 has 1 rackspace, and song 3 has 8 rackspaces. I used the hotkey to delete a rackspace ctrl+shift+backspace on the third song and gig performer hung. The title bar showed “project file name (not responding)” and I waited for a few seconds and then gig performer just disappeared completely and I confirmed in the task manager it was no longer running.
A few other times this happened on my machine as well, not with this exact function but when I was performing a Gig Performer task (not relating to plugins). Similar sequence of events: gig performer hangs for several seconds and then closes completely. A few times I’ve clicked within the program and it will become greyed out and the windows dialog will appear saying gig performer is not responding - Windows users know what I’m talking about. Then it exits. I updated my PC from Windows 10 to Windows 11 a few weeks ago but it has happened sporadically both before and after the update. My software is all up to date.
Some thoughts that may indicate the issue.
List item I have a good number of plugins running in the setlist as a whole. Trilian, Keyscape, and VB3 are in a number of the rackspaces. I’m also taking full advantage of the midi routing and have Gig Performer receiving and sending out a number of midi messages with various routings. These plugins work fine in general, however, usually without any issues.
List item I was running loopmidi (virtual midi ports) midi-ox (midi translator) and midikey2key (a program for custom LED feedback on my apc mini) alongside Gig Performer. However, this is on the most recent crash. I’ve also used GP without these running and had a crash.
List item I am running malware bytes as well. Can’t imagine my antivirus would get in the way of the program but who knows.
List item Since the crash last night, I turned on the “OpenGL Renderer” option for the visual renderer since I do have an RTX series graphics card. Hoping that increases stability. Haven’t had any issues since but it’s only been a day and there’s usually several days between crashes. Sometimes multiple times in a day.
Additional hardware/software info:
OS and version:
PC Windows 11 home (64-bit)
Computer hardware:
32gb RAM, i7-8700k, 500gb SSD (boot drive and installation folder), 2tb HDD (mostly samples, some libraries), 1tb SSD (sound libraries needing faster load time e.g. keyscape)
Gig Performer version:
Gig Performer 4.1.5 unlocked from PA
Plugins involved:
Not caused by plugins since it happens when performing gig performer related tasks.
don’t know how you are inferring this unless you have absolutely no plugins inside Gig Performer
My mistake. It could be from plugins. I was just assuming since the plugins seem to be stable in general and it usually crashes when I’m doing some function with the gig performer itself without any audio processing happening within the plugins. But like I said, I do have a number of plugins running. I can provide a list if need be.
No, deleting a rackspace using the hotkey in the same project file under the same circumstances worked fine when I reopened. It seems to happen at random. The instance I described above is the only time I remember exactly what happened. I haven’t been able to notice a specific pattern. Another time was a few seconds after I had opened midi monitor, and that time gig performer didn’t hang first it just closed without warning. I understand I’m not really giving you much to work with in terms of getting to the bottom of the issue so sorry if I’m wasting your time. I wish I could be more helpful.
I’ll just keep using as usual and I can report back to this thread if it crashes again?
Just an update in case anyone finds this thread in the future and has a similar issue. Turning on this option has increased stability immensely. In the time since I created this thread, I believe I’ve had only one single crash and it was likely plugin related when loading a large .gig project file while also having google chrome and a few other unnecessary programs open. If you have a dedicated GPU and are experiencing crashes like I was, modifying this option to “OpenGL Renderer” may solve your issues.
Besides the general GP support organisation, this community can also help you in tracking a bug. 