-
Notifications
You must be signed in to change notification settings - Fork 34
[NAME_BUG]: Names of the MIDI cable 'Swissonic MidiConnect 2' not correctly reported #589
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
When you ran MIDI-OX was it on the same PC, or a different PC? It's a 32 bit app. Is "MIDIIN2 (USB MIDI cable)" really the name you want/expect to see for the second port on each of those? This is the first device I've seen where that branch of code gets run. It really does complicate naming. |
I've ordered one of these from Thomann (it doesn't seem to be available within the US). I'll see what it produces on my other laptop |
MIDI-OX was executed on Windows 11 Pro, 24H2 as a basic 32-bit app not using Windows MIDI Services
Please see my remark to #522 because it is closely related. For a general discussion let's us #522
Thomann does not sell in US but such this is a typical USB MIDI cable where there are thousends out there. Some require drivers, some don't. |
Thomann ships to the US. I've purchased plenty from them in the past. The dozen or so other USB MIDI cables I have do not report the same names, even with our in-box driver. How the names are reported is very much up to what the device has in the USB Descriptors, and they are unfortunately, wildly inconsistent. The rest of the conversation is on 522. |
I received this from Thomann today. One thing is does differently vs many other similar units is it dynamically assigns each of the two physical connectors as input or output based on what it is attached to. So 4 ports, but 2 physical connectors. I'll add this device to the testing. |
I have this working now for all the MIDI 1.0 devices I've been able to test. Once I have it working correctly for MIDI 2.0 devices, I'll release another preview you can use to test. And for devices which name themselves using their filter instead: Note that because this code is written to be compatible with WinMM, it also shares the same bugs. For example, there are two different ContinuuMini devices attached, but only one name is shown, consistent with WinMM when the legacy WinMM naming option (the default) is chosen. The old WinMM/KS code assumes that for any given VID/PID there will be only one name. It doesn't account for devices which have unique names with things like serial numbers in them. |
Windows Version
Canary 27802.rs_prerelease.250222-1646 and Windows 11 Pro Version 24H2 OS build 26100.3194
Service Installation Method
GitHub
Location
Application using Windows MIDI Services SDK (MIDI 2.0)
Device Make and Model
Swissonic MidiConnect 2 cable
Name(s) you saw
4 * USB MIDI cable
Name(s) you expected
USB MIDI cable and MIDIIN2 (USB MIDI cable)/MIDIOUT2 (USB MIDI cable)
MIDI KS Info Output
MIDI endpoint properties
Additional notes
The MIDI cable is this. Notice: no special driver required
MIDI-OX (uses WinMM) shows this
The text was updated successfully, but these errors were encountered: