I have quite a few gig files each containing about 25 rackspaces. Ive been going through them and updating where needed. After working on a couple after boot up, GP just refuses to load the next chosen gigfile. Multiple rapid mouse clicking will sometimes load the new gigfile, and even right mouse clicking and then “load file” can work. However, more often than not, I have to reboot the computer before I can carry on. Obviously, something is preventing Windows from loading the next file. Is there a way to send a script or other to Windows so that any obstacles are removed allowing GP to load the next gig file? This will save endless Win reboots.
How exactly are you loading the next chosen gigfile? Maybe some plugin is refusing to close down quickly or takes a while to close down.
Edit: I don’t understand your title. Is gig performer loading SOME rackspaces and not others?
Ok, here goes (I hope).
- Boot up GP and load first GigFile
- Edit and save first rack space.
- Load second rackspace, edit and save
- Try to load third rackspace and it will not load or respond in any way.
- Reboot and start again (third rs loads fine on reboot)
- Process repeats.
I must say that I have extended sessions whilst editing.
Are you loading Gig Files or Rackspaces. As you know, they are totally different things. (Your first post refers to loading multiple Gig Files, but your last post seems to talk about loading rackspaces (importing them? Predictive Loading?)
I am a bit confused.
Sorry. Load gigfile and edit rackspaces. Then save.
Repeat with other Gigfiles.
Eventually get gigfile that wont load. Computer reboot required.
So these are all additional “instances” of Gig Performer? Adding more and more instances would seem to eat up a lot of ram.
Or are you closing out a Gig file before opening a new one? In that case, the culprit may be that the first rackspace needs to release ram (?).
But, let’s see what others say.
Yes, save then quitting one GigFile before loading the next. After two or three GigFiles have been edited and saved and despached, the next GigiFile I want to check and edit will not load. Reboot required to remedy the situation.
Thats what I was thinking.
Pretty much every time I close down GP, I open up the Windows Task Manager and terminate (“end”) Gig Performer (before shutting down the laptop).
Maybe do that before opening up another gig file?
Sound advice. I will try it.
Ok, so i had another non-start with GP today after I saved and deleted the edited version I had been working on. I brought up Task Manager and GP was not in the list. But there was a huge number of other items there. The list was so long I didn’t bother doing a screen shot. I have optimised the PC using the guide, and I know I have asked this before, but why are so many items in the list? How can I stop them from loading? More importantly, how can I find out which ones are not necessary for audio with GP?
Without seeing that list, I really don’t see how anybody can answer this.
That’s like going to your doctor, telling him to cure you but without providing your symptoms😱
The issue may be the order it is listed. (I think default is CPU use order)
Set it to list in order of ram use. I suspect GP will be on top. End that task and wait a few seconds. You should see it quickly release ram.
In my case Arturia Manager (or something like that) is usually 2nd in terms of ram use. I’ve been ending that task too.
That’s the way it is in Windows. No reason to stop the lot of them. They are background processes that Windows needs to run. I have nothing special going on right now, and my number of background processe are 91.
1 Like
Well, I found out what was happeneing. I brought up the Task Manager and there were six instances of Gig Performer sitting in the list a little way down. However, they disappeared one at a time in a few seconds, and had all gone before I could take a screen shot.
Now is a new day (here in NZ), and some the GP instances may have been from yesterdays session (not sure about that). After the TM had cleared itself of GP instances, the new gigfile loaded just fine without a re-boot. So I guess my question would be, Why was GP holding on to past gigfiles that had already been shut down?
I am not sure if the list was in ram order or cpu.
It seems weird that it held onto ram so long and then released it just because you opened up the Task Manager.
In any event, the good news is everything loaded fine.
You might want to just go into the task manager and terminate GP every time after you close GP. This has been helpful for me (otherwise it takes a long time to release ram and I get an error message when I try to shut down the laptop).
Probably a plugin not terminating properly
Good advice. I will do that from now on. Thanks to all who have contributed in helping solve this issue.
Just a follow up. Ive been using task manager on a regular basis now since I last posted. I have noticeed that when I quit a large GP file, another GP icon appears below about half way down the list. This icon is the main one that lives in drive C . It holds onto quite a bit of ram as well and takes quite a few seconds to clear. So I guess my questions are;
1 Why does the second GP icon appear in the first place?
2 Is the anyway to setup ram release automatically?
I have not seen that. Could you have two instances running?