Here I am, just wanting to start up Gig Performer, latest version, and mess around. I don’t blame GP for this, I blame Microsoft. I’ve tried 5 times to open GP5 and it never opens. Task manager shows it is running but it never displays the UI.
A little beckground. I rebooted my Win Home laptop. Installed some updates for Blue Cat Axiom and Scaler 3. Rebooted. Then when trying to open GP5, it always has an issue with my Audio interface.
It always goes to the stupid Windows Audio and I have to re-select ASIO. Very annoying. I don’t think this is a bug or GP issue, but rather an OS issue.
It also seems like if I start Scaler and get it to work and then close it and then open GP5 I get this audio interface issue. Windows doesn’t seem to be able to handle this switching from one app to another. I have to reboot every time I change from one App to another.
This is so annoying since I have spent so much money over the years on computers and software that you would think Microsoft could make the OS work without all this mess. Maybe it’s just my night and Microsoft AI is messing with my computer.
Sorry for the gibberish here, I just had to vent, and since I was really wanting to start GP5 and have a jam session, I just had to let it out.
GP is my favorite program for quickly creating a session with some VST’s and jamming.
I kind of wish I had gone Mac but I see a lot of issues there too. I guess they keep changing things and messing things up so they can get more money and never fix anything. What a scam.
Well, the Group Policy Editor (gpedit.msc) is not included in Windows Home edition (10 or 11). This feature offers more controllability, which ultimately can lead to better stability, i.e. preventing system-wide interruptions during a performance.
It’s very easy to upgrade to professional - I bought a licence for around $10 from one of the many sites selling licenses (presume they are unused corp licences). Just entered the activation code and it was done, no issues since.
Would definitely advise having pro, to be able to control update schedules.
Having said that, not really sure Pro is going to be able to solve the interface issue you’re having. Onboard and external interfaces should be able to co-exist without this happening, so not sure what the root cause is.
I’m not sure I agree with this statement. I’ve been the head of IT for most of my life and the only big difference between Home and Pro is that Pro allows businesses to connect that PC to a Domain network and be able to manage the PC via that domain environment.
At the heart of it though, Windows Home and Pro are no different. I personally don’t think changing to Pro will solve this issue. The fix is most likely driver related:
If the computer is a name brand, make sure you update all the drivers for that make and model. HP uses Support Assistant and Dell has their own utility as well. Making sure that your PC has the latest is critical because they all pertain to the core of the computer (BIOS, Hardware Drivers, and Brand-Specific Software Updates). If your computer was custom built, then good luck hunting down component drivers because you need to visit each of those manufacturer’s websites, know the model numbers, and hunt down drivers and firmware manually.
Then make sure the drivers for all your sound gear is up to date.
THEN
I would look at your USB Interface settings (Device Manager → USB Controllers) and set your USB devices power settings to not save power under the Power Management tab. Again, making sure your motherboard firmware is up to date and intel/amd chipset drivers are as well will ensure they are squeaky clean. I would also do a test - plug your Steinberg interface into a different USB port. What port is it currently plugged into, USB-A style or USB-C style port? There are known issues with Steinberg where it fixes issues forcing certain brand USB ports to USB 2 speeds.
I don’t use Windows any more but I would have thought that group policy configuration would be very valuable for optimizing Windows and that’s only available in Pro
OK, yeah, true. In fact, I probably quoted npudar out of context, out of haste (multitasking with a Cisco phone system / Exchange issue). Everything he said in that quote is true.
Also, your statement is true as well - local GPO editing is something you can only do in Pro, and being able to do that using regedit or PowerShell will be a PiTA, plus doing it via those methods can be rewritten with Windows Updates.
What I was really trying to say was that I don’t believe that having Gary1 buy Windows 10 Pro is the solution here. yes, he can optimize his machine better, but I don’t believe that being the source of his issue.
