[wdmaudiodev] Re: WIN10 update changes drivers name and icon + bug in control panel.

  • From: "Jeff Pages" <jeff@xxxxxxxxxxxxxx>
  • To: <wdmaudiodev@xxxxxxxxxxxxx>
  • Date: Mon, 24 Aug 2015 09:27:21 +1000

Other new behavior: the Control Panel / Sound Dialog Box does not always
show the level meter of playback or recording devices if used by WASAPI or
KS interface (in exclusive mode)…



If the audio device doesn’t have a hardware peak meter, an emulated one is
created in software but this only works when the device is shared and so
will disappear when an application opens it in exclusive mode. Starting from
Windows 8, KSPROPERTY_AUDIO_PEAKMETER was replaced by
KSPROPERTY_AUDIO_PEAKMETER2, and hardware peak meters in devices that only
support the old interface will be ignored on those platforms, with emulated
meters used instead.



Jeff





From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Vincent Burel
(VB-Audio)
Sent: Saturday, 22 August 2015 6:19 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] WIN10 update changes drivers name and icon + bug in
control panel.



Hello,



Does someone knows why WIN10 update renamed as default name, some audio
device points ?



Other new behavior: the Control Panel / Sound Dialog Box does not always
show the level meter of playback or recording devices if used by WASAPI or
KS interface (in exclusive mode)…



Regards

Vincent Burel



De : wdmaudiodev-bounce@xxxxxxxxxxxxx
<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] De la part de Vincent Burel
(VB-Audio)
Envoyé : lundi 10 août 2015 17:43
À : wdmaudiodev@xxxxxxxxxxxxx <mailto:wdmaudiodev@xxxxxxxxxxxxx>
Objet : [wdmaudiodev] WIN10 update changes drivers name and icon



Hello,



Just made a WIN10 update from a WIN7 64bits with my different Virtual Audio
Driver installed (VB-Cable / Voicemeeter).



And I got different strange problems :

On first Windows startup (1 or 2 first) the Control Panel / Sound Dialog Box
was not usable (crash when moving the mouse on it).



After that I discovered that VB-Cable’s and Voicemeeter Playback device were
renamed (with default “speaker” name) and the icon was changed in default
speaker icon… but not for recording device… re-installing VB-Cables just
reset the things correctly. But of course changing the name of audio driver
affects the audio configuration of your different application.



Does Anyone knows something about that !?



Regards

Vincent Burel

www.vb-audio.com <http://www.vb-audio.com>

www.mt128.com <http://www.mt128.com>

www.vb-cable.com <http://www.vb-cable.com>

www.voicemeeter.com <http://www.voicemeeter.com>

https://www.facebook.com/vbaudiosoftware

https://plus.google.com/110557338955940627490

https://twitter.com/VB_Audio





Other related posts: