[pcm]

A OSX Volume Indicator.

You can download it here: http://avedesk.philc.ca/modules/PDdownload...f1d827475c2d261

The desklet will also bind HOTKEY to the Mute/Volume up/Volume Down if you have a multimedia keyboard. Somecases you don't even need the hot key and you can just comment the entire section in the XML file.

Make sure to also download the latest version of AveScripter 1.0.5.5. I has a few fixs done.

[Zxian]

DOOD!!! You said a couple of days!

Oh well... it's pretty awesome... Thanks for this.

[Autumnmist]

Hey cool! I can get rid of 3r-1c. Simple but so effective for emulation.

[shmengie]

wicked cool. thx!

[Zxian]

Just in case anyone was interested in seeing this thing in action, I made a video of it in Camtasia.

OSX Volume Indicator in action

I changed the fade-out times a little, so it's faster to fade out on my machine, but otherwise all the work goes to pcm (which is pretty much everything - editing pre-made stuff is easy).

Thank you thank you thank you thank you thank you thank you thank you.

[strija]

Very nice, I'll definetly use this
Thanx!!!

[lid]

Finally a volume indicator that seems to have it all. Detects global volume changes regardless of method inc. mute and doesn't interfere when changing global volume ingame via keyboard (big problem with the standalone solutions). Fantastic work pcm.

One thing, just wondering because the fade out isn't 100% smooth on my system. I'm thinking it's more down to my nVidia card +- Avedesk rather than anything else.

Second thing, the minimum change in volume is detected (the widget appears) but does not show any change in filled bars. It's probably due to the change in volume required to fill each bar but it would be great if the first bar filled at any volume level greater than 0. At the moment there could be sound but no bars.

[pcm]

Ya.. it requires abit of change in the volume to see the difference.

I could replace the ticks with a progress bar that will always show some indications.

Take me a couple of mins if you want?

Smooth is controlled a couple of "sleeps" and alpha. you can alter it in the script.

*********

I just updated the OSX version to 1.01.. If you right click on the volume when it appears, you can choose bar or ticks.

For smooth issues, I would recommend you just open script file and look for HideDesklet procedure. Its very very simple.

[Zxian]

Like I said in my post above, I edited the sleeps to 50 (ms - right?) instead of 100. It seems to fade out a lot smoother now. Another option is to fill in steps inbetween what pcm originally had with intermediate values and set the sleeps between each step to 50. That way the total fading will be more gradual, but the total fade time will stay the same.

[pcm]

I'm sure there is better ways to adjust the fade. I took the easy and "cheap" way that looked perfect on my pc. People can always submit to me their changes, I'll try them all

Or you can always do modifications and upload new desklets to the site

Also I didn't spend too much time on this desklet. Took a couple of hours to stick it up together once I had the plugin done and the artwork from KoL.

And I'm trying to work on Animator module in avescripter to make things better for animation of stuff and easier :S.

[Zxian]

I think that you've probably got the easiest and simplest way to change the fade here. The only question is how many stages do you want for each, and how much time inbetween. Otherwise, you've given us the framework to tweak to our heart's content.

Man... I can't get enough of this thing... I just keep changing the volume just to see it pop up and then fade out...

[_cell]

This is gonna be the release of the month Wonderful solution for volume indicator problem

[lid]

Neat little update PCM the bar seems to do the trick, now even the smallest change from 0 is visible.

Also, thanks Zxian, as suggested I changed the value to 50 and indeed the fade is a little quicker and far smoother now.

[Sranshaft]

Noticed a small bug in the coding that could cause it not to center properly (which is why I noticed it in the first place)

Where you have: SetXYPos( ((MonObj.WorkWidth / 2) - (DeskletWidth / 2)),((MonObj.WorkHeight / 2) - (DeskletHeight - 50)) ) ;

It should be: SetXYPos( ((MonObj.WorkWidth / 2) - (DeskletWidth / 2)),((MonObj.WorkHeight / 2) - (DeskletHeight / 2)) ) ;


Nothing major but it makes a world of difference. Other than that, excellent little eye candy I can now finally ditch the on-screen volume that installs itself with the Microsoft wireless keyboard and for that this little puppy is worth its weight in pixels.

[AndreasV]

Quality release

[pcm]

Well I based the position to where it appears on my OSX computer. Its not in the center of the screen but in the center bottom of the screen. Which is why I did it -50 from the bottom.

But the center of the screen is good too. Since its easy to modify, everyone can change it to how they like it

Thanks for the feedback

[Zxian]

There's a slight bug that only appears if you press the volume up/down buttons while the fading has begun. It seems as though the second fade just goes straight to alpha = 0. I've been playing a bit with the script to try to remove this, but I'll have to wait until later to fix and post it.

And yes, 50px from the bottom is better than centered.

[pcm]

I've just updated the scripter again. Sorry for the 2 updates in one day. But after talking with Andreas, he recommended me a couple of things and I added an extra one that will be very useful. On of which is DeskletFadeIn/Out which could replace the "cheap" animation currently done.

DeskletFadout(false,500) seems ok on my system. I haven't update it yet.. but just letting people who hack around try it out first.

Which also fixes the bug you have ZXian

Let me know before I make it an update

Thanks all

[Zxian]

If it's an improvement, then great. I say go for it.

[Sranshaft]

"pcm" said:

Well I based the position to where it appears on my OSX computer. Its not in the center of the screen but in the center bottom of the screen. Which is why I did it -50 from the bottom.

I had always been under the assumption that the indicator was in the center of the screen. Guess it's true what they say about assuming...

Trying the new version now Thanks!