Dears,
have recently upgraded from Win10 to Win11. Have also upgraded my hard disk to 2T by cloning procedure. All went fine. Have also reviewed the Ultimate Guide for Optimization on Stage in order to follow the principle less is more. Don’t know if I have killed to much services or what, the fact is that now when I open Gig Performer all is fine, but when I try to load the last revision of my setlist, Gig Performer freeze at 95%. Even waiting for long time, it doesn’t change anything. Am obliged to abruptly end task with task manager. After that, if you try to open again Gig Performer, it doesn’t work. I need to restart the pc. Any suggestion to analyze deeply? Thank you
Just some thoughts:
- Does an empty file load?
- Rescan of all plugins?
- Are there samples stored on the new drive? Are they in the same place? Same drive letter?
- iLok dongles? There should be a popup, but sometimes it hides other windows.
If you kill gp using task manager, is gigperformer5.exe gone? Also in the ‘details’ tab? If not, then Windows cannot kill it properly, probably because it us waiting for an I/O to complete (could be disk I/O, network, but also an audio interface)
A not so nice way to investigate where the loading stalls, is:
- Make a copy of the gigfile!
- Did I already mention to make a copy of the gigfile?
- Open the copy gigfile with a text editor like notepad or notepad++ (not Word or something like that!)
- Remove some songs and/or rackspaces
- Save the file and see if it opens in GP
- Repeat until you’ve isolated the culprit
This procedure is only meant for diagnosing the problem. Poking around manually in the gigfile is not supported
2 Likes
That’s also a possible issue….some plugins do licensing protection on Windows by messing with underlying hardware, checking physical devices are the same, storing data in a way that thwarts cloning.
2 Likes
I guess I might want to know the last plug in it showed loading before it stopped.(?)
1 Like
While starting Gig Performer press the Shift Key
This opens up a dialog box where you can enable logging
Then load your gig file.
In the logged file you should see what is going on
But you must not use predictive load
1 Like
Dear all, thank you for all of your advices.
Starting from the last, the temporary startup options, I did the procedure and enabled logging. I don’t know however where to find the mentioned log file. Sorry for little knowledge.
The funny thing is, after I did that, my gigfile opened up!
I would say also, sake of good order, that even before, when opening an older version and only after that the last version of my gigfile, everything went smooth. Now, as suggested have selected Enable logging on, hand have de-selected predictive loading. Having done that, the loading procedure now is super slow and requires several minutes. Last but not least, the advice of opening my gigfile with a notepad, I did that, but having poor knowledge of scripts i closed after a while without changing anything. Cannot say now the problem is solved 100%. Will try again in the next days. Thank you meantime
Of course - because, without predictive loading, every single plugin needed has to be instantiated.
Also, some of your plugins may be trying to connect to their developer servers and depending on your internet connection, may be getting delayed.
How much RAM do you have and how many plugins are you actually loading?
1 Like
Hi, 32GB of RAM. Plugins about 15 (I have more but have disabled what i don’t currently use). Rackspaces about 40/50. Setlist about same may be less. Have found my logfile (enclosed). Today have just tried again and it works properly. I should say it is solved. Can I go back to predictive load. Do I have to disable logging? Thank you
GPLog2025-07-13_22-10-18.txt (28.4 KB)
Logging is only enabled when you enable it.
Next time you start it the normal way logging is off.
Yes please enable predictive load and see if the issue happens again.
Tried accordingly. Again up and running. Super fast!
Thank you
Sorry guys. Problem persists. Here enclosed the log file. Doesn’t say anything special to me. Am always obliged to end the task with task manager. The second time, when I press shift and enable logging, it works. Hence have a workaround in place. Still this is annoying. Any help appreciated
GPLog2025-07-18_21-35-43.txt (28.1 KB)
Maybe (while you are waiting for someone who really knows what they are talking about), I might consider creating a duplicate gig file and (in the duplicate Gig File) remove the song Crocodile Rock along with all rackspaces used in that song and see if the problem persists.
Maybe that would narrow the potential problem a bit?
(Or maybe wait until DHJ, Paul or someone else with more knowledge than me posts).
Dear @jeffn1 , thank you for yours. Can try anything, any reason why Crocodile Rock? You notice some inconsistency in the log file? Thank you
May be it’s just because it is the last of my setlist? It could be a logic reason. But please consider that when I record the log file the loading is always successful. When it happens (and it always happen at the beginning) I never had the chance to record a log file when it crashes. Strange enough I know. Never happened when I had Win10.
Yes, that was my logic, but it likely off base for the reason you mention.
So, you think the problem starts right when GP starts loading the setlist?
I don’t have any good suggestion…
Wait, are you saying that just turning in logging solves the problem?
Yes, always. Tried once again, as first things after starting my pc, few mins ago and again, it worked.
I wonder if the logging is slowing the loading down just enough to allow whatever plugin is causing issue to load properly.
Yeah, this may be a very obscure timing or race condition which would also explain why it worked on your older OS. Not sure right now how to address this one without reproducing it but I suspect @Dadi will have some ideas.
Thank you. Just for my knowledge. When it stops, it stops here:
The windows showing percentage loaded remains blocked with written “Loading song and setlists..” and showing 95% as percentage of loading.
At that time the plugins seems (are?) already all loaded succesfully. Can we exclude them among the possible causes?