Adjusting the Teensy MIDI device name

[vjmuzik]

I feel like I might have one more idea on why this could be happening, in the current usbMIDI implementation none of the midi ports have their own names so it relies on Windows to come up with one on its own. So what could be happening is it sees they have the same PID so it just picks one of them to generate a name from for both devices. And now that I mention it I do remember that I gave my ports they’re own names back when I first programmed 3 Teensy 3.6s that are on a Windows 7 machine. I’m pretty sure they don’t have any issues last time I checked, but it’s definitely something else to look into, if anyone wants a place to start with this here’s the thread from 2 years ago: https://forum.pjrc.com/threads/50043...IDI-Port-Names I haven’t messed with it since then so it probably would need to be updated.

[MatrixRat]

Interestingly, regarding the usb host port of the MIO-10 and it's ability to handle multiple identical class compliant usbMidi devices. In one setup I had several Teensy (3.2 - 4.0) usbMidi devices plugged in via a hub. All worked until I added a T2 usbMidi and to fix it, was not just a matter of unplugging the T2 and restarting the system. The hub needs to be unplugged, then you delete everything in the MIO-10's config, reboot then start over.

Further digging, in another iteration, had several off-the -shelf UsbMidi class compliant devices plugged into the MIO-10's host and added a (don't recall which)Teensy usbMidi to the mix which de-railed it. Have yet to dig deeper into that rabbithole and set up some test scenarios and take screenshots etc. to cover all the various permutations.

Have other work so will be a little while...

[woodslanding]

Well, I tried vjmuzik's idea of naming the ports, and fingers crossed, it seems to work! My host doesn't display those names, but the fact that they are unique seems to cause windows to get the interface names right....

Thanks!!

[eddevane]

hi, I've tried the suggestions listed in the documentation and the product ID definition, tried deleting devices in Windows Device Manager (Win 10) but the two devices I have keep being renamed in Ableton Live to whichever one was last plugged in. I have one called "footswitch" and one called "solenoid", but they appear as "footswitch#2" and footswitch#3" if footswitch was last plugged in. Each have unique name, manufacturer and serial number ids specified in the name.c file.

This is really confusing for my particular application, which is a live music set up that I want to be able to boot up and run at the flick of a power switch, using a tablet to remotely control a NUC PC. As the 3 devices I am using all use the same name, but do completely different things, they get mixed up in Live which is tricky to fix. Having unique names would be ideal as then I'd know if the correct device was assigned to the correct track in Live.

Any ideas?

[eddevane]

right so I did what others have suggested in previous posts as an intermediate work around: set up 3 different controllers one as MIDI, one as Serial + MIDI, and the other as Serial+MIDI+Audio. Each come up with their unique names which solves my problem, for now, unless I decide to add another Teensy based device to the mix...

[Theremingenieur]

At long term, I suggest trashing Win10 and move over to a Mac.

[woodslanding]

At long term, I suggest trashing Win10 and move over to a Mac.

Unless you use a touchscreen like I do. No Mac for me....

[MatrixRat]

@eddevane, how about using a T4.0 with a hub hooked to it's usb host port allowing Windoze to see your individual devices as a single multi-cable device?