Why we cannot change audio device name

[mrbarefoot1013]

Per Vincent's suggestion, I'm posting my email question here with his subject suggestion.

Semi-bug fix suggestion

VB-Audio Cables + Voicemeeter don't allow Windows>Settings>Sound
Devices>Playback/Recording>Properties>name change without causing start
up errors + failed I/O. And changing other devices names caused failed I/O.

It would be super helpful to be able to rename VB + other devices without issue. I have 25+ devices listed and organizing all helpful, especially when Voicemeeter multiplies this list by x2 or x3 for driver types when selecting. Is there a way to reference each device by it's unchanging name or id instead of by user changeable name? Can you explain if this is a Windows limitation i.e. Windows doesn't store/require unique unchangable device names or IDs? Thanks for considering.

[Vincent Burel]

with windows 10 and its automatic update came the bug related to audio driver re-installation:
https://forum.vb-audio.com/viewtopic.php?f=6&t=442

Since audio device pin name can be merged with different already installed driver after win10 or win 11 update, we consider the audio driver pin name change or icon change as a possible collateral effect of a bad driver re-installation by Windows Update procedure.

Also changing Pin Name and Icon of our virtual audio device could bring confusion on customer service. So we decided to hardcode the pin name and icon inside the driver itself (in VB-CABLE C+D and Voicemeeter VAIOs) and reset them on windows startup.

Then our virtual audio cable pin name and icon became an indicator to detect Win10 / 11 bad driver installation process:
https://forum.vb-audio.com/viewtopic.php?f=7&t=688

[mrbarefoot1013]

Thanks for your reply, Vincent. It sounds like you are dealing with a Microsoft issue/bug and encouraging folks to create a critical mass for MS to fix it. But given that was 5 years ago (and sounds like really 24 years ago), it sounds like they aren't likely to address it (which sounds like them). I've always thought the audio device naming situation was unreliable/weird but never knew why. Thanks.

Even though I'm an audio engineer and a software developer i.e. I feel like I'm somewhat good at stuff like setting I up Voicemeeter, I found several aspects of implementing VB-Audio products confusing. It took awhile of trial and error to understand what was happening (especially with ASIO hardware out functionality but that's for a different post). For me, a lot of that was the naming, especially with Voicemeeter devices. What do you think of this pin naming suggestion:

Company - Input/Output - Product - Subproduct

VB-Audio - Input - Virtual Cable - A
VB-Audio - Input - Virtual Cable - B
VB-Audio - Input - Virtual Cable - C
VB-Audio - Input - Virtual Cable - D
VB-Audio - Input - Virtual Cable - Hi-Fi
VB-Audio - Input - Virtual Cable - Standard OR Similar (previous blank)
VB-Audio - Input - VoiceMeeter - VAIO A OR 1 (previous blank)
VB-Audio - Input - VoiceMeeter - VAIO B OR 2 (previous AUX VAIO)
VB-Audio - Input - VoiceMeeter - VAIO C OR 3 (previous VAIO3)

VB-Audio - Output - Virtual Cable - A
VB-Audio - Output - Virtual Cable - B
VB-Audio - Output - Virtual Cable - C
VB-Audio - Output - Virtual Cable - D
VB-Audio - Output - Virtual Cable - Hi-Fi
VB-Audio - Output - Virtual Cable - Standard OR Similar (previous blank)
VB-Audio - Output - VoiceMeeter - VAIO A OR 1 (previous blank)
VB-Audio - Output - VoiceMeeter - VAIO B OR 2 (previous AUX VAIO)
VB-Audio - Output - VoiceMeeter - VAIO C OR 3 (previous VAIO3)

Obviously names could be shortened. Ex. VBA - In - vCable - A
Also .ico files could display the Company + I/O indicator + Product indicator + subproduct indicator

I'm curious why you would/wouldn't implement this. And if backwards pin name compatibility is an issue, if building in a dual check of legacy AND new pin names is possible.