[wdmaudiodev] AW: Re: AW: Re: AW: Re: virtual audio driver removed via devcon, but it's only hidden
- From: "Johannes Freyberger" <jfreyberger@xxxxxxxxxxxxxxxxxxxx>
- To: <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Thu, 18 Oct 2018 23:03:30 +0200
OK, I'll try to file a feature request.
But this doesn't sound very promising that there's a chance to find the
reason why devcon remove sometimes includes the audio inputs and outputs and
sometimes it doesn't?
Von: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> Im
Auftrag von Matthew van Eerde (Redacted sender "Matthew.van.Eerde" for
DMARC)
Gesendet: Donnerstag, 18. Oktober 2018 22:35
An: wdmaudiodev@xxxxxxxxxxxxx
Betreff: [wdmaudiodev] Re: AW: Re: AW: Re: virtual audio driver removed via
devcon, but it's only hidden
But then it would go out over the speakers too.
What we really need is a way for a third-party application to register
itself as an audio endpoint. Johannes, if you could file a feature
suggestion in Feedback Hub, I would appreciate it. There's some precedent
for this in the way that certain Windows features work - Remote Desktop,
Play To Miracast/Xbox, etc.
From: ambrish dantrey <mailto:a4ambrish@xxxxxxxxx>
Sent: Thursday, October 18, 2018 1:22 PM
To: wdmaudiodev@xxxxxxxxxxxxx <mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Re: AW: Re: AW: Re: virtual audio driver removed via
devcon, but it's only hidden
Just curious, why can't you use WASAPI loopback capture API to capture audio
data in user-mode and send it on RTP channel? It might be an easier solution
rather than going through VAD.
On Fri, Oct 19, 2018 at 1:35 AM Johannes Freyberger
<jfreyberger@xxxxxxxxxxxxxxxxxxxx <mailto:jfreyberger@xxxxxxxxxxxxxxxxxxxx>
wrote:
Yes, there's no hardware included. The audio is passed to my application and
then it's sent to a RTP stream.
Von: wdmaudiodev-bounce@xxxxxxxxxxxxx
<
mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx> <wdmaudiodev-bounce@xxxxxxxxxxxxx
<
mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx> > Im Auftrag von Matthew van Eerde
(Redacted sender "Matthew.van.Eerde" for DMARC)
Gesendet: Donnerstag, 18. Oktober 2018 21:59
An: wdmaudiodev@xxxxxxxxxxxxx <
mailto:wdmaudiodev@xxxxxxxxxxxxx>
Betreff: [wdmaudiodev] Re: AW: Re: virtual audio driver removed via devcon,
but it's only hidden
Does your audio driver need to be pure virtual? What does it do with audio
that Windows hands to it?
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
<
mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx> <wdmaudiodev-bounce@xxxxxxxxxxxxx
<
mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx> > on behalf of Johannes Freyberger
<jfreyberger@xxxxxxxxxxxxxxxxxxxx <
mailto:jfreyberger@xxxxxxxxxxxxxxxxxxxx>
Sent: Wednesday, October 17, 2018 6:10:59 AM
To: wdmaudiodev@xxxxxxxxxxxxx <
mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] AW: Re: virtual audio driver removed via devcon, but
it's only hidden
I tried pnputil to install the driver and I don't get any error on my cmd or
in setupapi.dev.log but my audio device is not visible. So I think I can use
pnputil only for updating drivers but not for a new installation of a pure
virtual audio driver?
When using devcon for install/uninstall I've seen on the customers machine
that in device manager the device is removed in "Sound, video and game
controllers" but the corresponding inputs and outputs in "Audio inputs and
outputs" just turn into the hidden state. Here on my machine the audio
inputs and outputs are also gone. Both machines are W10 1803/64 Bits.
Looking at my setupapi.dev.log the devcon uninstall looks like this:
[Delete Device - ROOT\MEDIA\0000]
Section start 2018/10/17 13:49:24.734
cmd: devcon.exe remove *R3LAYWDMDriver
dvi: Query-and-Remove succeeded
<<< Section end 2018/10/17 13:49:24.840
<<< [Exit status: SUCCESS]
[Delete Device -
SWD\MMDEVAPI\{0.0.0.00000000}.{6247CE0D-5C9E-41B1-BBA2-1688857CD843}]
Section start 2018/10/17 13:49:24.996
cmd: C:\WINDOWS\System32\svchost.exe -k LocalSystemNetworkRestricted
-p
<<< Section end 2018/10/17 13:49:25.012
<<< [Exit status: SUCCESS]
[Delete Device -
SWD\MMDEVAPI\{0.0.1.00000000}.{3E58B06F-7A2E-4669-9E5E-DAAD442046C7}]
Section start 2018/10/17 13:49:25.090
cmd: C:\WINDOWS\System32\svchost.exe -k LocalSystemNetworkRestricted
-p
<<< Section end 2018/10/17 13:49:25.105
<<< [Exit status: SUCCESS]
In the customers setupapi.dev.log I can only see:
[Delete Device - ROOT\MEDIA\0000]
Section start 2018/10/17 14:41:16.391
cmd: devcon.exe remove *R3LAYWDMDriver
dvi: Query-and-Remove succeeded
<<< Section end 2018/10/17 14:41:16.462
<<< [Exit status: SUCCESS]
So it seems the two subsequent Delete Device from my log are missing in the
customers logfile and probably they are related to audio inputs and outputs.
As I'm only invoking the devcon remove command, the next two seem to be
generated inside the OS on my system but not on the customers system. What
could be the reason for this?
Thanks and best regards,
Johannes Freyberger
Von: wdmaudiodev-bounce@xxxxxxxxxxxxx
<
mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx> <wdmaudiodev-bounce@xxxxxxxxxxxxx
<
mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx> > Im Auftrag von Tim Roberts
Gesendet: Samstag, 13. Oktober 2018 08:48
An: wdmaudiodev@xxxxxxxxxxxxx <
mailto:wdmaudiodev@xxxxxxxxxxxxx>
Betreff: [wdmaudiodev] Re: virtual audio driver removed via devcon, but it's
only hidden
On Oct 12, 2018, at 11:37 PM, Johannes Freyberger
<jfreyberger@xxxxxxxxxxxxxxxxxxxx <
mailto:jfreyberger@xxxxxxxxxxxxxxxxxxxx>
wrote:
when I'm uninstalling my pure virtual audio driver on some W10, 1803
machines via devcon remove the driver the driver doesn't seem to be
uninstalled completely as it is still visible as hidden device in the device
manager even after a reboot. But in setupapi.dev.log the corresponding entry
says:
...
On some other machines the drivers are completely gone and not in hidden
state.
Could this "hidden driver" effect be due to user privileges or some Antivir
software installed on these machines?
No. What this probably means is that the driver was not installed
correctly. How, exactly, do you install your device? "Devcon install" is
the right approach for systems up through Windows 8, but in Windows 10 it
can result in the creation of TWO devices. "pnputil" seems to be the right
way these days.
-
Tim Roberts, timr@xxxxxxxxx <
mailto:timr@xxxxxxxxx>
Providenza & Boekelheide, Inc.
Other related posts: