Volume control step size

[Ron]

CapnMatt,

I was really hoping that M$ would have made stuff compatible that was the whole idea and now these kinds of tricks.. pfff.

As an addition to BSchuler suggestion you should apply the mute to the "volume channel" not the mute channel. This is one for the tricks page i guess!

<font size=-1>[ This Message was edited by: RonB on 2001-05-28 09:34 ]</font>

[Ron]

Sure use "check reg" action.


Choose Register
put into the "icon/device" box: > 10
Assign the command to execute on "true"


<font size=-1>[ This Message was edited by: RonB on 2001-05-28 20:29 ]</font>

[CapnMatt]

The volume control on my sound driver is VERY dramatic for the first 10% and drops off heavily after that. After about 50% of the way up it stops making much difference at all.

I was wondering if there could be a way of using a logrithmic step size for the volume control, so that the steps start out very small and work up larger.

-Matt

[BSchuler]

Second question I answered this way tonight....

Use a registry key. Say the first one is RegA. Use a multicommand for the volumes. Inside both Volume Up and Down multicommands, add these commands:
a command to increase or decrease Reg A by 1
a command if RegA>10 then Goto VOLUMEUPSTEP10
a command if RegA= or <10 then Goto VOLUMEUPSTEP1

Use 2 commands, VOUMEUPSTEP10 and 1, to actually do the volume change. If you want more varance, just do more of the above.

If you have a question about the commands needed...just ask.

Remember to have mute set reg a=0. Also, until you mute the first time, this won't work right. Because the reg will start out a 0 regardless of where your volume began. But Girder can't export the volume level....not that I know of atleast....You could solve this by having girder run a Mute on startup to ensure you both (Girder and Windows) starts up matched right at volume 0.

[JOHN]

How can i make the if RegA>10 then Goto?

[JOHN]

Ok, Thanks Ron!