Windows updates come fast and furious and they seem to find some was of getting them installed.
I have gotten pretty good about deactivating GP when they come up, which I did here.
This time (as is the case about 30% of the time) OSC was disabled. Okay, I am used to that. No biggie.
But, my keyboard were not responding to midi. I went into the Rig Manager and it seems to have forgotten the keyboards associated with aliases. Okay, I got this (even ‘though I do not understand the Rig Manager as much as I should). I re-associated it and things seemed to work.
Now I am going into songs and the keyboard is not triggering samples in the SAP. So, I am resetting that up.
I have a bunch of work to to do for my gig Sunday (I have about as much time as I ever would to fix this, so it is really not a question of putting off the update).
What should I disable? The SAFP? Every plugin? (I did deactivate GP.)
Yikes, this is bad. Ride Like the Wind is totally fucked up.
I am going to start up my other laptop and try that Gig file (I did not do the Windows update on that one). Although that does not have some very recent tweaks. it is okay. Hopefully that will work.
Then we’ll see how that Gig file works on this laptop.
Fingers crossed that all I needed to do was restore the triggers for the SAFP. (I started running into other issues, but I think I might have caused them while trying to fix this one).
It was not as bad as I thought it was. And I think while trying to fix things, I created a mess. So, luckily I had another very recent Gig file and was able to work from that. But even with that one:
I am pretty sure there were two things that happened (in addition to the OSC being disabled, which seems to happen almost every other Windows update).
I think one of my controllers got disconnected from the Rig Manager. Usually when this happens it is because controller 1 and controller 2 got connected the wrong order. And, although you do not like it, David (sorry), I usually just restart the controllers in the right order to fix this. But, in this case it seems like the Rig Manager was no longer connecting to the controller. Although I am not too proficient with the Rig Manager, I managed to “re-associate” that controller in the Rig Manager. [For most people here, that would have been a simple issue].
When I hit the note on the controller that should have triggered a sample in the SAFP, it no longer triggered the sample. Another area I am not too strong (I guess figure out just what I need to get things working, but once I get it right, I don’t recall exactly how it works that well). So, it turns out all I had to do was find the widget and go into edit mode. Even though the note was not triggering the sample, in the MIDI Section of widget properties, it listed exactly the note I use to trigger it. So, I just relearned it.
Like I said, for some reason, it seems like widgets controlling mixer levels were changing, but maybe I caused it. (So, my guess is user error by me on that one).
I have no idea why this might have happened.
But, I feel very confident Window updates often disable OSC in GP. That happens a lot.
In this case, it seems like the Rig Manager changed (discussed above). (I really don’t think I did anything to cause that).
It seems like something happened with SAFP samples (also discussed above).
I suspect both issue are related. (I had to “relearn” Next/Previous Song/Songpart again too in Options>Setlist.)
No, I don’t think so. I think your’e right. If those notes were defined in the Rig Manager, I would not have had to re-learn them.
The bigger headache for me (I’m not so techy) is figuring out the issue. For example, I have read posts about deeper midi issues with new versions on Windows.
I install all Windows updates in a controlled manner and to be honest I’ve never deactivated GP or anything else and have never had a single issue with updates and OSC, Rig Manager, or really anything I can think of.
I even recently installed the new midi 2 stack (not yet on my dedicated music PCs) and have not had any problems with GP. I have two rack mounted Lenovo mini pcs dedicated to performance and neither have ever had adverse effects from Windows updates.
But David is right. If all my controllers were set up in the Rig Manager (and I figured everything out quickly), it would have been a 30 second fix
Re-enable OSC
Re-associate the controller.
(Note, I’m not the only one who has run into issues when there was a Windows update. That is why the developers suggest giving yourself time if something happens and deactivating GP before you install the update).
In my experience it is the deactivation of GP and, after the Windows update, the activation of GP. Somewhere during the activation GP reports that the OSC port is already in use. After activation, I have to re-enable OSC. I don’t think Windows update itself has anything to do with it.