OK, but you need to do this troubleshooting somewhere. I wrote you what I would do, if I were you. You need to do a series of tests to conclude what in your setup is faulty.
You should be more specific when you describe your issue.
Assuming that with “it” you mean “a gig file” and with “its faulty state” you mean that your gig file somehow became corrupted over time and causing you issues - that doesn’t happen .
Gig Performer will save your gig file normally and open it normally. It will not have “faulty states”, otherwise that “faulty state” will be saved and manifest itself on every reloading.
Theoretically, you can have issues with a corrupted gig file but that would mean that your HDD or SSD (or RAM) is the culprit, and the gig file would be faulty every time you open it.
2 different keyboards on same channel
2 diiferent models of keyboards
2 different computers
2 different gigfiles with same setlist
When using in setlist mode
And when in rackspace mode
Happens approximately after 1 hour playing
Could it be the amount of midi data being sent ? Corrupt data?
After certain amount of time ?
Gonna set up a test rackspace that I can switch to with some midi monitors in.
And also try to record all midi data
also set up a stand alone midi instrument outside of GP to see if data is being received and another midi monitor program that I can switch to if my system faults .
I have also rebuilt my gigfile to be fresh without using the setlist feature for the next 3 shows I have
2 different keyboards on same channel 2
2 different audio interfaces
2 different computers
2 different gigfiles with same setlist
When using in setlist mode
And when in rackspace mode
I don’t know this but your symptoms suggest that at some point your MIDI interface is disconnecting for a moment and coming back with a different name so Gig Performer thinks your device has changed.