VUMeter Plugin

[hiccup]

- New option "Use Skin Defaults". When checked this will apply any settings in the ini file listed under the [DEFAULT] section.

Thanks for fulfilling this request.
I think it's a massive improvement and benefit for end-users not needing to make any setting adjustments anymore for skins that come with such an ini file.

About using integers for the bg:
Wouldn't it be more obvious and simpler to use the more standard and common hex code for this?
Also, is there a reason for the alpha value also being used? Isn't RGB enough?
This seems to work well also?:
https://www.checkyourmath.com/convert/color/rgb_decimal.php

[BoringName]

Wouldn't it be more obvious and simpler to use the more standard and common hex code for this?
Also, is there a reason for the alpha value also being used? Isn't RGB enough?

Are they? Only time I've dealt with hex codes for colours is website design. Anywhere else is integers or straight RGB arrays like {120, 140, 255}

Sorry I'm not going to change it to hex codes. For what it's worth, the MusicBee API returns the same integer codes when I query the element colours.

As for the alpha channel, technically it doesn't need to be included for the INI value, it's just a result of me using the color.FromArgb/Color.ToArgb commands consistently through the code.

I'm not going to change it. Considering you can just set the colour within VUMeter and click "Save Defaults" to get the code I don't think it's that much of a hassle. The MusicBee skin XML files use RGB values so it's pretty easy to just punch those into the colour picker.

[hiccup]

Are they? Only time I've dealt with hex codes for colours is website design. Anywhere else is integers or straight RGB arrays like {120, 140, 255}

It certainly is for people that use tools such as Photoshop or Paint.NET.
And for those that create things like skins or VU meter skins for MusicBee.
I don't think image editors like these even support integer values for colours?

And from a human standpoint RGB is obviously the best choice to use or edit, since simply looking at its numbers will give you a good clue about both the colouring and the brightness of what it will produce.
But I do understand what you have decided on from a coder's perspective.

And end-users won't care about this stuff at all, as long as the 'Save Defaults' function simply works.
And for VU meter skin creators, using some website (or in my case Excel) to convert an RGB value to this integer format is not terribly complicated.
But it most certainly isn't intuitive with these weird numbers and (useless) negative values. (for alpha blends)

[hiccup]

I don't know how he made the *.vu files.  I think I'll just leave all of this to the experts for now!!

Being my usual honest and blunt 'me':
Considering your interest and dedication to all this stuff, why not just learn how to use the tools to create VU meter skins yourself?
I'm sure you are capable of that, and it will be both easier and more rewarding compared to trying to bend backwards in trying to extract and modify existing material?

[sveakul]

I don't know how he made the *.vu files.  I think I'll just leave all of this to the experts for now!!

Being my usual honest and blunt 'me':
Considering your interest and dedication to all this stuff, why not just learn how to use the tools to create VU meter skins yourself?
I'm sure you are capable of that, and it will be both easier and more rewarding compared to trying to bend backwards in trying to extract and modify existing material?

The only tool I have/am aware of is VUEditor.exe.  While I have the translated-to-English instructions from the developer,  frankly I find them a bit too "heavy-going" for me.  You start losing your edge after age 70, as well as allowable time.  I'm going to do a re-read of BoringName's new mods of his 2.2.1 plugin and I'll be lucky if I come out of that in one piece, haha..  The rest I'll have to leave to the developers/coders/designers like you and him.  I belong in the "enthusiastic user" department.

[hiccup]

The only tool I have/am aware of is VUEditor.exe.  While I have the translated-to-English instructions from the developer,  frankly I find them a bit too "heavy-going" for me.

You have also frequently referred to a tool to create LVU VU meter skins. (which is what made me think you intended to use for creating and sharing your own VU meter creations)
 Ah well, thanks for providing a better insight in your position and objectives. That should be helpful regarding any possible further discussions on his matter.

In case it is interesting to anyone trying to get a better understanding of things involved regarding VU meters and using VueEditor:
Here is a link to the website of a Japanese guy named Takechan (タケチャンの) that describes his adventures all the way from buying an actual VU meter to creating a digital replica of it using VUEditor.
Great stuff, and the time and effort he put into this should be appreciated.
https://takeabose.livedoor.blog/archives/6442931.html

[BoringName]

Here is a video that shows how to setup a meter with just a needle. It's very straight forward - VU Editor

Where the red lines intersect is the pivot point for the  needle.

To setup an LED you do a similar thing.
From the fourth menu option, select  Load Lamps and select a lamp image.
From the fifth menu option, select Lights
From the 6th menu option, select Remove All if any ticks are already present.
When you move the slider left and right you will see the Lamp image transparency changes.

Lets say you want the lamp to be 50% transparent at +1 decibels. Move the slider until the Lamp Light value at the bottom reads 0.50. Then select the 6th menu option and click on the +1 value. The same way the user does in the video when setting the needle angles. If you want it at 100% at +2, drag the slider all the way to the right so the Lamp Light value reads 1.0, select the 6th menu option and click on +2

edit: for multiple lamps you need to add the lamp images one after the other in the order you want them to appear. The Lamp Light maximum value will increase by 1.0 for every lamp added. So for 2 lamps the slider will go from 0.0 to 2.0. At 1.0 the first lamp will be opaque and the second transparent, at 1.5 the first lamp will be opaque and the second lamp will be at 50% transparency.

[hiccup]

Changes
- New option "Use Skin Defaults". When checked this will apply any settings in the ini file listed under the [DEFAULT] section. An example of the available settings -
[DEFAULT]
isVertical=true
bgColour=-16711936
rise=0.03
fall=0.03
curveAdj=5
singleMeter=false
peakLED=false

There is a typo when the plugin creates an .ini:
curevAdj instead of curveAdj

[BoringName]

There is a typo when the plugin creates an .ini:
curevAdj instead of curveAdj

Fixed - VUMeter2.2.2.zip

[sveakul]

@BoringName :  is it possible to be able to add a modificaton to the mbVUMeter.Settings.xml file to specify a custom folder location for skins?  As this can be done in the oops foo_vis_vumeter's advanced prefs, it would be great to use a shared skins folder for both, seeing as they both accomodate the same meter types.

[phred]

@Boring Name...

I would find it helpful if you'd add one more menu item: About. Which would show the currently installed version number. Thanks.

In addition, I just downloaded all of hiccup's revised/updated skins and now -no- .rar skins are showing in the dropdown. And MB is throwing an error when I enable or disable "Use Skin Defaults." All the previous versions (.zip) show in the dropdown as expected. Please see this detailed report on hiccup's thread: https://getmusicbee.com/forum/index.php?topic=41696.msg229673#msg229673

[hiccup]

In addition, I just downloaded all of hiccup's revised/updated skins and now -no- .rar skins are showing in the dropdown.

See here: https://getmusicbee.com/forum/index.php?topic=41696.msg229676#msg229676

 .rar skins don't exist, only .zip (AIMP format) and .bin (foobar2000) skins.
So you need to extract the downloaded .rar files to get the actual .bin skin file.

@Boring Name...
I would find it helpful if you'd add one more menu item: About. Which would show the currently installed version number. Thanks.

Speaking for myself, I would be against adding this to the settings menu.
The release version of a plugin can already be checked using MusicBee's Plugins Configuration panel:

[phred]

See here: https://getmusicbee.com/forum/index.php?topic=41696.msg229676#msg229676
 .rar skins don't exist, only .zip (AIMP format) and .bin (foobar2000) skins.
So you need to extract the downloaded .rar files to get the actual .bin skin file.

Great. Thank you. I replied in detail on the referenced thread. Apparently my three week absence resulted in my not carefully reading the changes that had been made while I was away.

@Boring Name...
I would find it helpful if you'd add one more menu item: About. Which would show the currently installed version number. Thanks.

Speaking for myself, I would be against adding this to the settings menu.
The release version of a plugin can already be checked using MusicBee's Plugins Configuration panel:
[/quote]
Yes, so it does. I'm in the habit of right-clicking > help > about and had forgotten about this. Thanks for jarring my memory.

[BoringName]

And MB is throwing an error when I enable or disable "Use Skin Defaults."

I can reproduce this when no skin is loaded and "Use Skin Defaults" is clicked.

Is that the only time this occurs for you, when no skin is loaded?

[phred]

Is that the only time this occurs for you, when no skin is loaded?

Well now that I have the skins properly loading (thanks to hiccup) I have not seen the error appear. Not when enabling "Use Skin Defaults" nor when disabling it.