[Solved] I thought that the Windows install of 5.3.3 had trashed the USB connection to my Nord Modular G2X but it turned out that the USB connection had broken

:sos_button: :person_tipping_hand:

It seems that the Windows install of 5.3.3 has trashed the USB connection to my Nord Modular G2. It just happened on my Dell desktop PC and laptop PC, both running Windows 11. This is a big problem for me. The G2’s software editor needs the USB connection to the hardware, without which I’m unable to see and manipulate the synth patches that I’m in the process of translating to new virtual-only versions in GigPerformer.

Can you give me a list of the audio drivers/DLLs that were updated since the previous release? Hopefully I can figure out which one has overwritten a driver/DLL that the G2 editor needs…

The Windows installer doesn’t touch anything related to USB or other drivers, it is solely installing (updating) the GP application. Other than the actual update of GP itself, the install process is identical to what was used in 5.2.2 and even the one before it.

Something else is going on.

Just to be clear, we do not include nor modify any audio drivers. We are solely updating a regular Windows application.

That can’t happen :slight_smile:
Gig Performer never touches any drivers.

It must have been something else going on.
System update?

No system updates have been installed on either PC, since the 8/12/26 Windows updates. The G2 Editor ran successfully and connected to its hardware after those updates.

I created system images on 8/12 before enabling those updates to be installed (my system policy won’t let them install automatically), so I will now have to do system restores to try to get the G2 back to normal.

Even so

even so, the installation process insists that you first terminate all audio applications…

Can you post a screenshot of that dialog?

Gig Performer cannot mess up, overwrite, or corrupt your macOS drivers. As a user-mode application, it interacts strictly with the operating system through standard APIs and does not have the administrative privileges required to alter system-level driver files.

it’s Windows, not macOS

The same applies to Windows.

For the same reason, Gig Performer can never cause BSOD (say).

So, after much testing I have good news for Gig Performer, but bad news for my Nord. It looks like the USB port on my Modular G2X keyboard has died. This happened years ago on my very first G2X, which I still use on stage, but then it was the result of a lot of un/plugging the USB cable while the G2X was still powered on – turns out, as Clavia informed me, that this can fry the port because it’s not hot-pluggable. I had to have my repair person send the synth to Sweden for a new $$$ motherboard. That will no longer be an option.

On my MacBook, last time I checked, the G2X driver and editor software were working fine within Parallels, in a Windows 7 VM. So I tested it there, and now the VM-hosted editor is failing to see the G2X. I’ve swapped out USB cables and the USB2 hub they need to connect through, but still no connection. So it’s pretty obvious that the port has died.

I apologize for causing alarm and blaming the GP5 update!

No worries, we are very confident in what Gig Performer can and can’t do. :slight_smile: