Please file your own issue and describe the symptoms you are experiencing,
which are different from those in the previous filed issues you link to.
________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on
behalf of Vincent Burel (VB-Audio) <vincent.burel@xxxxxxxxxxxx>
Sent: Tuesday, July 31, 2018 7:02:54 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: SYSVAD & Certification Process Failures...
This is already done ! since more than 2 years !
https://github.com/Microsoft/Windows-driver-samples/issues/57<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FWindows-driver-samples%2Fissues%2F57&data=02%7C01%7Cmatthew.van.eerde%40microsoft.com%7Cb9b4375bf6eb46759be208d5f6ee6aca%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636686426250540232&sdata=uUyGtZW4d4ajdnmqyNNhgCHbHq%2BYVnBE3Ao6xFa8Cr4%3D&reserved=0>
https://github.com/Microsoft/Windows-driver-samples/issues/46<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FWindows-driver-samples%2Fissues%2F46&data=02%7C01%7Cmatthew.van.eerde%40microsoft.com%7Cb9b4375bf6eb46759be208d5f6ee6aca%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636686426250540232&sdata=q6F06ofrcJne6ypaTgrp2L4iZ2yRMvLmfOau%2FvR2kog%3D&reserved=0>
How many issues must be sent ? and how many time Microsoft needs to fix this
issue ? Who is in charge of this project ?
So, does that mean you confirm there is no way to install SYSVAD on WIN10
certification machine ?
Or you can admit we can use “Add Legacy Hardware” from the Device Manager ?
VB
De : wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] ;
De la part de Matthew van Eerde (Redacted sender "Matthew.van.Eerde" for DMARC)
Envoyé : mardi 31 juillet 2018 15:38
À : wdmaudiodev@xxxxxxxxxxxxx
Objet : [wdmaudiodev] Re: SYSVAD & Certification Process Failures...
If the instructions on GitHub to install SysVad don’t work, please file an
issue on GitHub.
________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
<wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>> on
behalf of Vincent Burel (VB-Audio)
<vincent.burel@xxxxxxxxxxxx<mailto:vincent.burel@xxxxxxxxxxxx>>
Sent: Monday, July 30, 2018 10:16:05 PM
To: wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Re: SYSVAD & Certification Process Failures...
Matthew,
There is no way to install the current SYSVAD manually on Test machine ?
Please, confirm?
VB
De : wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] De la part de Vincent Burel ;(VB-Audio)
Envoyé : lundi 30 juillet 2018 09:18
À : wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Objet : [wdmaudiodev] Re: SYSVAD & Certification Process Failures...
Matthew,
The official way to install SYSVAD manually on test machine (client PC for
certification process) does not work.
Would you please point me a method to install the SYSVAD on WIN10 ?
Regards
Vincent Burel
De : wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] De la part de Vincent Burel ;(VB-Audio)
Envoyé : mercredi 25 juillet 2018 15:11
À : wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Objet : [wdmaudiodev] Re: SYSVAD & Certification Process Failures...
The pointed document does not say that the “add legacy hardware” is obsolete…
While what I reported is based on concrete experience that you can reproduce.
Actually you did not test SYSVAD manual installation process and HLK
certification process since 2 years at least (otherwise you would get the same
problem than me today).
Note: devcon.exe is not installed with WIN10 and needs to be extracted from WDK
(meaning Microsoft provides an O/S without driver installation procedure if the
“Add Legacy Hardware” procedure cannot be used – strange isn’t it ?).
So let’s follow the SYSVAD readme file to install manually SYSVAD audio driver:
1- There is no sysvad.inf file in the current SYSVAD package.
2- c:\tools\devcon install tabletaudiosample.inf
*ROOT\sysvad_TabletAudioSample does not work! The issue is known and always
opened since 2 years:
https://github.com/Microsoft/Windows-driver-samples/issues/57<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2FWindows-driver-samples%2Fissues%2F57&data=02%7C01%7Cmatthew.van.eerde%40microsoft.com%7Cb9b4375bf6eb46759be208d5f6ee6aca%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636686426250540232&sdata=uUyGtZW4d4ajdnmqyNNhgCHbHq%2BYVnBE3Ao6xFa8Cr4%3D&reserved=0>
3- pnputil -i -a tabletaudiosample.inf does not work too …
then we re-installed again SYSVAD by the Device Manager procedure “add legacy
hardware” and this time this process did not install 2x audio drivers but only
one …
We run HLK Studio to perform again our wrong test:
the following test are still failing:
- Audio Codec – KS Position Test
- Audio Codec – MFCaptureEngine API Test – Capture AMR-NB audio to a
file from the default capture pin
- Audio Codec – MFCaptureEngine API Test – Capture PCM audio samples
from the default capture pin
- Audio Codec – MFCaptureEngine API Test – Capture PCM audio to a wav
file from the default capture pin
But the following test are now successful:
- Audio Codec – AC3 Test – Certification – Desktop
- Audio Codec – Audio Logo Test – Glitch – Desktop
- Audio Codec – Class Driver Audio Logo Test – Certification – Desktop
“AC3 Test” & “Class Driver Audio Logo Test” seem to become successful on a
second pass after having done all other tests…
But “Audio Logo Test – Glitch” could pass successfully for another reason…
So the question remains:
How are we expected to produce a certifiable audio driver if the Microsoft
SYSVAD example is not even validated and cannot be certified ?
To everyone: Did someone already test the current SYSVAD audio driver with
latest HLK Studio on latest WIN10 x64 (17134.RS4)
Regards
Vincent Burel
De : wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] De la part de Matthew van Eerde ;
(Redacted sender "Matthew.van.Eerde" for DMARC)
Envoyé : mardi 24 juillet 2018 20:16
À : wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Objet : [wdmaudiodev] Re: SYSVAD & Certification Process Failures...
Ø where is it written on a Microsoft document that the Device Manager provides
obsolete driver installation procedure
Here you go:
https://technet.microsoft.com/en-us/library/ee851685.aspx<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fee851685.aspx&data=02%7C01%7Cmatthew.van.eerde%40microsoft.com%7Cb9b4375bf6eb46759be208d5f6ee6aca%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636686426250540232&sdata=RciD7jTkhnuYhp5YFQgBnoL5J3FArBBmod24Bu8HaB4%3D&reserved=0>
The Windows 7 driver store includes a small collection of drivers for legacy
devices, mostly older printers, modems, scanners, infrared ports, PCMCIA
controllers, and other oddball devices that don’t use Plug and Play
connections. As you might suspect, Windows will not automatically set up such
devices, and you’re rolling the dice if you find one of these old but still
worthwhile devices and try to install an old driver.
SysVad is not a legacy device in this sense.
Also, in Device Manager itself, when you click “add legacy hardware”, the first
page of the wizard says “This wizard helps you install driver software to
support older devices that do not support Plug-and-Play and which are not
automatically recognized by Windows. You should only use this wizard if you are
an advanced user or you have been directed here by technical support”
Ø You have surely read 2 messages from me
OK, so you’re citing
yourself<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.smbc-comics.com%2Fcomic%2F2011-08-07&data=02%7C01%7Cmatthew.van.eerde%40microsoft.com%7Cb9b4375bf6eb46759be208d5f6ee6aca%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636686426250540232&sdata=0Cbk3AKuZveXFe6cQfGo8J9%2BrFjlOpUo9zPvOWaDhMw%3D&reserved=0>;
fair enough. Please read my responses to those email messages you sent and
reply on those threads if appropriate.
________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
<wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>> on
behalf of Vincent Burel (VB-Audio)
<vincent.burel@xxxxxxxxxxxx<mailto:vincent.burel@xxxxxxxxxxxx>>
Sent: Tuesday, July 24, 2018 10:46:25 AM
To: wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Re: SYSVAD & Certification Process Failures...
Yes, citation please !
where is it written on a Microsoft document that the Device Manager provides
obsolete driver installation procedure ?
On my side, you have surely read 2 messages from me on this list:
One to say that SYSVAD WASAPI Exclusive playback mode does not work.
One to say that SYSVAD driver was not passing all HLK Certification test.
(first problem explaining why it cannot be successful for example on
KSPosition Test and Audio Logo Test – Glitch)
So I ask again:
How are we expected to produce a certifiable audio driver if the Microsoft
example cannot be certified ?
Regards
Vincent Burel
De : wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] De la part de Matthew van Eerde ;
(Redacted sender "Matthew.van.Eerde" for DMARC)
Envoyé : mardi 24 juillet 2018 17:04
À : wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Objet : [wdmaudiodev] Re: SYSVAD & Certification Process Failures...
“Add Legacy Hardware” isn’t the right way to install anything anymore, really,
but we have to leave it in because there’s probably something out there that
still uses it, and we don’t want to break it, whatever it is.
Ø the fact that this SYSVAD driver has not been neither validated nor certified
Citation please.
________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
<wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>> on
behalf of Vincent Burel (VB-Audio)
<vincent.burel@xxxxxxxxxxxx<mailto:vincent.burel@xxxxxxxxxxxx>>
Sent: Tuesday, July 24, 2018 6:54:48 AM
To: wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Re: SYSVAD & Certification Process Failures...
I used the main workfow given by Windows O/S,
Why it should not be the right way ?
Next time I will use
c:\tools\devcon install sysvad.inf *ROOT\sysvad_TabletAudioSample
but I don’t think it will change something about the fact that this SYSVAD
driver has not been neither validated nor certified.
VB
De : wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] De la part de Matthew van Eerde ;
(Redacted sender "Matthew.van.Eerde" for DMARC)
Envoyé : mardi 24 juillet 2018 15:26
À : wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Objet : [wdmaudiodev] Re: SYSVAD & Certification Process Failures...
“Add Legacy Hardware” is not the correct way to install Sysvad – see the readme.
________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
<wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>> on
behalf of Vincent Burel (VB-Audio)
<vincent.burel@xxxxxxxxxxxx<mailto:vincent.burel@xxxxxxxxxxxx>>
Sent: Monday, July 23, 2018 11:34:04 PM
To: wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Re: SYSVAD & Certification Process Failures...
I have simply used the windows procedure: Device Manager -> Add Legacy Hardware
So, If I resume :
No one validated the SYSVAD Driver (we saw in previous message that it is
"inefficient by design").
No one installed the SYSVAD driver yet.
No one tested the Certification process on it.
Don’t understand…
Vincent Burel
De : wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] De la part de Tim Roberts
Envoyé : mardi 24 juillet 2018 03:07
À : wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Objet : [wdmaudiodev] Re: SYSVAD & Certification Process Failures...
Vincent Burel (VB-Audio) wrote:
Installation note: Windows Hardware Installation procedure proposes 2 Audio
Tablet Drivers with 2 different versions.
Even if selecting latest version, Windows installs 2x audio tablet drivers (one
is set as non working driver and must be de-installed).
How did you install it? If you used "devcon install", then on Windows 10 you
do get two devices. They changed the non-PnP device installation process in
Windows 10 so that the installation process itself creates a fake device, and
the "devcon" tool creates another one. "pnputil" now seems to be the proper
tool.
--
Tim Roberts, timr@xxxxxxxxx<mailto:timr@xxxxxxxxx>
Providenza & Boekelheide, Inc.
