As per some feedback and suggestions , please find the JSP3 "AIMP Analog VU Meter" update attached, version named "1.0.1 QM 05-11-24" for convenient reference.

@ilovefb2k

...
How do you get the base images and needle for a VU meter? Is there a tool to rip them from an existing VUmeter BIN file?

Quote from: Defender on 2024-11-05 12:18:29

...
How do you get the base images and needle for a VU meter? Is there a tool to rip them from an existing VUmeter BIN file?

You can go to the AIMP forum and use the ZIP-Files containing the AIMP VU-Meters, in these Zip's you'll find the pics.

Quote from: ilovefb2k on 2024-11-05 11:20:50

As per some feedback and suggestions , please find the JSP3 "AIMP Analog VU Meter" update attached, version named "1.0.1 QM 05-11-24" for convenient reference.

@ilovefb2k

Thx.

Can you add an option to the right click menu for Background color? Option No fill or Transparent. Which effectively disables the painting of the background which is being done in line 503 and 504.

Can you add an option to the right click menu to set the margins (properties HA.METER.Left Margin and HA.METER.Top margin)?

The original VUmeter stretches to fill the window/panel it lives in. Your script fills from top/left until it reaches bottom/right margin but keeps aspect ratio. Would it be possible to add an option so your script stretches too?

How do you get the base images and needle for a VU meter? Is there a tool to rip them from an existing VUmeter BIN file?

sorry for being off topic but is it possible to get a sound level in the taskbar like in the picture

I have those in BIN format. The VU Editor (that creates the BIN files for foo_vis_vumeter) can not open/read its own BIN files. It opens VU project files. When you are done you can export a project to a BIN file which uses either No Compression, BZIP2 or LZMA.

Does anyone have a bright idea to extract the files from a VU meter BIN file?

1. add an option to the right click menu for Background color : Done. please find the script attached and 2 screenshots illustrated thereafter.

2.  properties HA.METER.Left Margin and HA.METER.Top margin adjustment: As you have already pointed out.  /SHIFT + right click/ on the panel to  bring the context menu up front, which should have item allowing us to access window properties. These properties should be there. 

3. Would it be possible to add an option so your script stretches [skin] too : Yes, in principal.
we may try the following pseudo_script,  which is whithin on_paint() callback to refresh per internal timer.  The point is that we create an instance\image of the VU Meter every internal timer,  then it is too fast to rapidly consume CPU-power and Memory, which , consequently,  may cause computer to memory leak and crash.
as such, my approach is to leave it aside till we can have better solution.      

4- base images and needle for a VU meter :  the script is solely based on AIMP VU Meter skins, which are compressed by standard method. In principal, we may let javascript to un-zip that files or utilize 3rd command-line tools to do it. I well noted this suggestion.
however, follow some of your later posts, it seems you want the script to play around with fb2k's VU Meter skin, which are zipped by its or component's method. so far, i have had no idea to give it a try cause i do not have any clue about that format and, therefore, the script has no feature to deal with fb2k VU Meter skins. 
however, based on @oops's comments during developing vu_vis_meter, i do think that that BIN should have at least a background, cover and a sheet list of data that help component to paint the needle. but, that is a guess.

@Defender



I set it to (30-30-30) to match the dark mode.
It's originally a color for DarkOne, right?
The needle vibration is also nice.
I also use 7inch_3.bin with foo_vis_vumeter.
I like that it's simple and easy to see.
Thank you.

@telboy1812
Reply #1867 By ilovefb2k: https://hydrogenaud.io/index.php/topic,110516.msg1053272.html#msg1053272
or
foo_vis_vumeter
https://hydrogenaud.io/index.php/topic,126733.0.html

Quote from: Defender on 2024-11-05 15:50:30

I have those in BIN format. The VU Editor (that creates the BIN files for foo_vis_vumeter) can not open/read its own BIN files. It opens VU project files. When you are done you can export a project to a BIN file which uses either No Compression, BZIP2 or LZMA.

Does anyone have a bright idea to extract the files from a VU meter BIN file?

I'll second that.  Could someone please make a tool that can both export the image components from a BIN file, and re-import them into the same BIN, overwriting the originals?  Then a user could make say a color change to a meter body using an image editor and then re-save the BIN with that change.  With VUEditor you can only do this by starting with "*.vu project files," not the BIN file.

how do you install the vu meter

