[wdmaudiodev] Re: Setting KSPROPERTY_AUDIO_VOLUMELEVEL
- From: Neetu Sand <neetu.freelist@xxxxxxxxx>
- To: wdmaudiodev@xxxxxxxxxxxxx
- Date: Sat, 25 Jun 2011 09:31:02 +0530
Hi Matthew,
Yes, this is what I am trying to do - expose a volume property with a range
between -96dB to 0 dB. Do you think I should expose some other values for
the range?
When I expose property handle for volume control, I implement it with Get,
Set and BasicSupport. I get calls for all three of them - In Set I cache the
value, in get I return the cached value and in BasicSupport I return the
range that I am trying to expose.
However this results in no changes to volume i.e. slider moves but no
audible changes in the volume level. This is puzzling so please tell me what
is wrong in my implementation.
cheers,
Neetu
On Fri, Jun 24, 2011 at 11:07 PM, Matthew van Eerde <
Matthew.van.Eerde@xxxxxxxxxxxxx> wrote:
> If the device does not expose volume properties, Windows will step in and
> add a -192 dB to X dB software volume control, which defaults to a high
> gain; this causes clipping.
>
> A workaround is to expose a volume property with a very narrow range that
> does not actually impact the signal.
>
> -----Original Message-----
> From: wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:
> wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Tim Roberts
> Sent: Friday, June 24, 2011 10:31 AM
> To: wdmaudiodev@xxxxxxxxxxxxx
> Subject: [wdmaudiodev] Re: Setting KSPROPERTY_AUDIO_VOLUMELEVEL
>
> Neetu Sand wrote:
> >
> > Our driver is based on wavecyclic miniport. It exposes a speaker and
> > MIC. We are seeing that on Windows 7, MIC volume has a 30dB gain with
> > a volume slider range -192 dB to 30 dB. Our device does not have a
> > volume knob but we want to change the volume slider range to -192 dB
> > to 0 dB or at least be able to set volume to 3dB for MIC. That way we
> > can get rid of extra gain. That's why I have implemented topology
> > filter and implemented property handler.
>
> If your device does not have adjustable volume, then you should not be
> exposing any volume properties at all, and there should not be a volume
> control in the control panel.
>
> --
> Tim Roberts, timr@xxxxxxxxx
> Providenza & Boekelheide, Inc.
>
> ******************
>
> WDMAUDIODEV addresses:
> Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
> Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
> Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
> Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
>
> URL to WDMAUDIODEV page:
> http://www.wdmaudiodev.com/
>
>
> ******************
>
> WDMAUDIODEV addresses:
> Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
> Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
> Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
> Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
>
> URL to WDMAUDIODEV page:
> http://www.wdmaudiodev.com/
>
>
Other related posts:
