Mapping Midi-Out in Setlist/Song/Songpart to new/other device

Hello, due to a conflict, I had to clean up the Midi drivers on my GP computer (win11). Now I have the problem that my Quad Cortex, which I control via Midi via the Setlist/Song/Songpart, has been given a new device name. This means that GP can no longer find it. I now have to go through all 35 songs, each with about 10 song parts/MIDI circuits, and change the MIDI device from “Quad Cortex (3)” to “Quad Cortex.” Is there a way to automate this?

Note: As far as I know, RigManager is not a solution here because I believe it only works for MIDI-in devices, not MIDI-out.

This is very annoying behavior, as it also happens when you accidentally connect the Quad Cortex to a different USB ports, which is often the case in dark rehearsal rooms or on darker stages. I would then keep plugging things in until I found the right port. But apparently Windows reinstalls the driver for each port, so the drivers slowly accumulate. And now, after cleaning up, I only have access to one driver and don’t want to play the game again until i’ve stacked the driver up to “Quad Cortex (3)”.

Do you know this dialogs when you change a MIDI Out device

Unfortunately it doesn’t work, because GP only shows known midi output devices. In my case the systen doesn’t know it any more, because I had to clean up.

But…
I solved it in a different way :-). After experimenting a bit I just came to the idea to opened up the .gig file in a text editor, just to take a look inside. It is just a xml-file, where the device name stands clearly written in all midi messages that are set up in the song parts. So it was easy to replace the name of the old, now unknown device to the current, known device via search and replace. Not a elegant, but a very fast way.

So I learned something new and solved the problem :-). Awesome :slight_smile:

When you edit the XML-File and after that you have issues…
Then you cannot expect any help, total unsupported.

Yes, I know. Therefore I’ve worked with a backup, to test it first :-).