Matthew, and others at Microsoft
As typical case, we have a nice thread on our forum that could help you to
see the problem we are talking about:
https://forum.vb-audio.com/viewtopic.php?f=6
<https://forum.vb-audio.com/viewtopic.php?f=6&t=886> &t=886
where it is explained that audio can suddenly stop working after a Win10
update.
- Audio Driver can be badly reinstalled requiring to re-install
them again
- Windows Audio settings can be changed (default audio device,
device format, volume mixer
).
- Privacy Settings regarding Microphone can also be changed (this
was the case for this problem report)
That you have to understand is that from a day to another, a working audio
configuration is turned into a hell for users.
And for us, because we get messages/report every day on this problem
Regards
Vincent Burel
www.voicemeeter.com
De : wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] De la part de Matthew van Eerde
(Redacted sender "Matthew.van.Eerde" for DMARC)
Envoyé : vendredi 20 septembre 2019 19:42
À : wdmaudiodev@xxxxxxxxxxxxx
Objet : [wdmaudiodev] Re: The link between Audio Properties and the Driver
Endpoint.
Sorry, Im not seeing it.
_____
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on
behalf of Vincent Burel (VB-Audio) <vincent.burel@xxxxxxxxxxxx>
Sent: Friday, September 20, 2019 10:38:31 AM
To: wdmaudiodev@xxxxxxxxxxxxx <wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Re: The link between Audio Properties and the Driver
Endpoint.
This is a single problem, but several symptoms
that should place you on the track to fix it
De : wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] De la part de Matthew van Eerde
(Redacted sender "Matthew.van.Eerde" for DMARC)
Envoyé : vendredi 20 septembre 2019 17:32
À : wdmaudiodev@xxxxxxxxxxxxx
Objet : [wdmaudiodev] Re: The link between Audio Properties and the Driver
Endpoint.
One problem at a time please.
_____
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on
behalf of Vincent Burel (VB-Audio) <vincent.burel@xxxxxxxxxxxx>
Sent: Thursday, September 19, 2019 10:57:30 PM
To: wdmaudiodev@xxxxxxxxxxxxx <wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Re: The link between Audio Properties and the Driver
Endpoint.
Matthew, no kidding!
Maybe you dont remember, but you already read or reply to several messages
on the subject:
10 AUG 2015: WIN10 update changes drivers name and icon
23 JUL 2019: SYSVAD & Certification Process Failures...
(several message explaining how all different driver installation procedures
are not working correct with SYSVAD)
13 OCT 2018: Re: virtual audio driver removed via devcon, but it's only
hidden
19 JAN 2019: Re: Is there a way to force clearing device property cache on
device uninstallation?
After installation the driver presents pin name of another driver (already
installed, or previously de-installed).
You will find in these messages some points from Gary Daniels explaining
that there is different potential bugs with AudioEndpointBuilder and PNP
Migration process and that also the driver must be fixed to work for OS
upgrades
so you cant ignore the problem.
14 MAR 2019: Re: DTM audio glitch test failing
It seems the driver installation (update) procedure is bugged and the
driver behavior can be impacted (if bad installed mess in audio points -
).
As you see, If you really wanted to help, it would be fixed since years.
Regards
Vincent Burel
De : wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] De la part de Matthew van Eerde
(Redacted sender "Matthew.van.Eerde" for DMARC)
Envoyé : jeudi 19 septembre 2019 18:42
À : wdmaudiodev@xxxxxxxxxxxxx
Objet : [wdmaudiodev] Re: The link between Audio Properties and the Driver
Endpoint.
* I definitely think that the problem is mainly located in the driver
installation process and the Audio Endpoint Point initial installation /
configuration
Tell me more. What leads you to that conclusion?
* Just make a google search
I want to help YOU. What problems are YOU running into?
_____
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on
behalf of Vincent Burel (VB-Audio) <vincent.burel@xxxxxxxxxxxx>
Sent: Thursday, September 19, 2019 9:37:49 AM
To: wdmaudiodev@xxxxxxxxxxxxx <wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Re: The link between Audio Properties and the Driver
Endpoint.
I definitely think that the problem is mainly located in the driver
installation process and the Audio End Point initial installation /
configuration.
If you are interested in this, just make a google search on WIN10 update
and audio issues for example
you will find something every day!
Regards
Vincent Burel
De : wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] De la part de Matthew van Eerde
(Redacted sender "Matthew.van.Eerde" for DMARC)
Envoyé : jeudi 19 septembre 2019 17:30
À : wdmaudiodev@xxxxxxxxxxxxx
Objet : [wdmaudiodev] Re: The link between Audio Properties and the Driver
Endpoint.
* typically stuttering / discontinued audio / cut in the sound on a
capture or render stream
This has nothing to do with Daves question, but Im interested anyway.
Out of respect for Dave, please start a new email thread with a new subject.
Follow the instructions here to grab logs of the problem in action:
https://matthewvaneerde.wordpress.com/2016/09/26/report-problems-with-logs-a
nd-suggest-features-with-the-feedback-hub/
<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmatthewva
neerde.wordpress.com%2F2016%2F09%2F26%2Freport-problems-with-logs-and-sugges
t-features-with-the-feedback-hub%2F&data=02%7C01%7CMatthew.van.Eerde%40micro
soft.com%7C4f836ccf71ec458b87f708d73df16d9c%7C72f988bf86f141af91ab2d7cd011db
47%7C1%7C0%7C637045979457144157&sdata=YwXUBqaPCd5IJCd8QqtfSBTpiZM%2BAzK%2B2w
qZ60K%2BYTo%3D&reserved=0>
Grab a link to the problem report and include it in the email.
Ill take a look at the logs and see if I can figure out what is causing the
stuttering / discontinued audio / cut in the sound.
_____
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on
behalf of Vincent Burel (VB-Audio) <vincent.burel@xxxxxxxxxxxx>
Sent: Thursday, September 19, 2019 7:00:01 AM
To: wdmaudiodev@xxxxxxxxxxxxx <wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Re: The link between Audio Properties and the Driver
Endpoint.
Yes, precise, but complicated, and does not help us to sale and support
audio app at the end.
Today with WIN10 ( 2019):
for each update or for each new USB audio device plugged, or for each new
audio driver installation,
there is a risk for the user to get a problem somewhere in the audio stack
typically stuttering / discontinued audio / cut in the sound on a capture or
render stream.
Example: I newly plug a USB microphone on a WIN10 computer, and then try to
use it with WASAPI or MME
no way to get stable stream.
then I newly plug it into another WIN10 computer, use in the same way
without any problem
Other example: I newly plug a USB device (e.g. SoundBlaster), it works ok
during the day
the day after: no way to make it work stable after computer
startup
then I reboot and it work again correct
Audio users are simply becoming crazy with this kind of behavior
.
Then I ask for questions: Is there a way to know if the audio stack is
running correct ? Is there a way to check that audio driver installation is
correct ? Could we have such kind diagnostic tool ?
Regards
Vincent Burel