--4.0.3-2.0.0
- Removed hard limit of five presets - they can now be added and deleted at will.
- Added mouse-wheel support to the LDB icon for master volume control.
- Clicking a preset will now hide the preset menu.
- Volume sliders now operate on a 5% basis, down from 10%.
- Added sound output dropdown menu, for switching between different output devices (such as headphones to speakers or the inverse of.)

-- 3.1.3-1.1.4
* The control panel will now automatically show when mousing over the LDB icon.
* Clicking the LDB icon will now mute/unmute all sound.
* The panel, when opened via the slash command, can now be dragged. Position is not saved between open/close. I basically did it for the hell of it.

-- 3.1.1-1.1.3

* Added a tooltip-style view when used in conjunction with an LDB display AddOn - The Blizzard-style view will now only show when using the slashcmds "/vol" or "/volumizer".

-- 3.1.1-1.1.2

* Added a toggle for "Pet Sounds".
* Changed the tooltip for the LDB plugin to use a localized string rather than English only.
* Changed LDB dataobject's type to "data source" from "launcher" since it does indeed display data.

-- 3.1.0-1.1.1

* Changed the title box to be more in line with the default Blizzard UI.
* Fixed a bug where naming a preset "Default" would make it disappear from the list.

-- 3.1.0-1.1.0

* Updated TOC for WoW 3.1.
* Revamped panel look-n-feel to more closely resemble the default UI.
* Added the ability to define and name five different volume presets.
* Changed LDB icon behavior to reflect whether or not the master volume was toggled.

-- 3.0.9-1.0.6

* The control panel will no longer close when the mouse pointer leaves it.
* Pressing the "ESC" key, clicking on the WorldFrame, clicking on the LDB icon, or using the SlashCmd while the panel is open will close it.
* Added tooltips for all checkboxes.

-- 3.0.9-1.0.5

* Added text field to LDB object to display the current Master volume level.
* Added current volume levels next to the slider names in the control panel - made the label font smaller to fit this in.
* Added "/vol" slash command to bring up the control panel.
* Minor bugfix and load-time optimizations.

Not sure what this needs, other than a TOC bump. Adding the Dialog button, perhaps. I've tried adding presets but Apparently I'm doing something wrong, because changes I make don't get propagated, it seems, from session to session. I've been assuming it was because my game was crashing when I swapped to other toons (which Blizz has been trying to fix, apparently).

The addon is missing Dialogues volume bar that is present in WoW sound options.
Also adding option to toggle Headphone mode would be awesome I keep switching from speakers to headphones in the evenings and night and have to go through menu and options to adjust it for better audio experience.

This addon is causing far too many errors, always during combat and always the errors are about Volumizer trying to call a protected function!

In August 2011 the author, Torhal, stated:

Almost 2 YEARS have gone past since then and apparently nothing's been done to fix it, does that mean it's just never going to be fixed? Is Volumizer really at fault here or is there something else at fault? I'm also wondering if Torhal is still working on this?

Edited for clarification.

Hey, now - watch the entitlement!

Seriously, though - there hasn't been anything really to be done with the code save for minor stylistic changes to what I do now as opposed to my style five years ago. The protected function stuff is Blizzard's taint system going haywire.

I'm not touching anything to do with CompactRaidFrames or anything else that's combat sensitive. What I am doing is using the default UI's DropDownMenu system which randomly taints the default UI code - something Blizzard has been needing to fix for years and which got really bad around Cataclysm and even worse with MoP.

I've tested several times; changing preset values (which triggers the usage of the DropDownMenu stuff) then go into combat, all without issue. If I can't reproduce it, I can't fix it. There also aren't any viable DropDownMenu replacements, and I haven't looked into writing one myself. (Either way, the code for that would likely be larger than Volumizer itself.)

At any rate, I've updated the AddOn for the 5.3 patch.

Firstly, apologies for the "entitlement", that certainly wasn't my intent.

Thank you for confirming my suspicions, that it's not actually the addon itself that is causing the errors but simply a fault of Blizzard's taint system itself. It's a shame that Volumizer gets the blame but I guess Blizzard don't want their system to be blaming itself so they prefer to put the blame on other addons!

I suppose we just have to live with this for now, at least until (or even if) Blizzard decide to actually fix their own coding.

This addon is causing far too many errors, always during combat and always the errors are about Volumizer trying to call a protected function!

In August 2011 the author, Torhal, stated:

Almost 2 YEARS have gone past since then and apparently nothing's been done to fix it, does that mean it's just never going to be fixed? Is Volumizer really at fault here or is there something else at fault? I'm also wondering if Torhal is still working on this?

Edited for clarification.

Hey, now - watch the entitlement!

Seriously, though - there hasn't been anything really to be done with the code save for minor stylistic changes to what I do now as opposed to my style five years ago. The protected function stuff is Blizzard's taint system going haywire.

I'm not touching anything to do with CompactRaidFrames or anything else that's combat sensitive. What I am doing is using the default UI's DropDownMenu system which randomly taints the default UI code - something Blizzard has been needing to fix for years and which got really bad around Cataclysm and even worse with MoP.

I've tested several times; changing preset values (which triggers the usage of the DropDownMenu stuff) then go into combat, all without issue. If I can't reproduce it, I can't fix it. There also aren't any viable DropDownMenu replacements, and I haven't looked into writing one myself. (Either way, the code for that would likely be larger than Volumizer itself.)

This addon is causing far too many errors, always during combat and always the errors are about Volumizer trying to call a protected function!

In August 2011 the author, Torhal, stated:

Unfortunately Blizzard has made the UIDropDown frames more prevalent in areas of code that are secured or protected, so AddOn taint is more of an issue. I'll look at mitigating some of this and, failing that, look for a different DropDown solution for presets.

Almost 2 YEARS have gone past since then and apparently nothing's been done to fix it, does that mean it's just never going to be fixed? Is Volumizer really at fault here or is there something else at fault? I'm also wondering if Torhal is still working on this?

Just wanted to report the following bug I've been getting. Mostly it seems to occur while in combat, but it happen at other times as well. It's interesting because when it does happen, I'm not messing with Volumizer at all. It's been going of a bit, but I keep forgetting to report it. Thanks.

this error comes in fights with massive npc, players in sights - like battlegrounds or 25 man raids. I don't know if it is a Volumizer Error, what has Volumizer to do with compactUnitFrame.lua?

Unfortunately Blizzard has made the UIDropDown frames more prevalent in areas of code that are secured or protected, so AddOn taint is more of an issue. I'll look at mitigating some of this and, failing that, look for a different DropDown solution for presets.

Support AddOn Development!

You have just downloaded by the author . If you like this AddOn why not consider supporting the author? This author has set up a donation account. Donations ensure that authors can continue to develop useful tools for everyone.