[wdmaudiodev] Re: KSPROPERTY_STEPPING_LONG problem!
- From: Rémi Coquet <remi.coquet@xxxxxxx>
- To: <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Mon, 29 Mar 2010 19:37:23 +0100
eric wrote:
>
> Thank you for your quick response. Actually, I have tried
> many different settings of Values and KSPROPERTY_STEPPING_LONG
> but there is no any difference. Here is on of the settings I tried,
> the upperest value of volume control is 0x31, but the lowest value
> strangely become -0x2147483648 (signed value 0x80000000).
------> -1 /+1 0 -> off 1-> Max phase -1-> Max /phase
From: Tim Roberts
Sent: Monday, March 29, 2010 6:32 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: KSPROPERTY_STEPPING_LONG problem!
eric wrote:
>
> Thank you for your quick response. Actually, I have tried
> many different settings of Values and KSPROPERTY_STEPPING_LONG
> but there is no any difference. Here is on of the settings I tried,
> the upperest value of volume control is 0x31, but the lowest value
> strangely become -0x2147483648 (signed value 0x80000000).
Where do you see 0x80000000? Do you handle "mute" as well? I have seen
cases where turning on "mute" results in a volume setting of 0x80000000.
(You have an interesting way of putting things. 0x80000000 would
actually be the UNSIGNED value; the signed value is -2147483648, which
is decimal, not hex.)
> const
> KSPROPERTY_STEPPING_LONG VolumeRangeAndStep [] =
> {
> {
> 1, // SteppingDelta
> 0, // Reserved
> {
> 0x0, // Minimum
> 0x31 // Maximum
> }
> }
> };
Is that really supposed to be 0x31, meaning decimal 49?
--
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/
Other related posts:
