on my win10 with GP4 I face following problem since monthes.
After some “settings” in GP our E-Drum TD-27, which is connected via USB/Midi,
was not triggering sounds anymore. On incoming messages I saw the litting of the little green light, paralell to the orange one below.
I thought it would be the cable/ hub/ win and checked and exchanged everything.
I run “USBDeview” to eliminate/ deinstall all not used, from win stored, old usb connection etc…
Yesterday I figgured out what is causing the “disconection”.
If I open “Midi Ports” the TD-27 becomes quiet, when I close the page"Midi Ports" nothing happens, the TD-27 is still quiet. Midi reset dosnt work, repluging the midi cable dosend help. It just works again if I shut down GP completely and start it again.
The related link to download the gig file is attached
The TD-27 offeres a USB-A connection for sending the Midi data. This is connected to a Anker, active, USB-HuB. This HUB is connected to a USB 3.0 connection at the NoteBook.
It works fine (and it worked fine for years with GP3, without issues), until I open “Midi Ports” in GP.
The software “USBDeview” is very simmilar to DevCon, as i understand. The device is still “green” and active. No status is changed, but GP is not reacting anymore after opening and closing “Midi Ports”.
I do not understand what the solution should be?
Deinstall the driver and reinstall? I made already several times.
as I wrote before the Midi from the TD27 is not recognized from GP anymore after opening the „Midi Port“ Window (and closed it) if a second instance is open.
After closing the second instance, and the midi reset in the main instance the TD27 is back!?
Ok, but I use the TD27 just in the first instance, in the second and third instance the TD27 is not checked in the midi settings.
The second instance is just for mics and has connection to my NanoControl, the third is for the E-Guitar, just controlled by a midi food switch.
All three have to react on my Keyboard (Roland RD2000). Could it be a midi through setting of the Keyboard?
I am on Win10, the laptop is just and only there to run GP and is completely stripped down for Audio (and works well, with a lot of load, as the whole band is running through GP).
The „problem“ is not a „show stopper“, but I would like to minimize the chance of an interruption during a Gig…
So, if I understood correctly, TD27 works great in the first instance and if you open the MIDI Ports options in the second instance, the MIDI connection is lost in the first instance?
The root cause is definitely the (single-client) driver (I immediately suspected on your driver) so when the second instance queries for available MIDI devices, the first instance loses the connection.
I’m not sure if this behavior is the same for all single-client MIDI drivers, but if it is, perhaps devs can do something about it (e.g. implement a button that manually lists available MIDI ports, don’t know, just thinking out loud).
Yes, it is like this.
Why is the midi connection “shut down” in the first (main) instance if I open the „Midi Port“
Window? That is the reason why another instance is grapping the connection, for no reason, because I did not tell another instance to connect…
I tried today again with loopMidi and Midi- Ox and other Midi helpers, no success…
If I open in the main instance the “Midi Control”
and a second instance is running, the incoming midi signal will be not used (in the main instance), after leaving the “Midi Control” anymore.
The midi in lit is shining green, just in the main instance, but is not in use anymore.
For me it is an GP bug…