PDA

View Full Version : Help with VolumeOSD.



Doof
October 13th, 2002, 01:55 PM
I'm trying to get VolumeOSD set up on my system (using Girder ver. 3.2.4), and I'm having a couple of problems that all stem, I'm sure, from my ignorance of some of these more advanced plugins & Girder capabilities.

The problems I'm having are:

1. When I change the volume, either up or down, the volume gets muted somehow. I'm thinking this has something to do with the Check Mute State command that gets executed? I've pointed the Volume +/- and Mute Toggle commands to my soundcard, but I don't know what I'm supposed to do exactly with some of the other commands, like Check Mute State and Read Volume. I tried to point those to my soundcard as well, but the same thing happens.

2. The Volume Bar shows up, but none of the progress bar graphics ever fill in.

3. Do I have to run the Volume Change.gml file through the 3.1->3.2 converter?

Doof
October 13th, 2002, 01:55 PM
Well, I'm making some progress here. I now have the bitmaps filled in, but they're not moving as the volume changes. And it always says that it's muted, even though it's not.

I think I'm just confused on two points. How do you get Girder to check the status of mute? And how do you get Girder to check the value of the Volume? I think that's where my trouble lies.

Monster
October 13th, 2002, 01:55 PM
Sorry for long silence, I was away.
Ok, I'll try to help at this point:

1. How do you get Girder to check the status of mute?

Action: Volume change
Step size: 0
Volume ID: something like Volume->Mastercontrols->Mute
Register checkbox checked

This should put 0 or 1 in reg25 depending on mute status

2. And how do you get Girder to check the value of the Volume?

Action: Volume change
Step size: 0
Volume ID: something like Volume->Mastercontrols->Master volume
Register checkbox checked

This should put value of master volume in reg25

Aeroschmelz
October 13th, 2002, 01:55 PM
I had to change the following points to get it working:

1.) Adapt the path in Girder at points:
Mute, show OSD
Not Muted, show OSD

2.) Adapt the path again in the two ini Files
VolOSD_muted.ini
VolOSD_volume.ini

3.) Control and Change the Device Settings (SB Audigy has other Device Numbers than the exitsting ones)

4.) At point Mute state -> reg24

I changed the entry in reg24=reg25 without the space between the equal sign

After that it worked really nice...

Doof
October 27th, 2002, 09:47 PM
Well, I finally got around to trying your suggestions and now everything is working great! Thanks! :)