@oops : just wanted to let you know I took the plunge to version 0.10.0 and I didn't turn into transparent columns, haha..  Thanks for making all that jazz on/off optional.. all running nice and smooth, thank you for your work!

One question: in the setting Options->Ignore Defaults, what are the "defaults" it is referring to?  Is that the bin.ini file inside some of the hiccup-authored skins?  In .9.1 this option was always greyed out, now I see it is active.

• INI file in RAR archive, that you mention from hiccup's skins. The supported parameters are fall, rise, singleMeter, peakLED, isVertical, curveAdj, and bgColour.
• Loose INI files that share their name with a BIN file, same as above otherwise.
• The scheme I made up to encode the layout for the screensaver mode in between the curly braces ({}) in the file name.

For the panels directory in Prefs/Advanced how do I enter a path for portable use? For example, ESLyrics path would be %fb2k_profile_path%DarkOne\Lyrics. But VU Meter doesn't accept this kind of path.

Quote from: Majestyk on 2025-03-01 08:07:22

For the panels directory in Prefs/Advanced how do I enter a path for portable use? For example, ESLyrics path would be %fb2k_profile_path%DarkOne\Lyrics. But VU Meter doesn't accept this kind of path.

Try adding a backslash "\" as the last character

Quote from: sveakul on 2025-03-01 11:40:05

Quote from: Majestyk on 2025-03-01 08:07:22

For the panels directory in Prefs/Advanced how do I enter a path for portable use? For example, ESLyrics path would be %fb2k_profile_path%DarkOne\Lyrics. But VU Meter doesn't accept this kind of path.

Try adding a backslash "\" as the last character

Thanks, but that doesn't work.

I create a junction for the couple of components that don't accept %fb2k_profile_path%.
Eg. mklink /j %APPDATA%\foobar2000-v2

For the panels directory in Prefs/Advanced how do I enter a path for portable use? For example, ESLyrics path would be %fb2k_profile_path%DarkOne\Lyrics. But VU Meter doesn't accept this kind of path.

Setting a custom path through advanced preferences definitely works for an absolute, local file path. It is not elegantly implemented since I don't really have a need for it and advanced preferences are kind of weird. The backslash at the end is implied and the component adds it automatically for you if it is not there.

Quote from: Defender on 2025-03-01 18:08:22

I create a junction for the couple of components that don't accept %fb2k_profile_path%.
Eg. mklink /j %APPDATA%\foobar2000-v2

For my own purposes I prefer to use symbolic links. For example, to share the VU meter path between x86 and x64:
foobar2000_x86\profile> New-Item -Type SymbolicLink -Path vumeter -Target ..\..\foobar2000_x64\profile\vumeter\

Quote from: Majestyk on 2025-03-01 08:07:22

For the panels directory in Prefs/Advanced how do I enter a path for portable use? For example, ESLyrics path would be %fb2k_profile_path%DarkOne\Lyrics. But VU Meter doesn't accept this kind of path.

