Windows Midi device naming shenanigans

So far, really enjoying my first day with the Arp.

However, I've a bit of a weird issue. I am using Arp with an NDLR, both with USB MIDI to my DAW (and from the DAW to both devices for sync and instructions.) I am not using pass-thru at this point.

However, the Midi device names keep getting mixed up between the NDLR and the Arp. The changes are sporadic but always happen when rebooting or reopening the DAW. For example, at first, I had Midicake Arp and Arp 2 named midi, then it switched to NDLR (replacing the original NDRL midi) and created an NDLR #2 device.

Note: I am not talking about the MIDI channels - they are all good. It is the names given to the actual midi devices.

There is a well-known bug in Windows 11 (and earlier) related to how USB assigns midi instrument names, detailed here:

https://medium.com/@stickgrinder/how-to-solve-the-infamous-windows-10-midi-device-renaming-issue-9aa793fa9f0a

I have spent a lot of time clearing out all my previous sets and then replugging all my kit. Also, checking the registry. However, the issue continues. I did a complete nuke of all USB devices in registry and when I rebooted, the problem continued this time the four NDLR midi devices being named Midicake Arp #2 to #5 (but uncertain which of these if which of the four NDLR devices.)

I could live with the incorrect naming, but the problem is that midi devices do not seem to the consistently applied the midi device names. So I am constantly having to go through each device one at a time and find our which device name it is attached to.

I have two theories: the first is that perhaps I need to put the NDLR and the Arp on completely separate USB busses within my PC hardware. I can't test that on my current rig.

The second is that both the Arp and the NDLR are using Teesy boards. Windows *may* be getting confused as a result of some difficulty with Windows identifying the difference between two.

I am not sure if you have seen a similar situation before or if you have a workaround.

Looking forward to a response. Take your time and feel free to ask for more info.

4 comments

Comments (4)

Chris Brown

Jul 20, 2024

Hi,

The cause of the issue is because both ARP and NDLR use a Teensy micro controller. Each device has a name file but on windows, the first name file detected is used for all devices.

I do not currently know of a fix for this but it is some time since I last looked into it and it is still on the active todo list.

I will look into it again over the next couple of days and will let you know if I can find a solution.

submo

Replying to

Is it because the Hardware ID's (PID & VID) are matching in the usb descriptors? ....... Just curious

Edited

jsweeney

Jul 21, 2024

Thanks for the prompt feedback. Yes! I suspected that may be the issue. I looked at developing my own 'dream' midi controller during COVID, and saw that this could be an issue.

Currently, the situation is workable(ish) but the device names do jump around between sessions. Bitwig does reasonable job of solving the problem with how it handles controller patches. Separating each track of the NDLR & Midicake Arp helps to find what's what quickly. S o other than a 2-4 minute check up and repatch for each session, it's not a show stopper.

However, there are a lot of other synt/sequencer projects that use the Teensy, so a more perminent solution would be nice. This would be much messier if I had another teensy based device in my kit.

BTW recorded my first weird track with the NDLR/Arp combo today. "Anime Techno 01 - Noodling In other world with my Level 1 Arp supercheat power I dance with the Demoness"

Yeah. I have a friend who's gotten me into absolute trash Isakai. Soooo... why not go all in.