Hi guys. I’m a little desperate by now. I’m new at Gig Performer (still using trial mode) and running on a SER8 (win 10, 32 Ram, Ryzen 7 8845HS). I’m using various Vst’s and yesterday, in a wedding rehearsal (which is about to happen next month) I had various crashes. I’d like some clarification to understand the crash reports. I’m a nwew user so I cannot post them here. I wonder how I can share with you.
First of all, per our guidelines, we do not recommend using the trial version for real shows….the trial is intended to allow you to test the capabilities of GP so you don’t have to buy it until you know it will work for you.
That said, without providing any information about your system (, audio interface, drivers, controllers, how everything is connected and so forth) and a crash report, it’s pretty much impossible to diagnose your problem.
Most likely it’s a plugin but really can’t speculate without information described above
Edit: we upped your privileges so you should be able to upload crash report now. Please compress it first
1 Like
Thanks for your reply.
I’ll probably buy it cause I’m enjoying it a lot. The crashes were those on a txt file.
My rig:
Arturia Key Lab 88 + Akai Mini Plus
Arturia Mini Fuse 1 (audio interface)
Computer (SER 8 Beelink, 2 ssds 1tb Nvme, 32Gb Ram, Clock around 4 GHZ, Ryzen 7 8845HS)
I’m using Keyscape, Swam vsts, montage, spitfire and a lot of other vsts.
CrashRpt-Log-20250923-230743-{a632e6d5-cabd-4020-a894-79706105fb5d}.zip (12.4 KB)
Please attach the log per the instructions provided in the link above.
As far as I can see this are only reports of creating the crashdump, but the crashdump itself isn’t there. I kindly and strongly advise you to follow the instructions @npudar pointed out.
@Fsilvanoa yes, Frank1119 is correct. Please follow the instructions provided to provide the actual crash reports.
I was offline during the gig.
I`m checking in the Event Viewer and there are no events on the date and time of the logs registry. I saw some reports on 1001 events from earlier days but those did not close the gig performer - and i could not notice them.
So it seems all I have are those txt files… unless there`s another place to search them
..
The crashes that happend during the rehearsal were on 25th Sep…
Then please do your best to cause the crash and then post the crash log here.
I suspect that one of your plugins is crashing.
1 Like
Have you looked in C:\Windows\CrashDump for reports?
Hi. I bought pro edition. And I’m trying my best to fail - at the best side of the meaning. Right now I just tried to open Gig Performer and another crash just happened. Twice. I cannot find the zip file cause it seems it failed to send the error online.. Any guesses?
CrashRpt-Log-20251001-174907-{5537732f-cc36-408a-b999-cfd0ad327410}.txt (18.5 KB)
CrashRpt-Log-20251001-173649-{c2a4d8a6-9897-404a-85f2-8b2d096e8d78}.txt (18.6 KB)
I just found the paste crashdumps. Errors from 23th and 27th sep were there. Could you please check? (today’s errors are not there).
CrashDumps.zip (11.8 MB)
Thanks for your confidence. If the problem is in fact in GP (unlikely but hey, could be) we will certainly attend to it quickly.
Do you have the xml files that should be there along with the full dump?
I’m trying my best to find them. They are not on that paste.
@dhj and @npudar . I wonder the reason I cannot send the error when it asks me if I want to. I click on “send” but due to some reason It cannot go through, as you can check on the “sending error report” that I posted here in the forum. Seems there is an error on :”Server response Code: 522”. That time I was fully connected. Maybe this is causing the missing xml files or something else…
No, don’t send them. Export them.
See this how-to: How to post a crash log on Windows
Hi @Fsilvanoa,
I checked the dump files, it seems that BBC Symphony Orchestra plugin has crashed.
Can you please try to remove this plugin temporarily and see if it is not crashing anymore?
2 Likes
Interesting – that’s Spitfire? They have started using their own plugin for much of their content.
@Dadi it makes sense.
The opening error on oct 1st was due to spitfire. After trying to open Gig for the third time, I opened spitfire audio app first then opened gig performer. Then it worked out.
It seemed that spitfire needed a direct access first. Could you please tell me if the dump files that you analised were from 23th and 27th? If yes, so all errors were caused by that library…
yes. Spitfire audio.