Sure, done. Threw in environment variable expansion too (giving you all the weapons, please use responsibly . For next release.

@oops

I finally found the time to fully implement the ideas I had about using your foo_vis_vumeter in transparent mode in combination with blurring the background with the cover of the playing track/station.

I created a couple of VU skins with your code that are transparent all around and have the inner part with 50% alpha (and 20% shaded) and thus take full advantage of the blurred background. I attached the BIN's to this post.
Results look stunning imo.

So once again thank you for the staggering amount of work you put in to get transparency working (from PSS and JSplitter).

I'd like to remind you of the question I have about disabling the minimum sizecheck of foo_vis_vumeter, because I'd like to use foo_vis_vumeter without displaying parts outside the coordinates I gave in the main PSS instead of wrapping it in a child PSS.

Thx again.

Quote from: Defender on 2025-03-04 10:49:27

UTD + Alpha VU

Looks good! What js or component are you using for the top left panel? I'm pretty sure I've seen it before but I can't find it.
(Unless you wrote it yourself for personal use...then disregard)

Very long shot feature request:

If >2 channel audio data is available, to combine the L&R channels as follows:
L = FL + a*Center + b*Sub
R = FR + a*Center + b*Sub

where a,b are user configurable ratios.

uint32_t left_channels = channel_front_left | channel_back_left | channel_front_center_left | channel_side_left | channel_top_front_left | channel_top_back_left;
uint32_t right_channels = channel_front_right | channel_back_right | channel_front_center_right | channel_side_right | channel_top_front_right | channel_top_back_right;
uint32_t center_channels = channel_front_center | channel_lfe | channel_back_center | channel_top_center | channel_top_front_center | channel_top_back_center;
std::array<int8_t, defined_channel_count> mix_factors{0, 0, -3, -10, -3, -3, -6, -6, -6, -3, -3, -6, -3, -6, -3, -3, -6, -3}; // front_left, front_right, front_center, lfe, back_left, back_right, front_center_left, front_center_right, back_center, side_left, side_right, top_center, front_left, front_center, front_right, back_left, back_center, back_right

• Catch DirectX adapter creation runtime errors to stop UI element window creation (instead of exiting foobar2000 with a "crash")
• Add "%fb2k_profile_path%" and environment variable expansion to advanced panels directory option
• Update foobar2000 SDK to 2025-03-07

Quote from: boxerfan88 on 2025-03-08 13:54:31

Very long shot feature request:

If >2 channel audio data is available, to combine the L&R channels as follows:
L = FL + a*Center + b*Sub
R = FR + a*Center + b*Sub

where a,b are user configurable ratios.

Current multi-channel mixing is as follows:

Code: [Select]

uint32_t left_channels = channel_front_left | channel_back_left | channel_front_center_left | channel_side_left | channel_top_front_left | channel_top_back_left;
uint32_t right_channels = channel_front_right | channel_back_right | channel_front_center_right | channel_side_right | channel_top_front_right | channel_top_back_right;
uint32_t center_channels = channel_front_center | channel_lfe | channel_back_center | channel_top_center | channel_top_front_center | channel_top_back_center;
std::array<int8_t, defined_channel_count> mix_factors{0, 0, -3, -10, -3, -3, -6, -6, -6, -3, -3, -6, -3, -6, -3, -3, -6, -3}; // front_left, front_right, front_center, lfe, back_left, back_right, front_center_left, front_center_right, back_center, side_left, side_right, top_center, front_left, front_center, front_right, back_left, back_center, back_right

Left panel gets left and center channels. Right panel right gets right and center channels. The mix factors attenuate center channels by half, generally, since they are mixed into both channels. There are too many channels (18) to intuitively allow for a specific mix factor for each. In case it wasn't obvious, the mix factors are in decibels.

The needle is displayed before lights are applied. As a result, part of the needle disappears behind Lights.
Can you change this?

Quote from: Defender on 2025-03-15 16:03:58

The needle is displayed before lights are applied. As a result, part of the needle disappears behind Lights.
Can you change this?

Can you be more specific? What type of skin is this? AIMP-style or BIN-style. If it's BIN-style, I think I can swap the drawing order.

Quote from: oops on 2025-03-09 07:33:56

Current multi-channel mixing is as follows:

Code: [Select]

uint32_t left_channels = channel_front_left | channel_back_left | channel_front_center_left | channel_side_left | channel_top_front_left | channel_top_back_left;
uint32_t right_channels = channel_front_right | channel_back_right | channel_front_center_right | channel_side_right | channel_top_front_right | channel_top_back_right;
uint32_t center_channels = channel_front_center | channel_lfe | channel_back_center | channel_top_center | channel_top_front_center | channel_top_back_center;
std::array<int8_t, defined_channel_count> mix_factors{0, 0, -3, -10, -3, -3, -6, -6, -6, -3, -3, -6, -3, -6, -3, -3, -6, -3}; // front_left, front_right, front_center, lfe, back_left, back_right, front_center_left, front_center_right, back_center, side_left, side_right, top_center, front_left, front_center, front_right, back_left, back_center, back_right

Left panel gets left and center channels. Right panel right gets right and center channels. The mix factors attenuate center channels by half, generally, since they are mixed into both channels. There are too many channels (18) to intuitively allow for a specific mix factor for each. In case it wasn't obvious, the mix factors are in decibels.

Ah ... i see.
Any chance to expose mix_factors for user adjustments?
Either in config_panel or foobar_advanced_preferences?
Thank you in advance for your consideration.

• Fix multi-monitor behavior during fullscreen
• Draw LEDs before the needle in BIN-style panels

• Do not regenerate panels directory when using a custom panel path
• Add mixer dialog

On a related topic, may I know why the FC isn't downmixed into the left_channel or right_channel for VU display, instead FCL and FCR is used instead?

Features from forum requests:

• Do not regenerate panels directory when using a custom panel path

How did you figure that? All "center channels" are mixed in equally into right and left. The reason the center channel levels are (generally) halved in the default levels _is_ because of they are "downmixed" into the L and R stereo channels. The C channel would overwhelm the traditional L and R ones if left at 0 dB (which is why I made the default -3 dB; the ideal assuming equidistant channel separation from and constructive interference at the listening position). This mixing is very clearly visible when using test tones.
According to foobar2000 SDK, 5.1 is: FL, FR, FC, BL, BR, LFE. I had always thought SL and SR were for 5.1 with BL and BR completing the 7.1 configuration. But in this case, following the SDK. If the channels are not included in the PCM stream or they are silent, there is no impact.

uint32_t left_channels = channel_front_left | channel_back_left | channel_front_center_left | channel_side_left | channel_top_front_left | channel_top_back_left;
uint32_t right_channels = channel_front_right | channel_back_right | channel_front_center_right | channel_side_right | channel_top_front_right | channel_top_back_right;
uint32_t center_channels = channel_front_center | channel_lfe | channel_back_center | channel_top_center | channel_top_front_center | channel_top_back_center;

I didn't see front_center in the left_channels and right_channels, that is why I asked.
Now that you've clarified, it is my misunderstanding. My apologies.

VU_L = left_channels + center_channels
VU_R = right_channels + center_channels