Closed DatanoiseTV closed 1 year ago
@DatanoiseTV do you see the same issue if you try the midi2usbhub project? The same hardware should work, except now you have to use the CLI to route MIDI. It uses the latest MIDI host stack. I was able to use an Arturia Keylab Essential 88 with it; it has 2 virtual cables.
@rppicomidi I didn't check that yet. What are the major differences between the USB MIDI Host implementation? I can give it a go tomorrow (and also send you some debug logs with increased verbosity, if that helps).
@DatanoiseTV The major differences between the USB MIDI Host implementations are
Also, I just pushed up some code I have been testing on my local machine. It handles USB packets received differently. Will you please pull the latest code for this project and test it? This code will route only messages from virtual cable 0 to the UART MIDI Out and it should handle receiving packets from multiple virtual cables that arrive in a single USB transfer.
If you do test the midi2usbhub project, please be aware there is no default routing. You will have to use the CLI to choose which virtual cable will send data to the MIDI UART, and you will have to choose to which virtual cable the MIDI UART will send data.
@DatanoiseTV Did the change I to USB packet handling fix your issue?
@DatanoiseTV Did the change I to USB packet handling fix your issue?
Yes, mostly. Sometimes when replugging devices some issues appear, but seldomly and in a random fashion.
OK Thanks. I will close this issue. If you can describe what happens when replugging in a separate issue, I would appreciate it.
When using a Novation 24SL MKII for example, which presents itself as a 4 virtual cable device, the device will not work and report: