[wdmaudiodev] Re: msvad volume reset to 100

  • From: "Matthew van Eerde" <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "Matthew.van.Eerde" for DMARC)
  • To: "wdmaudiodev@xxxxxxxxxxxxx" <wdmaudiodev@xxxxxxxxxxxxx>
  • Date: Tue, 5 Feb 2019 19:24:47 +0000

So this one?
https://www.microsoft.com/en-us/download/details.aspx?id=42273

Whether the driver implements KSPROPERTY_AUDIO_VOLUMELEVEL or not, my 
understanding is that the audiosrv service is supposed to persist the volume 
setting and apply it after every restart.

There is an .inf entry to opt out of this, but MSVAD doesn’t use it.
https://docs.microsoft.com/en-us/windows-hardware/drivers/audio/opting-out-of-volume-level-persistence

So it would seem you have found a bug.


________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> on 
behalf of Robert Dalton <bob@xxxxxxxxxxxx>
Sent: Tuesday, February 5, 2019 11:07:53 AM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: msvad volume reset to 100

I'm using the pcmex example project from the Win8.1 MSVAD sample, and the 
KSPROPERTY_AUDIO_VOLUMELEVEL is referenced in:

toptable.h
basetopo.cpp


On Tue, Feb 5, 2019 at 2:02 AM Matthew van Eerde 
<dmarc-noreply@xxxxxxxxxxxxx<mailto:dmarc-noreply@xxxxxxxxxxxxx>> wrote:
Which particular unmodified version of MSVAD are you using?

Does it implement KSPROPERTY_AUDIO_VOLUMELEVEL?

________________________________
From: wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx
<wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>> on 
behalf of Robert Dalton <bob@xxxxxxxxxxxx<mailto:bob@xxxxxxxxxxxx>>
Sent: Monday, February 4, 2019 8:00:26 PM
To: wdmaudiodev@xxxxxxxxxxxxx<mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] msvad volume reset to 100

Hello,

I'm using an unmodified version of the MSVAD for testing on Win7/8.1 machines.  
Everything builds and installs fine, but I'm noticing that the volume is always 
reset to 100 when the machine is restarted.  I can't seem to find any logic 
that would be resetting this value, or is it more of an issue that the actual 
volume is never persisted anywhere?  Anyone ever seen this issue or know where 
to look?

Thanks.

Bob






--
Robert Dalton Jr.
Co-founder / CTO at Dysonics
dysonics.com<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.dysonics.com&data=02%7C01%7CMatthew.van.Eerde%40microsoft.com%7C059d512fc6b049bbe9bc08d68b9d568f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636849905234604708&sdata=fRkrrybO%2F%2BYG%2BRUGvqjkJoSLwhzdFJPa7GTbz6%2FnkYk%3D&reserved=0>
c: 415-786-0265

Other related posts: