The updated foo_vis_vumeter is a reimagining of the existing analog VU meter component. It decodes panels from the same ".bin" files and it renders using DirectX 12.

It is available in the components repository.

Enjoy!

Feature request:  add "Tuning -> Off" that ignores the mouse wheel.

I send Qobuz streaming by mConnect to Foobar and all working well, also VST. But component like VuMeter or Waveform seeker doesn't move. Can you help me?

Looks fantastic in action, responds very similar to a real vu meter. I have experienced crashes though, doesn't seem to play nicely with your milkdrop2 component. No crashes when each one is used on its own but together foobar2000-v2 crashes.

Suggestion: Support vumeter panel in CUI layout Directx 11

Suggestion: Support multiple vumeter panels in DUI layout

Can you tell me how to change these settings?

Quote from: foobrik on 2024-10-10 08:34:02

Can you tell me how to change these settings?

Ha. Took me a while to figure out too.

Select one of the options (eg. Decay), you will see a "dot" beside it to show it is selected.
Then scroll the mouse wheel.
You should see the values change.

.

Quote from: boxerfan88 on 2024-10-09 15:56:46

Feature request:  add "Tuning -> Off" that ignores the mouse wheel.

Done, will be in the next release. Thanks for the idea!

Quote from: Angelo58 on 2024-10-09 18:05:23

I send Qobuz streaming by mConnect to Foobar and all working well, also VST. But component like VuMeter or Waveform seeker doesn't move. Can you help me?

Nope. I do not subscribe to any streaming services so I don't know how they plug in through foobar2000. Since another component is also not wiggling, I would say that the PCM data is not getting into the player. More than that I wouldn't know.

Quote from: Mekoz on 2024-10-09 15:53:53

Looks fantastic in action, responds very similar to a real vu meter. I have experienced crashes though, doesn't seem to play nicely with your milkdrop2 component. No crashes when each one is used on its own but together foobar2000-v2 crashes.

Thanks! Strange, I've been running 0.1.9 non-stop alongside the development version of VU meter for the past 3 weeks. Never seen a crash caused by interaction between the two; or a crash for that matter. Also getting through hibernation and other system state transitions without issue. I'll try to take a look at the crash dump.

Quote from: Cardiacs on 2024-10-09 13:44:21

Suggestion: Support vumeter panel in CUI layout Directx 11

Nope to both. DUI is already a huge effort due to the lifecycle/resource management required for DirectX. This is the biggest source of bugs and dev time wastage. Having to discover all the idiosyncrasies inherent in CUI is not something I want to dive into.
And if your machine(s) cannot support DirectX 12, I don't know what to tell you. The minimum supported Feature Level for this component is "11_0". You can look at Wikipedia for a list of GPUs that support Direct3D 12 and, specifically, look at the "11_0" row in the table.
If you're asking because you're intending to run through Wine/DXVK or some other translation layer, that is way beyond the scope of this component.

Quote from: yeyo on 2024-10-09 12:56:51

Suggestion: Support multiple vumeter panels in DUI layout

Similar answer as above. The way the component is structured is very similar to a game. So, in essence you're asking to run 2 instances of a game sharing the same engine and static data under the same application in 2 different windows. The component has very limited control of its windows and message queues, which makes what you're asking to require largely rearchitecting the component.

I wanted to say a new argument

I use the plugin via visualizations. Is it possible to correct the display of settings? The first picture shows the settings after launching the plugin. The second picture shows the settings after expanding the plugin window to full screen, and then collapsing

Feature request: support skins designed for Analog Meter visualization for AIMP player in-addition to DRON's analog VU meter for foobar2000, so we can have classic and night variant of AIMP's analog VU meter visualization.

Also, how about a Mid/Side mode like in my own multichannel peakmeter visualizer? Which when selected, the VU meter visualization would display M/S (sum and difference channels respectively) instead of L/R channels.

@oops :
Could you please post what the default values are for all the option settings in 0.1.2 beta?  Thanks!

// Defaults
constexpr bool default_debug_output = false;
constexpr bool default_lock_aspect_ratio = false;
constexpr bool default_downmix = false;
constexpr bool default_cubic_interpolation = true;
constexpr bool default_lock_tuning = false;
constexpr bool default_vsync = false;
constexpr float default_zero = 0.0f;
constexpr float default_range = 0.0f;
constexpr float default_decay = 0.01f;
constexpr float default_rise_factor = 0.2f;
constexpr float default_jitter = 0.0f;
constexpr float default_round_corners = 1.0f;
constexpr double default_preamp_gain = 0.0;
constexpr double default_sample_window = 42.0;
constexpr uint32_t default_max_fps = 60;
constexpr layout default_layout = layout::LEFT_RIGHT__V;
constexpr mode default_mode = mode::LR;
constexpr level default_level = level::RMS;
constexpr tune default_tune = tune::ZERO;
constexpr std::wstring_view default_panel = L"Model 702.bin";
constexpr bool default_enable_hdr = false;
constexpr DXGI_FORMAT default_back_buffer_format = DXGI_FORMAT_B8G8R8A8_UNORM;
constexpr DXGI_FORMAT default_depth_buffer_format = DXGI_FORMAT_D32_FLOAT;
constexpr UINT default_back_buffer_count = 2;
constexpr D3D_FEATURE_LEVEL default_min_feature_level = D3D_FEATURE_LEVEL_11_0;

Spoiler (click to show/hide)

Quote from: foobrik on 2024-10-10 11:12:44

I use the plugin via visualizations. Is it possible to correct the display of settings? The first picture shows the settings after launching the plugin. The second picture shows the settings after expanding the plugin window to full screen, and then collapsing

Good eye. Thanks for noticing. Fixed in 0.1.3.

Quote from: TF3RDL on 2024-10-11 15:43:30

Feature request: support skins designed for Analog Meter visualization for AIMP player in-addition to DRON's analog VU meter for foobar2000, so we can have classic and night variant of AIMP's analog VU meter visualization.

Also, how about a Mid/Side mode like in my own multichannel peakmeter visualizer? Which when selected, the VU meter visualization would display M/S (sum and difference channels respectively) instead of L/R channels.

Mid/Side added in 0.1.3. Not multichannel yet, only stereo at the moment.
Also completed enabling of the AIMP skins, but the needle movement is trash at the moment. So, I skipped including it in 0.1.3.

Quote from: sveakul on 2024-10-13 21:07:29

@oops :
Could you please post what the default values are for all the option settings in 0.1.2 beta?  Thanks!

Sure, quick copy/paste because of time constraints:

// Defaults
constexpr bool default_debug_output = false;
constexpr bool default_lock_aspect_ratio = false;
constexpr bool default_downmix = false;
constexpr bool default_cubic_interpolation = true;
constexpr bool default_lock_tuning = false;
constexpr bool default_vsync = false;
constexpr float default_zero = 0.0f;
constexpr float default_range = 0.0f;
constexpr float default_decay = 0.01f;
constexpr float default_rise_factor = 0.2f;
constexpr float default_jitter = 0.0f;
constexpr float default_round_corners = 1.0f;
constexpr double default_preamp_gain = 0.0;
constexpr double default_sample_window = 42.0;
constexpr uint32_t default_max_fps = 60;
constexpr layout default_layout = layout::LEFT_RIGHT__V;
constexpr mode default_mode = mode::LR;
constexpr level default_level = level::RMS;
constexpr tune default_tune = tune::ZERO;
constexpr std::wstring_view default_panel = L"Model 702.bin";
constexpr bool default_enable_hdr = false;
constexpr DXGI_FORMAT default_back_buffer_format = DXGI_FORMAT_B8G8R8A8_UNORM;
constexpr DXGI_FORMAT default_depth_buffer_format = DXGI_FORMAT_D32_FLOAT;
constexpr UINT default_back_buffer_count = 2;
constexpr D3D_FEATURE_LEVEL default_min_feature_level = D3D_FEATURE_LEVEL_11_0;