@ilovefb2k : I loaded your newly posted 1.011 script completely as-is with just the skin folder path mod, and the meter movements are MUCH more reactive and seem more accurate.  Thanks for clarifying the "check setting" prompts!  What I have been doing when I load a new skin is do the "check setting" procedure, and keep the "tweak min/max level" option checked--I am assuming that the latter is performing an additional refinement to using the "check setting" buttons--is that correct?

I did not add the portion of script to 1.01 you posted a day earlier in response to my concerns about needle movement, as I am guessing those changes are addressed in the new 1.011 QM 05-11-24 version.

peak_rms =  Math.sqrt(sum/frame_len);
//instantly react: RMS_levels[c] = peak_rms;					
// or: gently
if (peak_rms > RMS_levels[c]) RMS_levels[c] = peak_rms;
else RMS_levels[c] *= rms_decay_speed;

Quote from: ilovefb2k on 2024-11-05 17:43:59

1. add an option to the right click menu for Background color : Done. please find the script attached and 2 screenshots illustrated thereafter.

2.  properties HA.METER.Left Margin and HA.METER.Top margin adjustment: As you have already pointed out.  /SHIFT + right click/ on the panel to  bring the context menu up front, which should have item allowing us to access window properties. These properties should be there. 

3. Would it be possible to add an option so your script stretches [skin] too : Yes, in principal.
we may try the following pseudo_script,  which is whithin on_paint() callback to refresh per internal timer.  The point is that we create an instance\image of the VU Meter every internal timer,  then it is too fast to rapidly consume CPU-power and Memory, which , consequently,  may cause computer to memory leak and crash.
as such, my approach is to leave it aside till we can have better solution.      

4- base images and needle for a VU meter :  the script is solely based on AIMP VU Meter skins, which are compressed by standard method. In principal, we may let javascript to un-zip that files or utilize 3rd command-line tools to do it. I well noted this suggestion.
however, follow some of your later posts, it seems you want the script to play around with fb2k's VU Meter skin, which are zipped by its or component's method. so far, i have had no idea to give it a try cause i do not have any clue about that format and, therefore, the script has no feature to deal with fb2k VU Meter skins. 
however, based on @oops's comments during developing vu_vis_meter, i do think that that BIN should have at least a background, cover and a sheet list of data that help component to paint the needle. but, that is a guess.

Ad 1) Works. Thx. The reason I like to have it in the rightclickmenu and as a property is when you release a new version I do not have to outcomment the background paintcode everytime.

Ad 2) I noticed that sometimes the properties reset themselves loading different skins or changing rightclick options.
Another thing is that it is a bit inconsistent to only set left and top margins. If you set a top and left option I would expect these margins to be also applied to the right and bottom which they are not. So please add separate padding options for right and for bottom or apply the setting for left also to right and the setting for top also to bottom.

Ad 3) Ok. I will look into  it later.

Ad 4) The idea I have is to extract the images from a BIN file, create an appropiate skin.ini and use your script to display the results.

As a proof of concept I have been experimenting with recreating stuff from a BIN file. If you rightclick on a running foo_vis_vumeter BIN skin you can see the native resolution. Then I define a panel in my  skin with this exact size in which I run the BIN. Make a screenshot when not playing anything and make a screenshot at full level with replaygain off. Merge the two screenshots to get rid off the needle. Which leaves you with the base png of the particular skin.
Then paint the needle (I use lunapic) in a separate png. Very hard to determine the correct length needed for the needle.
Then experiment with changing values in a skin.ini until it more or less resembles the behavior of the original BIN.

I find it is very difficult to determine settings for PivotPointX and PivotPointY. Also changing settings for MobilityNegative and
MobilityPositive do not change behavior as far as I can see.

All in all very timeconsuming.

It would help a lot if the values of PivotPointX and PivotPointY could be calculated automatically. If you have those values it is far more easy to determine the needed length for the needle.

I attached the results of my experiment including the AIMP skin I created and the original BIN file.
The lower large VU meter is the BIN file running. The upper large VU meter is run by your script. The left part runs with the original needle of Line Magnetic 501 and the right part runs with my recreated needle.
Both are running in their native resolution.

2 -1: sometimes the properties reset themselves :  I did utilize window.Reload(option), where option = false. this should not trigger any properties reset to default. i will check it over the weekend.
2-2: add separate padding options for right and for bottom :  Done. please find the script attached. There may be likely bugs cause i am in a rush.
4- It is fantastic that you can play around with that. I humbly raise an idea to calculate x0,y0 as per image attached. It should be easy for you to catch up.