hi @all,
another weekend is coming, friYaY and also another holiday season to come.
please find a script attached, named JSP3 Analog VU Meter, version 1.0.0 DT-N 23-Nov-24 for easy reference.
   - features :
      + load analog/needle AIMP Vu meter (after unziping)
       + load FB2K VU Meter (after extracting by @BoringName 's tool).
      + free allocation in panel
      
   - AIMP VU Meter types covered:
      1 > AIMP VU Meter:
      + analog NEEDLE only (not analog LED) =>  vertical/horizontal needle, up/down needle arrow ,>< V & /\ needle shape.
         * type 1 : 1 image set for both channels
         * type 2 : 2 image sets, each for each channel.
      + LED (LVU) :  vertical/horizontal bar
      - how to :
      + download AIMP Vu Meter skin file e.g.
         * analog NEEDLE : https://www.aimp.ru/forum/index.php?topic=52865.0
         * LED (Led VU) : https://www.aimp.ru/forum/index.php?topic=54005
      + unzip AIMP Vu Meter skin into a folder and copy this [folder] to specific directory as indicated by this script.
      + load this script into a JSP3 /UI/ panel
      2> FB2K VU Meter:
      - step 0: get a FB2k Vu meter skin (e.g. https://audio-file.org/foobar2000-vu-meter-skins-gallery)
      - step 1: extract bin file by employing @BoringName's tool: https://getmusicbee.com/forum/index.php?topic=41692.msg230008#msg230008
            (re-post by @BoringName 's permission https://getmusicbee.com/forum/index.php?topic=41692.msg229964#msg229964)
            we may get 1024 needle image files (needle0000.png, . . . needle1023.png), 1024 LED image files (LED0000.png, . . LED1023.png),
            background.png per channel.
            => 1024 + 1024 + 1 = 2049 files /channel x 2 channels = 4098 files.
            
      - step 2: create a folder named after 'name.bin' (name is fb2k skin name, e.g. 'fisher', 'accuphase', 'sony'...).
      - step 3: if skin has 1 set needle, 1 set LED images : create a sub folder 'VU' for needle images, a subfolder 'VU_LED' for LED images
              if skin has 2 needle sets, 2 LED image set: create a sub folder 'VU_L' for left needle images, a subfolder 'VU_LED_L' for left LED images
              then, 'VU_R' folder for all right needle images, 'VU_LED_R' for all right LED images.
              all these subfolder are right under 'name.bin' folder.
      - step 4: copy/move 'name.bin' folder into specfic folder as indicated in the script,line 140  [fb.ProfilePath + "skins\\viking\\images\\vnav_fb2k\\beat_audio_vu_meter\\"];       
            we can change this path to any other for convinience.
      note: we recognised this folder as FB2k VU Meter skin by its '.bin' characters, so make sure to have this text in the folder name.       
   - limitation:
      + options: MobilityNegative, MobilityPositive > could not take MobilityPositive into account.
      + meter range (in the skin) is quite inaccurate based on fb2k's audio engine.
      + Fb2k's VU Meter skins are currently consumed high RAM memory.
         note: refer to fb2k , @oops's, Analog VU Meter Visualisation/foo_vis_vumeter component [https://www.foobar2000.org/components/view/foo_vis_vumeter]
         for more options    
   - credit and acknowledgment:
      + @marc2003 for rich-feature and powerful, rapid-updated JSP3 component.
      + @Case and @marc2003 for their JSP3 VU Meter.
      + @Artem and contributors /AIMP VU Meter - analog NEEDLE/ for their beautiful analog VU Meters.
      + @xrEngine and contributors /AIMP VU Meter - LED / for their elegant LED VU Meters.
      + @BoringName at https://getmusicbee.com/forum/index.php?topic=41692.msg230008#msg230008 for BinExtractor.exe tool to extract fb2k VU Meter bin skins.
      + @Defender, @sveakul and @Air KEN for nice suggestions and positive feedbacks.
   - special JSP3 features:
      + IJSImage.CreateBitmap() : (3.8.4++) to reduce memory consumed before caching.
      + gr.PopLayer()  : (3.8.5++) set a boundary to be visualied.
      + gr.DrawBitmap() : (3.8.4++) improve rendering image due to  image-converted Bitmap in advance, more efficient CPU-load.

wish you all a very nice weekend and happy holiday season to come.
hope that you all can find this humble script a little bit joyful.
regards,
@ilovefb2k

Quote from: ilovefb2k on 2024-11-22 22:27:07

frankly, how hard we have tried, we could not figure out how these parameter related to each others (INI file of AIMP analog Vu Meter):
MinAngle, MinLevel
ZeroAngle,ZeroLevel
MaxAngle, MaxLevel

MinLevel - The minimum level displayed by the meter in decibels. eg) -40, -20 etc..
MinAngle - The angle of the needle when the peak level is at or below the Minlevel
ZeroLevel - What level should be classed as zero. It's nearly always set to zero. It's a method to offset the meter for AIMP users as AIMP doesn't allow you to adjust the decibel level like Foobar and my plugin in Musicbee do with the mousewheel.
ZeroAngle - The angle of the needle when the peak level is 1.0 (zero decibels).
MaxLevel - The max level displayed on the meter in decibels eg) 5, 10 etc...
MaxAngle - The angle of the needle when the peak level is at or above the MaxLevel.

This is the code I use in C#. The reason it's not just maxAngle - minAngle * peak is some meters use a different scale for each side of zero.

Code: [Select]

if (peak > 1.0)
{
    rotOffset = (zeroAngle - minAngle) + (peak - 1.0f) * (maxAngle - zeroAngle);
} else {
   rotOffset = peak * (zeroAngle - minAngle);
}
rotation = minAngle * Constants.radian + rotOffset * Constants.radian;

Sorry if I added to the dumpster fire. I did warn about the insane amount of image files that method would create......but who am I to judge.

If you want any more info ilovefb2k just send me a PM and I'll see if I can help.

Quote from: BoringName on 2024-11-22 23:08:06

Quote from: ilovefb2k on 2024-11-22 22:27:07

frankly, how hard we have tried, we could not figure out how these parameter related to each others (INI file of AIMP analog Vu Meter):
MinAngle, MinLevel
ZeroAngle,ZeroLevel
MaxAngle, MaxLevel

MinLevel - The minimum level displayed by the meter in decibels. eg) -40, -20 etc..
MinAngle - The angle of the needle when the peak level is at or below the Minlevel
ZeroLevel - What level should be classed as zero. It's nearly always set to zero. It's a method to offset the meter for AIMP users as AIMP doesn't allow you to adjust the decibel level like Foobar and my plugin in Musicbee do with the mousewheel.
ZeroAngle - The angle of the needle when the peak level is 1.0 (zero decibels).
MaxLevel - The max level displayed on the meter in decibels eg) 5, 10 etc...
MaxAngle - The angle of the needle when the peak level is at or above the MaxLevel.

This is the code I use in C#. The reason it's not just maxAngle - minAngle * peak is some meters use a different scale for each side of zero.

Code: [Select]

if (peak > 1.0)
{
    rotOffset = (zeroAngle - minAngle) + (peak - 1.0f) * (maxAngle - zeroAngle);
} else {
   rotOffset = peak * (zeroAngle - minAngle);
}
rotation = minAngle * Constants.radian + rotOffset * Constants.radian;

Sorry if I added to the dumpster fire. I did warn about the insane amount of image files that method would create......but who am I to judge.

If you want any more info ilovefb2k just send me a PM and I'll see if I can help.

hi @BoringName ,
wow, we will have something to chill this weekend.
thank you very very very much for your valuable information and see if we can digest this to not bothering you again.
P/S. @marc2003 just said so, but @marc2003 is kind and nice inside. without recent JSP3 updated, we still struggle with an annoying bug of the JSP3 Analog Vu Meter.

best regards and nice weekend,
@ilovefb2k  

Quote from: ilovefb2k on 2024-11-22 22:54:33

new script

First look ... first findings (and very pleased btw).
I'm running my original AIMP skin based on VU Editor project and did not extract a thing.

Proper transparency support (like it already was).
Music stopped, needle goes to the defined MinLevel in all scalings now. Fixed.
No more needle ghosting outside of glass L_2/R_2, cutoff btw should be one pixel higher.
There's lights/lamps in scaling mode with standard aspect ratio. Lights are not shown in H:Maximize though.

What's the reason that I only see one needle in V/H:Maximize (old issue)?

So it seems all the visuals are in place, just needs some tweaking.
Still missing a much needed mouse scrollwheel though to adjust the needle(s).

I won't be able to test for the upcoming month. Only access to a laptop with probably limited/no internet access and I'll be submerged a lot of the time.

Reply #1814: https://hydrogenaud.io/index.php/topic,110499.msg1054529.html#msg1054529

A reminder that the ilovefb2k JSP3 Script Analog VU Meter requires the installation of a Javascript Panel 3 version not exceeding 3.8.5.  Support for this meter display format was withdrawn by the JSP3 author after that version.  The 3.8.5 version is attached to this post.  At this time, the latest version of the meter script itself is 1.0.23 DT-N 23-Nov-24 and is also attached.  Full support for AIMP analog and AIMP LVU meters is provided.  BIN support is still in an experimental stage, and I recommend sticking with foo_vis_vumeter for BINs.

My friends, for the AIMP meters you need to throw mathematics at the problem. The ad hoc approach is not going to get you good results. In the AIMP forum someone mentioned using the Photoshop ruler to get the angles to draw the meter graduations accurately (Black & AVP & Bim). Use the point-slope formula as this is the math that Photoshop is using for that tool and the answer to your calculation. That will result in perfectly measuring test tones in that and similar properly designed original skins (and most ones based on properly squared pictures of actual meters).

Also, you shouldn't blindly assume and compare against 1.0, use the data in the INI file.

Lastly, why are you using the extraction tool to draw the `.bin` files? Just redraw the background and apply the difference. You will have no memory issues that way as the entire memory footprint of most panels is between 1.5 and 10 MB uncompressed. For general knowledge this difference approach is used extensively in media compression. What DRON implemented is a basic video compression technique to achieve good data compression. You can think of the background as an I-frame and the various needle pictures as P-frames. You only need the deltas vs. the I-frame to draw an entire frame for any given position. So, so, so much nicer to work with these pre-composited frames than the nastiness of the AIMP image juggling/transformation/cropping/rotation/translation/matrices.

Let me know if I can be of any help.

function dbToAngle(db,c){
	var angle= 0;	
	var offset_angle0 	=  	ZeroAngle[c] - MinAngle[c] ; 
	var offset_angle1 	=  	MaxAngle[c] - ZeroAngle[c] ; 
	var offset_angle3 	=  	offset_angle0 + offset_angle1; 

	if ( (ZeroAngle[c] != null ) 
			&& ( ZeroAngle[c] >= MinAngle[c] && ZeroAngle[c] <= MaxAngle[c] )  )
		{ 	//[member=166016]BoringName[/member] , https://hydrogenaud.io/index.php/topic,110516.msg1054405.html#msg1054405
			var signal_level 	= 	dBToPct(db > 0 ? db+3 : db);
			angle = MinAngle[c]	+ 
					(signal_level <= 1 
					? signal_level * offset_angle0 
					: offset_angle0 + (signal_level - 1) * offset_angle1);
			
	} else {  //@Black_AVP , https://www.aimp.ru/forum/index.php?topic=52865.msg325067#msg325067 
			var ratio 		=	Math.abs(MinAngle[c]/offset_angle3);
			angle			=	(offset_angle3 * (  dBToPct(db - MaxLevel[c]) - ratio )) ; 
	};
	
	return angle;
}

		
	readFile: function (path) {
		const file = new ActiveXObject('ADODB.Stream');
		const doc = new ActiveXObject('Msxml2.DOMDocument.3.0');
		const element = doc.createElement('temp');
		element.dataType = 'bin.hex';
		file.Type = 1;
		file.Open();
		file.LoadFromFile(path);
		const hexArr = [];
		let i = file.Size;
		while (i--) {
			element.nodeTypedValue = file.Read(1);
			hexArr.push(String.fromCharCode(parseInt(element.text, 16)));
		}
		file.Close();
		return hexArr;
	},

@ilovefb2k :  thanks for your first posts in your project's dedicated thread!

A feature request:  please add the ability to read AIMP analog and LVU meters directly from a ZIP file, instead of having to unzip them to a folder first.  As the MusicBee VUMeter plugin and foo_vis_vumeter already do this, this would allow being able to use one shared skin folder for all three players.

You can parse binary data via activeX. For example I use this to parse .fpl native playlist on my playlist manager. (at least on SMP/JSplitter)
https://github.com/regorxxx/Playlist-Manager-SMP/blob/main/helpers/helpers_xxx_playlists_files_fpl.js

Code: [Select]

		
	readFile: function (path) {
		const file = new ActiveXObject('ADODB.Stream');
		const doc = new ActiveXObject('Msxml2.DOMDocument.3.0');
		const element = doc.createElement('temp');
		element.dataType = 'bin.hex';
		file.Type = 1;
		file.Open();
		file.LoadFromFile(path);
		const hexArr = [];
		let i = file.Size;
		while (i--) {
			element.nodeTypedValue = file.Read(1);
			hexArr.push(String.fromCharCode(parseInt(element.text, 16)));
		}
		file.Close();
		return hexArr;
	},

@ilovefb2k

JSP3 Analog VU Meter, version 1.0.0 DT-N 23-Nov-24



"Fisher.bin" appears fine.
But, If you select a different skin, you will need to restart foobar to see "Fisher.bin" again.

Task Manager CPU: 6.5 - 9.0

Windows 11 Home 24H2
Processor: AMD Ryzen 7 5700X 8-Core Processor 3.40 GHz
RAM: 48GB
GPU: NVIDIA GeForce RTX 4060

@ilovefb2k :  thanks for your first posts in your project's dedicated thread!

A feature request:  please add the ability to read AIMP analog and LVU meters directly from a ZIP file, instead of having to unzip them to a folder first.  As the MusicBee VUMeter plugin and foo_vis_vumeter already do this, this would allow being able to use one shared skin folder for all three players.

Quote from: sveakul on 2024-11-28 10:07:23

A reminder that the ilovefb2k JSP3 Script Analog VU Meter requires the installation of a Javascript Panel 3 version not exceeding 3.8.5.  Support for this meter display format was withdrawn by the JSP3 author after that version.  The 3.8.5 version is attached to this post.  At this time, the latest version of the meter script itself is 1.0.23 DT-N 23-Nov-24 and is also attached.  Full support for AIMP analog and AIMP LVU meters is provided.  BIN support is still in an experimental stage, and I recommend sticking with foo_vis_vumeter for BINs.

hi @sveakul ,
thank you for creating this thread and for your reminding that we still own @BoringName an implementation of BinExtractor 1.1 as a fb2k's VU meter BIN command-line utility extracting https://hydrogenaud.io/index.php/topic,110516.msg1054445.html#msg1054445. or https://getmusicbee.com/forum/index.php?topic=42174.msg230008#msg230008
Spoiler (click to show/hide)

it is so quick that another friYaY is coming and we definitely have something for this weekend.
let see what we can do 'cracking' BIN on-the-fly. 
as thing goes by, people are nice by nature and, sometimes, we have to do things that we really do not at all.

regards,
@ilovefb2k