HydrogenAudio

Its for DUI, not CUI.

I'll add to the wish list, if at all possible, a config window like old plugin had:

Hi,
this component does not work for me.
FB2.0, 64bit, Win10.
The component installs ok (tried both versions) but when I play audio and click view-visualisations-spectrum analyser I just get a black window with nothing inside.

Quote from: wojak on 2023-11-13 17:09:49

Hi,
this component does not work for me.
FB2.0, 64bit, Win10.
The component installs ok (tried both versions) but when I play audio and click view-visualisations-spectrum analyser I just get a black window with nothing inside.

Have you started playing a track? The display 'in rest' is still a black background.

Yes, as I have written "when I play audio". I know that when idle, there is nothing to be displayed. But this component just does not display anything for me. Just blank window.

This is a very early alpha release which contains no logging or diagnostics code. At this stage I'm unable to help you,

Just installed the third version on this component. Still just blank black window. All other visualisations and meters work properly.

v0.1.0.3, 2023-11-14

* New: Implemented the frequency bands of AveePlayer (https://aveeplayer.com/).

* New: Implemented the smoothing methods of the spectrum.
  * This addresses one of the early comments about the 'jitter' in the rendering. F.e. use "SmoothingMethod: 1" and "SmoothingFactor: 0.75"

v0.1.0.3, 2023-11-14

* New: Implemented the frequency bands of AveePlayer (https://aveeplayer.com/).
* New: Implemented the smoothing methods of the spectrum.
  * This addresses one of the early comments about the 'jitter' in the rendering. F.e. use "SmoothingMethod: 1" and "SmoothingFactor: 0.75"
* New: Added some DirectX debug logging to the console. Set the "LogLevel" parameter to 1 to enable; Use 6 (default) to disable.

Blank for me too, this and the last version. Latest FB2K release version, Win 11 Pro, everything at 96kHz.

Color: only Solid works (blue).

Edit: Everything in the Configuration works only in the default settings.

v0.1.0.4, 2023-11-16

* New: Implemented color schemes.
* New: Implemented the peak value indicators.
* Improved: Replaced the FFT with one that supports complex values and non-radix-2 FFT sizes.
* Improved: Improved and refactored rendering code.
* Added some more diagnostics code.
  * LogLevel 0 will write messages to the console everytime an audio chunk and the spectrum gets rendered.

Please check the wiki (https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Components/Spectrum_Analyzer_(foo_vis_spectrum_analyzer)) for an explanation about the parameters.

With this version I have a blank window with horizontal and vertical lines (grids) and dB values on the left. Still no "content" (while playing audio files).

I'm still not able to change this settings in configuration window.

Quote from: wojak on 2023-11-17 15:31:26

With this version I have a blank window with horizontal and vertical lines (grids) and dB values on the left. Still no "content" (while playing audio files).

Thx. At least the rendering code works. What happens if you set the log level to 0 (Trace)?

The following messages can appear in the console:

- Unable to create visualisation stream.
- Visualisation stream is invalid.
- Rendering chunk { ChannelCount: %d, SampleRate: %d }.
- Rendering %d bands.

If you mean the last position in the advanced settings, changing the digit from 3 to 0 does nothing. The console does not show any info when starting or closing your component.

Quote from: wojak on 2023-11-17 18:16:53

If you mean the last position in the advanced settings, changing the digit from 3 to 0 does nothing. The console does not show any info when starting or closing your component.

That should not be possible...

foo_vis_spectrum_analyzer: Rendering chunk { ChannelCount: 2, SampleRate: 44100 }.
foo_vis_spectrum_analyzer: Rendering 160 bands.

foo_vis_spectrum_analyzer: RenderTarget: { Width: 661, Height: 409 }

I've noticed that the installation each new version deletes the existing json file.

Looking forward to a fully functional GUI control panel.

@pqyt This should allow different instances of this component have its own settings right?

BTW, I hope this new Musical Spectrum remake doesn't get into the list of known problematic components list (which means I can't recommend this to someone else if it is listed as problematic/glitchy)

Quote from: TF3RDL on 2023-11-18 01:56:58

@pqyt This should allow different instances of this component have its own settings right?

What's the use case for this?

Quote from: pqyt on 2023-11-18 08:21:18

Quote from: TF3RDL on 2023-11-18 01:56:58

@pqyt This should allow different instances of this component have its own settings right?

What's the use case for this?

To be able to use this plugin in possible different spots in your skin at the same time with different layout. I personally do this a lot with foo_uie_vis_peakmeter_spectrum, foo_vis_vumeter and foo_uie_vis_channel_spectrum.

And how do you select which settings to use? Some kind of saveable preset mechanism?

Quote from: Defender on 2023-11-18 10:24:03

Quote from: pqyt on 2023-11-18 08:21:18

Quote from: TF3RDL on 2023-11-18 01:56:58

@pqyt This should allow different instances of this component have its own settings right?

What's the use case for this?

To be able to use this plugin in possible different spots in your skin at the same time with different layout. I personally do this a lot with foo_uie_vis_peakmeter_spectrum, foo_vis_vumeter and foo_uie_vis_channel_spectrum.

And how do you select which settings to use? Some kind of saveable preset mechanism?

No. That could be extra functionality added on top but per instance data is saved by fb2k in your theme.fth. Instead of using cfg_var and friends, you'd use set_configuration and get_configuration from ui_element_instance.

Quote from: TF3RDL on 2023-11-18 01:56:58

BTW, I hope this new Musical Spectrum remake doesn't get into the list of known problematic components list (which means I can't recommend this to someone else if it is listed as problematic/glitchy)

You sure know how to motivate someone...

* New: Implemented logarithmic Y axis.

The configuration dialog is not pretty to look at, has a lot of rough edges and is not user-friendly but it works. Use it to play with but except things to change (and hopefully improve).

The JSON file will be ignored from now on, possibly later to be re-used for loading and saving presets.

v0.2.0.0, 2023-11-18

* New: Implemented a configuration dialog.
* New: Implemented logarithmic Y axis.
* New: Experimental "Fade-Out" mode for the peak indicators.

You can download it from the Components (https://www.foobar2000.org/components/view/foo_vis_spectrum_analyzer) repository.

The configuration dialog is not pretty to look at, has a lot of rough edges and is not user-friendly but it works. Use it to play with but except things to change (and hopefully improve).
The JSON file will be ignored from now on, possibly later to be re-used for loading and saving presets.

So again I removed the component. Now everything seems to be OK.

One thing that would help, would be if it were made clearer which settings affected use as a frequency spectrum analyzer as opposed to a musical spectrum display.  It's my understanding that it is meant to serve both functions optionally.  Maybe splitting off the parts of the config that only affect one or the other?

Also, it would be nice to see a clarification of what the settings actually do, perhaps in a readme (skew factor, bandwidth, use absolute, smooth lower frequencies, etc.).

Very nice work!

Quote from: sveakul on 2023-11-19 19:10:58

Also, it would be nice to see a clarification of what the settings actually do, perhaps in a readme (skew factor, bandwidth, use absolute, smooth lower frequencies, etc.).

I started updating the wiki (https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Components/Spectrum_Analyzer_(foo_vis_spectrum_analyzer)) but it needs a lot more work. And to be frank, some of the parameters I don't understand myself yet  :D .

• Skew factor: Basically a parameter that affects any adjustable frequency scaling functions like hyperbolic sine and nth root. Higher values means more linear spectrum (in the case of Avee Player's frequency distribution, exactly linear when this parameter is 1)
• Bandwidth: Basically a distance between low and high frequency boundaries for each band, I think this parameter is more useful for constant-Q/variable-Q transforms and Mel/triangular filterbank energies (higher values smooths out the spectrum and reduces the visual noise) than bandpower mode that we have currently at the time
• Use absolute: Which sets min dB range to -Infinity dB (0.0 on linear amplitude) when enabled. This only applies when not using logarithmic amplitude scale (or in other words, using linear/nth root amplitude scaling) as by mathematical definition, logarithm of any base of zero is always -Infinity
• Smooth lower frequencies: When enabled, the bandpower part is only gets used when number of FFT bins to sum for each band is at least two or more (rather than one in the case of this parameter is set to disabled, which of course, has artifacts on lower frequencies similar to ones seen in spectrum visualizations on YouTube videos generated by ZGameEditor Visualizer that comes with FL Studio like this (https://www.youtube.com/watch?v=F0QLJbyGQ40)), otherwise a sinc/Lanczos-interpolated spectrum

• There's a white border inside the window frame. Is it possible to hide it?
• Visualization doesn't work when I show the popup window the first time after launching the program and playing a track. I have to replay the currently playing track to make it work. But it works as expected after that even if I close and show the popup window again.

Thank you very much. Great component.

There's a white border inside the window frame. Is it possible to hide it?

Visualization doesn't work when I show the popup window the first time after launching the program and playing a track. I have to replay the currently playing track to make it work. But it works as expected after that even if I close and show the popup window again.

@pqyt

> 2. Visualization doesn't work when I show the popup window the first time after launching the program and playing a track. I have to replay the currently playing track to make it work. But it works as expected after that even if I close and show the popup window again.

Not made into a panel. Display in PopUp.

1. Play the track.
2. "Menu > View > Visualizations > Spectrum Analyzer"  start.
3. Spectrum Analyzer screen is the same as when stopped.
4. Play the track.
5. Spectrum Analyzer starts working.

Thanks a lot that's wonderful. Also, this is what I mean with the white border.

v0.3.0.0, 2023-11-20

* New: Implemented a first version of a Constant-Q transform (CQT). Default is still FFT.

* New: A custom FFT size can be specified in the configuration dialog.
* New: A sample rate-based FFT size can be specified in the configuration dialog. The FFT size will be calculated based on the duration specified and the sample rate of the track being played.

* New: Implemented Mel scale mapping of the FFT coefficients.

@pqyt
Much appreciated. I've noticed the full screen mode is greyed out in the new release. Is it for the time being?

Quote from: pqyt on 2023-11-20 19:43:18

* New: Implemented Mel scale mapping of the FFT coefficients.

I went with the Mel name because that's what I found articles about. If "Triangular Filter Bank" is more accurate, I'll change it.

I went with the Mel name because that's what I found articles about. If "Triangular Filter Bank" is more accurate, I'll change it.

I went with the Mel name because that's what I found articles about.

• the Y axis doesn't show the full -120dB scale
• the X axis frequency is not shown
• the X axis seems to be cutoff at 3kHz -- the spectrum display should run until 40kHz

@pyqt -- Thank you for a very very nice component!

I am running 0.3.0.0 and I've observed some issues.

Two of my laptops are experiencing the same symptoms.
Is it a similar environment?

Are you running with high(er) DPI settings? While everything is designed to support it I haven't really tested that setup yet.

• the X axis frequency is not shown
• the X axis seems to be cutoff at 3kHz -- the spectrum display should run until 40kHz

Quote from: boxerfan88 on 2023-11-22 02:19:57

• the X axis frequency is not shown
• the X axis seems to be cutoff at 3kHz -- the spectrum display should run until 40kHz

Same issue here with no frequency labelling of the X axis, and no apparent change when its mode is changed.  Seems to be cutting off the high end altogether as boxerfan88 notes.  My display is just a W10 125% scale and 1920 X 1080 resolution..[/list]

Not trying to annoy, just letting you know we are on the same page.

v0.4.0.0, 2023-11-26

* New: Most colors and the custom color scheme can be modified in the configuration dialog.
* Improved: Each instance of the component now has its own configuration. Note: The fullscreen version is a separate instance.
* Improved: Added spin buttons to most numeric controls.
* Changed: Mel scale mapping is now called Triangular Filter Bank scale mapping.

You can download it from the Components (https://www.foobar2000.org/components/view/foo_vis_spectrum_analyzer) repository.

You'll notice that the configuration dialog is becoming quite large and complex. Please report any quirks or crashes.

Some issues I have:
- still no labels on X axis (no digits nor letter, no Hz,no Notes)
- because there are no labels (see above) I am not 100% sure but it seems that changing values (like Hz or notes range) has no effect on the display. Ex. I change frequency to 96kHz and play an mp3 file....and to my suprise I see moving bars right to the right end of the component window. How is that possible for mp3 to be able to "play" 96kHz? So either the bars show something different than they should or the changes do not take effect. As somebody has written earlier - it looks likje the display is cut at some low/mid frequency and does not show anything higher no matter what changes in the menu we make.
Please make x axis values visible (just like Y axis and dB are) so we would know what we really see.

Using different Windows DPI setting than 100% clips the contents of the window and things are only partially visible. At least here easily reproducible.

X axis is OK. There is still a problem with the Y axis.
Hmm, how do I use it?

I'm afraid my experiences with 0.4.0.0 are the same as wojak--there is no visible X-axis labelling either by frequency or note.  This is using Foobar 2.1 x64 2023-11-22 preview, Windows x64 at 125% scale on a 1920X1080 display resolution.  The images attached here show what I am seeing, and what my settings are.  The plugin was added as a regular tabbed fixed UI element using Layout Editing Mode, like all my stuff is.

A new "irritation" of this version is the inablity to change band no. or frequency range quickly by using the delete or backspace key in the setting boxes and typing the desired value--now you must use the small up/down arrow buttons for any change made.

Quote from: Case on 2023-11-27 06:29:29

Using different Windows DPI setting than 100% clips the contents of the window and things are only partially visible. At least here easily reproducible.

It's not here. I just switched one of my screens to 125%, created a new tab and added a new instance of the element. Perfect sizing from the start.

For example, the top of the Y axis (-6db) cannot be displayed any further.
Is it something like this?

Quote from: pqyt on 2023-11-27 08:13:28

Quote from: Case on 2023-11-27 06:29:29

Using different Windows DPI setting than 100% clips the contents of the window and things are only partially visible. At least here easily reproducible.

It's not here. I just switched one of my screens to 125%, created a new tab and added a new instance of the element. Perfect sizing from the start.

I can match the behavior you see by adjusting foobar2000 compatibility settings and forcing it to use System performed DPI scaling. Then the spectrum isn't clipped and all text goes blurry, like in your screenshot. But with default settings the scaling is unfortunately off. Doesn't matter whether the element is embedded to the UI or just opened quickly as a popup from the main menu.

the inability to manually put desired values into boxes is a shortcoming for me too.

Quote from: wojak on 2023-11-27 09:21:53

the inability to manually put desired values into boxes is a shortcoming for me too.

Some people would call that a UI improvement... Out of the box there's no decent numeric textbox with a spin control and edit functionality. I'm not yet 100% satisfied with the UI yet. I'll see what I can do.

I find it hard to accept that to view the X-axis when Windows is set to 125% scale (necessary for my vision) I must reset the DPI compatibility settings of the whole application and end up with blurry text.  The other spectrums I use on the same computer--Musical Spectrum with FB 1.6.17, and Enhanced Spectrum Analyzer with FB 2.1 64-bit--both show the X and Y axis just fine and with no compromise to the text.  I would hate to have to abandon such an excellent addition to FB's visualization selections because of this surely curable problem;  please,  I encourage you to give this thing another try.  Thanks!!

Edit: Breakthrough! At least I can reproduce it now... Thx to @Case  for saying the right thing at the right moment...

Not sure if it has been mentioned before... clicking Reset in the configuration panel crashes.
Some settings are reset when restarting again, but not all.
Tested in both 32/64 bit with the latest fb2k preview and component versions.

• More transform options: Sliding windowed infinite Fourier transform/SWIFT (https://codepen.io/TF3RDL/pen/JjBzjeY) (similar to DFT Progressive on ColorChord) and analog-style (or more accurately, IIR filter bank) spectrum analysis algorithms, with latter having symmetrical peak shape when viewed on a logarithmic frequency scale (asides from cramping) and different filter coefficient configurations (e.g. Butterworth, Chebysev type I and type II, Elliptic, Bessel, and Linkwitz-Riley) act as window types and as for both types, it have a filter order parameter to reduce leakage at the expense of bad time resolution
• Changes on config dialog: Y-axis mode should be changed to only affect dB/amplitude labels/lines and a dedicated checkbox option called "Logarithmic amplitude scale" is used instead to change the amplitude scale from/to decibels/logarithmic and linear/nth root

Are you using 0.4.1.1? The 0.4.1.0 version had that regression.

A crash happens in configuration panel.
Steps to reproduce:
1. Change color scheme to custom and edit any of the colors and press OK.
2. Scroll the color scheme drop-down-list box using the mouse scroll wheel and the program crashes.

Thanks pqyt, can't find a thing wrong with this superb spectrum!  Your hard work much appreciated.

Just updated to 0.4.1.1, the scaling is fixed, both the axis are displaying properly. Very nice indeed!
Thank you very much for developing this component!

Quote from: sveakul on 2023-11-29 21:28:47

Thanks pqyt, can't find a thing wrong with this superb spectrum!  Your hard work much appreciated.

Thx but @TF3RDL should also be credited for his prototype and the math. Without that it would have taken a lot longer than 14 days to get this far.

One issue: now the settings popup is always "full-screen" vertically (meaning from the top to the bottom, but not horizontally) of my screen and can't be shrinked. Because is it from top to bottom, "reset", "OK" and "cancel" buttons are hidden behind MSWindows taskbar (bottom bar). I also cant move the settings window to another position. So the only way to change settings of the plugin (which needs "OK" to be clicked) is to change the settings of MSWin to auto-hide the taskbar - only then I can see the "OK" button of settings window.
ain - thank you for this component.

Quote from: wojak on 2023-12-01 07:39:02

One issue: now the settings popup is always "full-screen" vertically (meaning from the top to the bottom, but not horizontally) of my screen and can't be shrinked. Because is it from top to bottom, "reset", "OK" and "cancel" buttons are hidden behind MSWindows taskbar (bottom bar). I also cant move the settings window to another position. So the only way to change settings of the plugin (which needs "OK" to be clicked) is to change the settings of MSWin to auto-hide the taskbar - only then I can see the "OK" button of settings window.
ain - thank you for this component.

The dialog is 'only' 700 pixels height. Even at 125% that's only 875 pixels. What's you're display resolution?

Quote from: pqyt on 2023-12-01 12:30:19

Quote from: wojak on 2023-12-01 07:39:02

One issue: now the settings popup is always "full-screen" vertically (meaning from the top to the bottom, but not horizontally) of my screen and can't be shrinked. Because is it from top to bottom, "reset", "OK" and "cancel" buttons are hidden behind MSWindows taskbar (bottom bar). I also cant move the settings window to another position. So the only way to change settings of the plugin (which needs "OK" to be clicked) is to change the settings of MSWin to auto-hide the taskbar - only then I can see the "OK" button of settings window.
ain - thank you for this component.

The dialog is 'only' 700 pixels height. Even at 125% that's only 875 pixels. What's you're display resolution?

Hi,

my resolution is 1920*1080.
I can drag the left or right edge of the window and widen it with mouse. But I can't do anything vertically. It stays solid from the bottom to the upper edge. Can't change the position of the window. Only widening is possible.

Quote from: wojak on 2023-12-01 16:36:52

Quote from: pqyt on 2023-12-01 12:30:19

Quote from: wojak on 2023-12-01 07:39:02

One issue: now the settings popup is always "full-screen" vertically (meaning from the top to the bottom, but not horizontally) of my screen and can't be shrinked. Because is it from top to bottom, "reset", "OK" and "cancel" buttons are hidden behind MSWindows taskbar (bottom bar). I also cant move the settings window to another position. So the only way to change settings of the plugin (which needs "OK" to be clicked) is to change the settings of MSWin to auto-hide the taskbar - only then I can see the "OK" button of settings window.
ain - thank you for this component.

The dialog is 'only' 700 pixels height. Even at 125% that's only 875 pixels. What's you're display resolution?

Hi,

my resolution is 1920*1080.
I can drag the left or right edge of the window and widen it with mouse. But I can't do anything vertically. It stays solid from the bottom to the upper edge. Can't change the position of the window. Only widening is possible.

Any window 'enhancer' or tiling tool that you are running? The configuration dialog is a standard modeless dialog without a min/max button. Have you tried to Reset all the settings? Possibly they are corrupt after trying some of the earlier alpha's.

My only two requests are (1) to have a way to color notes black and white just like on a piano keyboard, so the identities of the notes can more easily be recognized at a glance. (I like using it to see what notes singers are actually hitting.)

And (2) to have 30 Hz as a "refresh rate limit" option, (but this is really quite minor, and in the meantime I can just use 20Hz or 60Hz and hardly even see the difference).

@pqyt

Spectrum Analyzer Configurartion Windows fonts:

Can you make it a system font?
Or is it not possible to choose?

Unfortunately, problems from the get-go with 0.4.2.0:

1.  Right-clicking inside the panel and choosing "Configure" only produces a "flickering" square showing the pointer's freq/note position, no configuration window appears.

2.  Also created is an odd box in the upper left corner of Foobar with "S..  ?  X" in it that does nothing I can determine, except hitting the "X" makes it go away (see attached).

(Foobar x64 2.1 2023-11-27 Preview)

Quote from: Air KEN on 2023-12-04 04:48:12

@pqyt

Spectrum Analyzer Configurartion Windows fonts:

Can you make it a system font?
Or is it not possible to choose?

The font of the dialog itself because that should already be the case? Or do you mean the font of the text used on the axes?

Quote from: sveakul on 2023-12-03 21:47:21

Unfortunately, problems from the get-go with 0.4.2.0:

1.  Right-clicking inside the panel and choosing "Configure" only produces a "flickering" square showing the pointer's freq/note position, no configuration window appears.

2.  Also created is an odd box in the upper left corner of Foobar with "S..  ?  X" in it that does nothing I can determine, except hitting the "X" makes it go away (see attached).

(Foobar x64 2.1 2023-11-27 Preview)

The flickering is the tooltip that seems to turn on and off. And how you get a 0x0 dialog by default is a mystery, for now...

Unfortunately, problems from the get-go with 0.4.2.0:

1.  Right-clicking inside the panel and choosing "Configure" only produces a "flickering" square showing the pointer's freq/note position, no configuration window appears.

2.  Also created is an odd box in the upper left corner of Foobar with "S..  ?  X" in it that does nothing I can determine, except hitting the "X" makes it go away (see attached).

(Foobar x64 2.1 2023-11-27 Preview)

You can resize and reposition it for now. The new size and position will be remembered from then on. It's a stupid initialization bug...

Quote from: pqyt on 2023-12-04 05:29:12

Quote from: sveakul on 2023-12-03 21:47:21

Unfortunately, problems from the get-go with 0.4.2.0:

1.  Right-clicking inside the panel and choosing "Configure" only produces a "flickering" square showing the pointer's freq/note position, no configuration window appears.

2.  Also created is an odd box in the upper left corner of Foobar with "S..  ?  X" in it that does nothing I can determine, except hitting the "X" makes it go away (see attached).

(Foobar x64 2.1 2023-11-27 Preview)

The flickering is the tooltip that seems to turn on and off. And how you get a 0x0 dialog by default is a mystery, for now...

Quote from: sveakul on 2023-12-03 21:47:21

Unfortunately, problems from the get-go with 0.4.2.0:

1.  Right-clicking inside the panel and choosing "Configure" only produces a "flickering" square showing the pointer's freq/note position, no configuration window appears.

2.  Also created is an odd box in the upper left corner of Foobar with "S..  ?  X" in it that does nothing I can determine, except hitting the "X" makes it go away (see attached).

(Foobar x64 2.1 2023-11-27 Preview)

You can resize and reposition it for now. The new size and position will be remembered from then on. It's a stupid initialization bug...

resizing works but it does nothing good for me. If I shrink the windowI can't see the whole content so I still can't accept the changes (as I do not see the OK button). The window is bigger than the previous one so it is even worse.

Quote from: wojak on 2023-12-04 10:25:45

resizing works but it does nothing good for me. If I shrink the windowI can't see the whole content so I still can't accept the changes (as I do not see the OK button). The window is bigger than the previous one so it is even worse.

But if you shrink it from the top you can move it so that the OK button becomes accessible.

I just installed v. 0.4.2.1 and still both defects exist:
- can't use settings because the window does not fit on the screen and can't be properly shinked

- frequencies/notes displayed on the bars are improper

Any chances to add as panel in Columns UI like other visualizations?

Quote from: wojak on 2023-12-05 18:07:46

I just installed v. 0.4.2.1 and still both defects exist:
- can't use settings because the window does not fit on the screen and can't be properly shinked

I had no intention to do anything about it. Your use case is an edge case. I already spent too much time on the UI.

Quote from: wojak on 2023-12-05 18:07:46

- frequencies/notes displayed on the bars are improper

No, they are not. They are displayed as intended.

Yes, but it's new territory for me. I'll have to study it first because the example on it's website does not compile.

The tooltip has nothing to do with the X-axis. It shows the center frequency and, when appropriate, the note name of the bin. The X-axis is an approximation anyway. So the driving factor is the specification in the Frequencies part of the configuration.

When you specify a freq. range e.g. between 20Hz and 96kHz, the last bin will show 96kHz no matter what X-axis setting you set.

Confirmed. It's a high-DPI thing again. I'm getting pretty fed-up with this mess. DirectX is supposed to be resolution independent. But somewhere in the mapping of the mouse coordinates something goes wrong...

Quote from: pqyt on 2023-12-06 11:14:08

Confirmed. It's a high-DPI thing again. I'm getting pretty fed-up with this mess. DirectX is supposed to be resolution independent. But somewhere in the mapping of the mouse coordinates something goes wrong...

Thanks for confirming this.  I'm wondering what the code considers to be "high-DPI"--I am using a regular HDMI monitor with Windows set to 125% scale and the screen resolution at 1920 X 1080.  Your efforts have been and are appreciated and I'm more than willing to accept your work at whatever stage you are satisfied with.  It's a beautiful and effective spectrum.

I think a more distinctive name is required to seperate it from the stock CUI visualisation...

It's easy for me to tell because I know musicmusic uses British English spelling like I do. Not so easy for others. :P

v0.5.0.0, 2023-12-08

* New: Columns UI support.
* Fixed: Tooltips display at the correct position on installations scaled higher than 100%.

You can download it from the Components (https://www.foobar2000.org/components/view/foo_vis_spectrum_analyzer) repository or upgrade from within foobar2000.

Thanks to @musicmusic for helping me with the release bug.

v0.5.0.0 Frequency range configuration.
There appears to be a problem with the storage of the Frequency range.
After specifying 20.00 to 96000.00 in the settings (image 1) and once exiting Foobar 2.1 Preview, the saved settings are 96000.00 to 20000.00 (image 2).
In v0.4.2.1, the settings were saved successfully. The same was also true after initialisation by clicking the Reset button.

Yup. Copy/Paste error. The low frequency is read twice from the CUI configuration. I'll release a hot fix.

Quote from: brichanfiana on 2023-12-08 20:50:10

v0.5.0.0 Frequency range configuration.
There appears to be a problem with the storage of the Frequency range.
After specifying 20.00 to 96000.00 in the settings (image 1) and once exiting Foobar 2.1 Preview, the saved settings are 96000.00 to 20000.00 (image 2).
In v0.4.2.1, the settings were saved successfully. The same was also true after initialisation by clicking the Reset button.

Yup. Copy/Paste error. The low frequency is read twice from the CUI configuration. I'll release a hot fix.

I just noticed that the 32-bit version of the plugin is not useable with Foobar 1.6.17--when attempting to install, Foobar produces a "failed to load DLL, not compatible with this version of the Foobar SDK" message.  Any chance of making it backward compatible with the older SDK?

Quote from: sveakul on 2023-12-09 22:39:09

I just noticed that the 32-bit version of the plugin is not useable with Foobar 1.6.17--when attempting to install, Foobar produces a "failed to load DLL, not compatible with this version of the Foobar SDK" message.  Any chance of making it backward compatible with the older SDK?

You'll have to ask Peter to back-port the API's. The message is generated by foobar2000 itself.

Quote from: sveakul on 2023-12-09 22:39:09

I just noticed that the 32-bit version of the plugin is not useable with Foobar 1.6.17--when attempting to install, Foobar produces a "failed to load DLL, not compatible with this version of the Foobar SDK" message.  Any chance of making it backward compatible with the older SDK?

You'll have to ask Peter to back-port the API's. The message is generated by foobar2000 itself.

Quote from: pqyt on 2023-12-10 00:22:46

Quote from: sveakul on 2023-12-09 22:39:09

I just noticed that the 32-bit version of the plugin is not useable with Foobar 1.6.17--when attempting to install, Foobar produces a "failed to load DLL, not compatible with this version of the Foobar SDK" message.  Any chance of making it backward compatible with the older SDK?

You'll have to ask Peter to back-port the API's. The message is generated by foobar2000 itself.

I just compiled your latest sources with the latest SDK with FOOBAR2000_TARGET_VERSION at 80, which is the default, and the component works fine even on foobar2000 v1.5.

Are you perhaps using the foobar2000 SDK 2023-09-06? It had a bug in its version defines and it defaulted to require foobar2000 v2.0. It was fixable by editing the version defines and a fixed version was uploaded a week later.

I have been using this extension for a few hours and love it and see no obvious problems.  :)

My only two requests are (1) to have a way to color notes black and white just like on a piano keyboard, so the identities of the notes can more easily be recognized at a glance. (I like using it to see what notes singers are actually hitting.)

And (2) to have 30 Hz as a "refresh rate limit" option, (but this is really quite minor, and in the meantime I can just use 20Hz or 60Hz and hardly even see the difference).

pqyt: does this version use the fixed SDK mentioned here (https://hydrogenaud.io/index.php/topic,125031.msg1036213.html#msg1036213) so that is now compatible with Foobar 1.6.17 as well?

v0.5.1.0, 2023-12-14

* New: Support for DUI and CUI default user interface colors.
* New: LED mode.
* New: The color scheme can be used as a horizontal gradient.
* New: The color for the background of white and black 'keys' can be selected separately.
* New: Galss window function.
* Improved: Rendering occurs on a separate thread resulting in smoother animation.
* Improved: Re-designed configuration dialog to fit on installations scaled higher than 100%.
* Fixed: Some settings were reset when the configuration dialog re-opened during the same session.
* Fixed: Scaling method was available when other than Linear distribution was selected.
* Fixed: Bug in Median, RMS and RMS Sum summation method.

You can download it from the Components (https://www.foobar2000.org/components/view/foo_vis_spectrum_analyzer) repository or upgrade from within foobar2000.

One small request: Since we can set freqs form ex. 1Hz to 96kHz (probably even more), it would be great if the x-axis labels (being notes) would reflect that. Now the forst labels is C0 and last is C10 (or 11). Could you please add labels below and above it (C_1 (or C-1)...and so on)?

Quote from: wojak on 2023-12-16 08:50:46

One small request: Since we can set freqs form ex. 1Hz to 96kHz (probably even more), it would be great if the x-axis labels (being notes) would reflect that. Now the forst labels is C0 and last is C10 (or 11). Could you please add labels below and above it (C_1 (or C-1)...and so on)?

Why? Simply for display purposes? Anything above 20kHz is not audible. It does not make sense to assign a 'note' letter to it.

Quote from: sveakul on 2023-12-14 21:20:04

pqyt: does this version use the fixed SDK mentioned here (https://hydrogenaud.io/index.php/topic,125031.msg1036213.html#msg1036213) so that is now compatible with Foobar 1.6.17 as well?

Answering my own question, YES!  Thank you pqyt!  Fully compatible and looking as great with Foobar 1.6.17 32-bit as it does with my 64-bit Foobar v2.1.

Quote from: sveakul on 2023-12-14 23:04:10

Quote from: sveakul on 2023-12-14 21:20:04

pqyt: does this version use the fixed SDK mentioned here (https://hydrogenaud.io/index.php/topic,125031.msg1036213.html#msg1036213) so that is now compatible with Foobar 1.6.17 as well?

Answering my own question, YES!  Thank you pqyt!  Fully compatible and looking as great with Foobar 1.6.17 32-bit as it does with my 64-bit Foobar v2.1.

This component seems to break foobar2000 compatibility with Windows 7 and 8.1. Because I'm getting this error message on Windows 7 and 8.1:
Failed to load DLL: foo_vis_spectrum_analyzer.dll
Reason: The specified procedure could not be found

Searching with an hex editor, I can see some reference to atlthunk.dll but this DLL is available only on Windows 10 or above :(

I'm having difficulty adding the component to an existing 64-bit CUI theme; foobar crashes. I can add it to a fresh install, but I'm reluctant to rebuild the theme around it there.

I haven't had any trouble with previous 32-bit CUI and 64-bit DUI installations.

Quote from: Sue Dunham on 2023-12-15 21:48:26

I'm having difficulty adding the component to an existing 64-bit CUI theme; foobar crashes. I can add it to a fresh install, but I'm reluctant to rebuild the theme around it there.

I haven't had any trouble with previous 32-bit CUI and 64-bit DUI installations.

I found a workaround for this that may shed a little light. The sticking point in 64-bit CUI seemed to be adding one of these to the layout and removing the CUI-stock Spectrum analyzer in the same operation. I could add this component, press OK, restart fb2k, and then remove the other spectrum successfully.

To reproduce the crash: Add Tab Stack in CUI layout, add panel Spectrum Analyzer in Tab Stack. Crash.

-it should not be using size_t anywhere. This obviously differs depending on 32bit/64bit meaning config files are not portable.

- Be able to flip the visualition on both axis.

- Stereo and/or surround imaging.

Another thing: be able to import settings from Channel Spectrum panel and replicate as best as possible would be sweet as well but not obligatory.

Glitch: Spectrum Analyzer DUI/CUI panel, Configure, OK, no tooltip in Spectrum Analyzer panel

To reproduce the crash: Add Tab Stack in CUI layout, add panel Spectrum Analyzer in Tab Stack. Crash.

I'm trying to match my 64-bit settings to my 32-bit ones, and there's a difference in the color blending that I can't account for. The 32-bit is on the left, and the top (pink) end seems to be favored with the darkest blue having a narrower band.

The 32-bit came first when I was still figuring out how to work with the colors, so it did involve more trial and error, while the 64-bit one was done more quickly and directly. But all the settings I can see seem to be matched.

The component doesn't work on anything older than Windows 10 because it calls GetDpiForWindow (https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-getdpiforwindow) function, which was introduced in Windows 10. If the function is necessary to get over all the DPI issues people have suffered one simple solution would be to only use it on Win10 or newer.

I noticed the visualization element is created with default bright background causing it to flash rather nastily on start before rendering its correct colors.

There may be something wrong with the fancy up/down arrows next to numeric values. With default config for example hitting the up arrow next to Pitch increases the value from 440.00 to 440.50. Then hitting down arrow changes the value to 44.50.

As it happens, I like it better this way; please don't fix it too quickly and restrictively.  ;D

typedef UINT (WINAPI *GetDpiForWindow_t)(_In_ HWND hwnd);
GetDpiForWindow_t GetDpiForWindow_w10 = NULL;

static BOOL initGetDpiForWindow_w10()
{
    HMODULE handle;
    if ((handle = LoadLibraryA("user32.dll")) != NULL) {
        GetDpiForWindow_w10 = (GetDpiForWindow_t)GetProcAddress(handle, "GetDpiForWindow");
    }
    if (!GetDpiForWindow_w10) {
        if (handle) FreeLibrary(handle);
    }
    return (GetDpiForWindow_w10 != NULL);
}

static BOOL initGetDpi()
{
    static BOOL success = initGetDpiForWindow_w10();
    return success;
}

HRESULT DirectX::GetDPI(HWND hWnd, UINT & dpi) const
{
    if (initGetDpi())
        dpi = ::GetDpiForWindow_w10(hWnd);
    else
    {
        FLOAT DPIX, DPIY;

        #pragma warning(disable: 4996)
        _Direct2D->GetDesktopDpi(&DPIX, &DPIY);
        #pragma warning(default: 4996)

        dpi = (UINT) DPIX;
    }

    return S_OK;
}

The 0.6.0.0 release doesn't work on anything older than Windows 10 still, because you directly reference the function that causes problems. The compiler links the function stubs in and things break.

Here's a replacement that allows the function to be used on any OS where it's present and not cause problems on stock Win7:

Code: [Select]

typedef UINT (WINAPI *GetDpiForWindow_t)(_In_ HWND hwnd);
GetDpiForWindow_t GetDpiForWindow_w10 = NULL;

static BOOL initGetDpiForWindow_w10()
{
    HMODULE handle;
    if ((handle = LoadLibraryA("user32.dll")) != NULL) {
        GetDpiForWindow_w10 = (GetDpiForWindow_t)GetProcAddress(handle, "GetDpiForWindow");
    }
    if (!GetDpiForWindow_w10) {
        if (handle) FreeLibrary(handle);
    }
    return (GetDpiForWindow_w10 != NULL);
}

static BOOL initGetDpi()
{
    static BOOL success = initGetDpiForWindow_w10();
    return success;
}

HRESULT DirectX::GetDPI(HWND hWnd, UINT & dpi) const
{
    if (initGetDpi())
        dpi = ::GetDpiForWindow_w10(hWnd);
    else
    {
        FLOAT DPIX, DPIY;

        #pragma warning(disable: 4996)
        _Direct2D->GetDesktopDpi(&DPIX, &DPIY);
        #pragma warning(default: 4996)

        dpi = (UINT) DPIX;
    }

    return S_OK;
}

Quote from: Case on 2024-01-01 09:10:59

The 0.6.0.0 release doesn't work on anything older than Windows 10 still, because you directly reference the function that causes problems. The compiler links the function stubs in and things break.
Here's a replacement that allows the function to be used on any OS where it's present and not cause problems on stock Win7

Hmmm, what was I thinking... you're right. I'll release a hot-fix.
EDIT: v0.6.0.1 should fix the fix...

I updated directly from 0600 to 0602, and immediately noticed different frequency bar spectrum behavior, "frantic" jerky up-and-down movement throughout the frequency range.  I had been using a 60Hz refresh rate and both smoothing options off, which gave me IMO perfect real-time looking but controlled bar behavior.  Backing the rate down to 20Hz fixed it "mostly" but still with a lack of overall smoothness that led me to roll back to 0600.  I assume this was due to the 0602 fix described as "Finally found a (the?) correct way to use the sample window duration of foobar2000"--are you sure this change was effective/necessary?  I am using Foobar 2.1 x64 and 1.6.17 with Windows 10 x64 22H2.

The CUI panel Full-Screen Mode doesn't work.

What FFT size are you using?

Quote from: pqyt on 2024-01-02 20:13:01

What FFT size are you using?

16384

The last two 64-bit component releases claim to be version 0.6.0.0. 32-bit dlls have the right version info.

foo_vis_spectrum_analyzer 0.6.0.0
Copyright (c) 2023 P. Stuer. All rights reserved.

A spectrum analyzer for foobar2000
Based on the Audio Spectrum project (https://codepen.io/TF3RDL/pen/poQJwRW)

Built with foobar2000 SDK 20230923
on Dec 31 2023 16:55:48.

Quote from: Case on 2024-01-02 20:36:40

The last two 64-bit component releases claim to be version 0.6.0.0. 32-bit dlls have the right version info.

Huh?

Quote from: pqyt on 2024-01-02 21:07:13

Quote from: Case on 2024-01-02 20:36:40

The last two 64-bit component releases claim to be version 0.6.0.0. 32-bit dlls have the right version info.

Huh?

He means that the 0602 release shows up in the Foobar 2.1 x64 component list as 0600 (confirmed).  The dll itself is correctly tagged as 0602.

Quote from: grimes on 2024-01-02 21:49:11

Download 0.6.0.2:

Quote

foo_vis_spectrum_analyzer 0.6.0.0
Copyright (c) 2023 P. Stuer. All rights reserved.

A spectrum analyzer for foobar2000
Based on the Audio Spectrum project (https://codepen.io/TF3RDL/pen/poQJwRW)

Built with foobar2000 SDK 20230923
on Dec 31 2023 16:55:48.

Something else must be wrong. All version information derive from 1 set of defines. Are you sure the DLL is replaced in your foobar2000 profile? Both 32 and 64-bits show up correctly on 3 different system here.

€
           À      Fè€
   €Q €
   €S €
   €\ €
   p\ €
   À€
   PP €
   @P €
   p €
   °p €
   àp €
   ðq €
   ¨Ù,âÜŸí C Uù¸€
   œa €
   @P €
   p €
   °p €
   ðW €
    \ €
   G"PoZF’E‹ý;`8€
   Ðv €
   Spectrum Analyzer       foo_vis_spectrum_analyzer.dll   foo_vis_spectrum_analyzer 0.6.0.0
Copyright (c) 2023 P. Stuer. All rights reserved.

A spectrum analyzer for foobar2000
Based on the Audio Spectrum project (https://codepen.io/TF3RDL/pen/poQJwRW)

Built with foobar2000 SDK 20230923
on Dec 31 2023 16:55:48.        0.6.0.0 forced cast failure     À$€
   }¦€
   }¦€
   }¦€
   }¦€
   €#€
   𸠀
   𸠀
    ¹ €
   0¸ €
   p\ €
   h €
   𸠀
   𸠀
   `» €
    · €
   з €
   ð· €
   ¸ €
   ˜&€
   @¸ €
   è'€
   €¹ €
   (€
   °º €
   ¨'€
   𸠀
   𸠀
   0º €
    · €
           ¼  ¾  Æ  È

v0.6.0.2, 2024-01-02
* Fixed: Frequency range specification when using notes.

Are you using 64 bit? It claims to be 0.6.0.0 instead of 0.6.0.2

Are you using 64 bit? It claims to be 0.6.0.0 instead of 0.6.0.2

Something else must be wrong. All version information derive from 1 set of defines. Are you sure the DLL is replaced in your foobar2000 profile? Both 32 and 64-bits show up correctly on 3 different system here.

Quote from: grimes on 2024-01-03 15:29:39

Are you using 64 bit? It claims to be 0.6.0.0 instead of 0.6.0.2

Can you try unzipping the package and copying the 64-bit DLL manually to your profile, please?

@pqyt - just open the Components page in Preferences and see the version info and about page. The component says it's 0.6.0.0. Only the resource manifest speaks about 0.6.0.2.

And before I reported it to you I had verified that the same bug affects both the binary on component repository and on github.

And it's not a bug in sources as my compile correctly reports 0.6.0.2.

Edit: though I tweak your solution settings to suit my structure and I skip your complex powershell archiving script. I haven't tried to understand what it does.

@pqyt - just open the Components page in Preferences and see the version info and about page. The component says it's 0.6.0.0. Only the resource manifest speaks about 0.6.0.2.

And before I reported it to you I had verified that the same bug affects both the binary on component repository and on github.

And it's not a bug in sources as my compile correctly reports 0.6.0.2.

Edit: though I tweak your solution settings to suit my structure and I skip your complex powershell archiving script. I haven't tried to understand what it does.

And, please add left and right reversed setting to x-axis
 for displaying left and right channel side by side.

The sample window duration is now optimized for FFT 4096. There is a relation between the window duration and the FFT size but I haven't found it yet. Higher FFT sizes will indeed show a lot of jitter now for 'pure' signals but music tracks should be fine.

Had another look at this, it's getting there, well done with all the hard work.

In order to fully replace Musical Spectrum for me, it'll need the ability to turn off all axis text and lines, so just the main graphic display with no text etc. For full screen I like the axes and text, but when it's smaller as part of a main layout I like to just see the graphics. Forgive me if this is already implemented and I missed it!

Quote from: darkflame23 on 2024-01-04 14:37:43

Had another look at this, it's getting there, well done with all the hard work.

In order to fully replace Musical Spectrum for me, it'll need the ability to turn off all axis text and lines, so just the main graphic display with no text etc. For full screen I like the axes and text, but when it's smaller as part of a main layout I like to just see the graphics. Forgive me if this is already implemented and I missed it!

Set the X axis and Y axis to mode "None". Is that what you were looking for?

Request: Spectrum Analyzer Configuration window in dark mode.

A slope control would be nice. I usually have my frequency analysers (SPAN or Prism) set to 3, 4.5 or 6dB slope towards the highs to read "flatter".

Quote from: darkflame23 on 2024-01-06 15:49:18

A slope control would be nice. I usually have my frequency analysers (SPAN or Prism) set to 3, 4.5 or 6dB slope towards the highs to read "flatter".

Do you have any documentation or articles I can read because I don't understand what you're asking?

Quote from: pqyt on 2024-01-07 17:10:06

Quote from: darkflame23 on 2024-01-06 15:49:18

A slope control would be nice. I usually have my frequency analysers (SPAN or Prism) set to 3, 4.5 or 6dB slope towards the highs to read "flatter".

Do you have any documentation or articles I can read because I don't understand what you're asking?

A standard analyser with no slope/weighting will make White Noise look "flat", but most musical program signals follow something closer to a Pink Noise spectrum (a 3dB per octave roll off) or even more. Music on standard analysers will always show more level in the bass than looks natural. More advanced analysers will have a dB slope control where you can adjust it to your liking. I'd highly recommend downloading Voxengo SPAN and TDR Prism (both free plugins), having a play, and reading their manuals to understand it a bit better. Prism is state of the art (I was on the beta team).

https://www.voxengo.com/product/span/

https://www.tokyodawn.net/tdr-prism/

Quote from: pqyt on 2024-01-07 17:10:06

Quote from: darkflame23 on 2024-01-06 15:49:18

A slope control would be nice. I usually have my frequency analysers (SPAN or Prism) set to 3, 4.5 or 6dB slope towards the highs to read "flatter".

Do you have any documentation or articles I can read because I don't understand what you're asking?

A standard analyser with no slope/weighting will make White Noise look "flat", but most musical program signals follow something closer to a Pink Noise spectrum (a 3dB per octave roll off) or even more. Music on standard analysers will always show more level in the bass than looks natural. More advanced analysers will have a dB slope control where you can adjust it to your liking. I'd highly recommend downloading Voxengo SPAN and TDR Prism (both free plugins), having a play, and reading their manuals to understand it a bit better. Prism is state of the art (I was on the beta team).

https://www.voxengo.com/product/span/

https://www.tokyodawn.net/tdr-prism/

The Prism manual explains it really well:

https://docs.tokyodawn.net/tdr-prism-manual/#Analyzer_Weighting

Glitch: Play -> Pause -> Stop. Spectrum Analyzer is not resettet.

I saw it in waveform minibar (mod): Tooltip on_mouse_lbtn_down. The on_mouse_move tooltip is a little bit annoying and is buggy. Thanks for patience.

I have installed the updated build and it's now showing as version 0.6.0.2 in the components list, but the A4@117.90 Hz and B7@440 Hz issue is still there :(

Which settings are you using?

Are you using high DPI settings?

Hi, I'm having 2 issues with your plugin :
- Using it in fb2k x64 crashes, so I revert back to x32 and it works. I see that your changelog on 0.6 have the mention of "Fixed: Crash when adding multiple instances to CUI (Columns User Interface) layouts." Maybe with this fix it could be fix my setup but I need to retry later the installation of the x64 fb2k.

- When I double click on the panel to show me in fullscreen, the screen remains black and nothing appears but if I right click I see that's the panel because it shows me the context menu. Has it been reported by other people ?

How can I make the background transparent?
In settings you can specify background color which works fine and also set alpha which does nothing which confuses me.

How can I set foo_vis_spectrum_analyzer to the same pseudo behavior as the old foo_ui_vis_channel_spectrum?

Quote from: Defender on 2024-01-12 10:19:58

How can I make the background transparent?
In settings you can specify background color which works fine and also set alpha which does nothing which confuses me.

The background color is transparent but the panel itself is not a layered window. What's behind the panel?

Quote from: Defender on 2024-01-12 10:19:58

How can I set foo_vis_spectrum_analyzer to the same pseudo behavior as the old foo_ui_vis_channel_spectrum?

Define 'pseudo behavior'

Quote from: pqyt on 2024-01-12 22:44:15

Quote from: Defender on 2024-01-12 10:19:58

How can I make the background transparent?
In settings you can specify background color which works fine and also set alpha which does nothing which confuses me.

The background color is transparent but the panel itself is not a layered window. What's behind the panel?

Quote from: Defender on 2024-01-12 10:19:58

How can I set foo_vis_spectrum_analyzer to the same pseudo behavior as the old foo_ui_vis_channel_spectrum?

Define 'pseudo behavior'

Plugins like yours live in a CUI PSS panel in my skin, which has pseudo transparancy enabled. In the PSS code for that particular splitter I paint the background with a gradient and display the art I want to see. Per plugin I can choose between whether I want to display from a selection of two different bandlogo's, recordlabelogo, artistcountryflag, albumcover or a selection of artistpics. After the background and art are displayed I activate the plugin.
Some old plugins (Waveseekbar, VU Meter and Peakmeter do not support pseudo transparancy). Other old plugins do support pseudo like ELP, ESP, Channel Spectrum, Lyrics3 and all WSH scripts. Almost all modern plugins do support pseudo transparency. For instance all Will-B scripts do (spidermonkey) and YT. JS3 doesn't support pseudo out of the box but it's quite easy to disable one line of code (where it paints the background of it's location) which will activate pseudo. Unfortunately that has to be done everytime a new version pops up.

So, although I'm quite happy with the way the old Channel Spectrum looks operating in pseudomode it's not supported anymore. Therefore I wanted to give your new plugin a shot now it's seems to be stable. I also saw you are working on implementing painting art yourself in your plugin. I prefer to do that myself, but need pseudo support (eg the plugin has an option not to display background).

I haven't spent any time with Columns UI so 'pseudo transparency' is new to me. And frankly, it sounds a bit weird. Either something is transparent, supports alpha blending or is opaque, nothing pseudo about it. From your explanation could it be that when you talk about 'scripts' that they just render to an existing window while 'old' plugins and mine create their own (child) window and have to rely on the Windows transparency rules? I'll have to revisit old code of mine because I gave up on window transparency when Microsoft changed their mind and implementation rules with every new Windows version since XP.

		uie::container_window_v3_config get_window_config() final
		{
			return { L"jsp_class_cui_toolbar", true, CS_DBLCLKS };
		}

Quote from: pqyt on 2024-01-10 10:32:05

Which settings are you using?

Quote from: pqyt on 2024-01-10 10:32:05

Are you using high DPI settings?

No. Default 100%.
MOD edit: modify attachment links

I see what's wrong. I forgot to take non-standard Bands per Octave values into account. Fixed in the next version.

Quote from: Brazil2 on 2024-01-10 21:56:30

Quote from: pqyt on 2024-01-10 10:32:05

Which settings are you using?

Quote from: pqyt on 2024-01-10 10:32:05

Are you using high DPI settings?

No. Default 100%.
MOD edit: modify attachment links

@Brazil2, thx. I see what's wrong. I forgot to take non-standard Bands per Octave values into account. Fixed in the next version.

Is there a way to customize the following:

1. set a distinct color just for the line (curve)?
2. set a distinct color just for the peaks (bars)?
3. set bars thickness?

You're grossly over-simplifying what it takes. You don't just avoid drawing a background colour and have the parent auto-magically shine through.

There is a one line helper in the CUI SDK which makes it easy enough for GDI users because it takes an HDC arg...

https://github.com/reupen/columns_ui-sdk/blob/fddba5e0f6fade23785fe03af75a027d70802721/win32_helpers.h#L79

I can also use it in JSP3 because I'm using a D2D1 DC render target. Might be more work for this component because I searched and found it uses HWND render targets.

edit: almost forgot, my CUI get_window_config has the 2nd arg set to true like this...

Code: [Select]

		uie::container_window_v3_config get_window_config() final
		{
			return { L"jsp_class_cui_toolbar", true, CS_DBLCLKS };
		}

v0.6.0.3, 2024-01-13
* Fixed: Wrong note names in the tooltip when using a non-default number of bands per octave.

Quote from: marc2k3 on 2024-01-13 11:00:43

You're grossly over-simplifying what it takes. You don't just avoid drawing a background colour and have the parent auto-magically shine through.

There is a one line helper in the CUI SDK which makes it easy enough for GDI users because it takes an HDC arg...

https://github.com/reupen/columns_ui-sdk/blob/fddba5e0f6fade23785fe03af75a027d70802721/win32_helpers.h#L79

I can also use it in JSP3 because I'm using a D2D1 DC render target. Might be more work for this component because I searched and found it uses HWND render targets.

edit: almost forgot, my CUI get_window_config has the 2nd arg set to true like this...

Code: [Select]

		uie::container_window_v3_config get_window_config() final
		{
			return { L"jsp_class_cui_toolbar", true, CS_DBLCLKS };
		}

It seems to be possible with a custom swap chain. I don't say no but not now. I want to finished some other features I'm working on.

It seems, you have the bars mode. So you have to untick bar background

Quote from: pqyt on 2024-01-13 17:15:42

v0.6.0.3, 2024-01-13
* Fixed: Wrong note names in the tooltip when using a non-default number of bands per octave.

Thanks!
Much better, but look at the screenshots.

20 bands per octave? An octave has 12 semitones. Are you fan of microtonal music?

In microtonal music the unit is Cent. An octave is 1200 Cent. Each semitone is +100  Cent, quartertone is +50 Cent. In your case of 20 tones per octave, this should be labeled +60 Cent per tone.

Quote from: grimes on 2024-01-13 21:44:55

20 bands per octave? An octave has 12 semitones. Are you fan of microtonal music?

In microtonal music the unit is Cent. An octave is 1200 Cent. Each semitone is +100  Cent, quartertone is +50 Cent. In your case of 20 tones per octave, this should be labeled +60 Cent per tone.

I don't mind adding that sub-unit but... I hope everybody understands we're using an audio player not a science experiment ;-)

* Improved: The sample window size for the FFT is now calculated based on the sample rate and the FFT size.

20 bands per octave? An octave has 12 semitones.

In your case of 20 tones per octave, this should be labeled +60 Cent per tone.

This should also account for resampling DSPs (especially extreme ones like when the source material is at 48kHz sample rate and the resampling DSP's target rate is 8kHz), which obviously affects all visualizations since visualization stream API gathers data after all DSP effects right?

Quote from: Black Lotus 974 on 2024-01-11 17:28:48

- When I double click on the panel to show me in fullscreen, the screen remains black and nothing appears but if I right click I see that's the panel because it shows me the context menu. Has it been reported by other people ?

What settings are you using? Is a track playing? Do any of the axis appear? A completely black screen has never been reported.

I use the sample rate as reported by an audio chunk once they start coming in. Before that, it's a guestimate based on what the track reports in its metadata. For synthesized tracks the sample rate starts at 44100.

It seems to be possible with a custom swap chain.

HDC dc{};

// I use microsoft/wil, could be pfc from the fb2k SDK or whatever
wil::com_ptr_t<ID2D1GdiInteropRenderTarget> gdi;
if SUCCEEDED(render_target->QueryInterface(IID_PPV_ARGS(&gdi)))
{
	if SUCCEEDED(gdi->GetDC(D2D1_DC_INITIALIZE_MODE_COPY, &dc))
	{
		// do stuff with dc here
		gdi->ReleaseDC(nullptr);
	}
}

Quote from: pqyt on 2024-01-13 17:14:07

It seems to be possible with a custom swap chain.

Not sure if it would work for this but I need to use DrawThemeBackground in my own code and it's done like this...

a) adjusting your D2D1::RenderTargetProperties with D2D1_RENDER_TARGET_USAGE set to D2D1_RENDER_TARGET_USAGE_GDI_COMPATIBLE

b) a bit of code like

Code: [Select]

HDC dc{};

// I use microsoft/wil, could be pfc from the fb2k SDK or whatever
wil::com_ptr_t<ID2D1GdiInteropRenderTarget> gdi;
if SUCCEEDED(render_target->QueryInterface(IID_PPV_ARGS(&gdi)))
{
	if SUCCEEDED(gdi->GetDC(D2D1_DC_INITIALIZE_MODE_COPY, &dc))
	{
		// do stuff with dc here
		gdi->ReleaseDC(nullptr);
	}
}

Cool. I'll look out for it and maybe I can modernise mine. I'm generally too stupid to do much myself. :P

1. Shouldn't the configuration window be honoring the user selected dark/light mode?

  2A. Please consider adding the option to save multiple configurations. It would be nice to quickly switch between them.

  2B. Peak mode for curve type

Quote from: kenzzy on 2024-01-03 23:36:22

And, please add left and right reversed setting to x-axis
 for displaying left and right channel side by side.

Me too as I haven't (and someone else) able to find the channel spectrum visualization for Default UI that it is compatible with foobar2000 x64 v2.x

I've already have side-by-side channel visualization mode (Visualization type = separate) on my own Channel Spectrum panel remake on Web Audio API as a CodePen project (https://codepen.io/TF3RDL/pen/NWBYeaE) a long-time ago after realizing that there are people who wanting to see a 64-bit remake of foo_uie_vis_channel_spectrum, so I've added that to aforementioned CodePen project and renamed this project from "Overlayed channel spectrum + custom FFT" to just "Channel spectrum + custom FFT", and another FR: more frequency distribution mode as in the aforementioned CodePen project (which have similar behavior to Classic Spectrum Analyzer (vis_classic) plugin for Winamp as well as Channel Spectrum panel (foo_uie_vis_channel_spectrum) component for foobar2000 as I've realized that Channel Spectrum panel frequency scaling depends on the FFT size and actual number of bands rather than a true Mel scale)

BTW, I've noticed that my own Web Audio API visualizations especially ones involving simultaneous channel visualizations only react to the Front part of the surround sound, though the mono (one AnalyserNode that connected to the audio source before ChannelSplitterNode) visualization reacts to everything except LFE channels per specifications for the channelInterpretation="speakers" behavior when comes to downmixing (https://developer.mozilla.org/en-US/docs/Web/API/Web_Audio_API/Basic_concepts_behind_Web_Audio_API#audio_channels), which you can test it by putting a surround sound (or anything more than 2 channels) audio file into the visualizer

Hi,
I'd also like to have X-axis and Y-axis mirroring ;-)
thanks a lot for your work!

Quote from: pqyt on 2024-01-11 18:25:51

Quote from: Black Lotus 974 on 2024-01-11 17:28:48

- When I double click on the panel to show me in fullscreen, the screen remains black and nothing appears but if I right click I see that's the panel because it shows me the context menu. Has it been reported by other people ?

What settings are you using? Is a track playing? Do any of the axis appear? A completely black screen has never been reported.

Hi, this is the panel into my fb2k and when I double click on the panel. As you can see it seems I can do right click but nothing is showed. There is 2 windows : the fb2k window which shows me that spectrum is displayed in the thumb, and the plugin window which shows me a black screen.
I have a dual screen, is it supposed to be an issue for displaying in fullscreen ?
I made screenshots of the configuration

Minor cosmetic issue when visualization type is set to curve. When nothing is playing the top of the curve line appears on the very bottom of the analyzer (see image below). I think expected behavior would be that nothing is visible.

(https://i.imgur.com/oVEChik.png)

Quote from: Black Lotus 974 on 2024-01-14 18:59:09

Quote from: pqyt on 2024-01-11 18:25:51

Quote from: Black Lotus 974 on 2024-01-11 17:28:48

- When I double click on the panel to show me in fullscreen, the screen remains black and nothing appears but if I right click I see that's the panel because it shows me the context menu. Has it been reported by other people ?

What settings are you using? Is a track playing? Do any of the axis appear? A completely black screen has never been reported.

Hi, this is the panel into my fb2k and when I double click on the panel. As you can see it seems I can do right click but nothing is showed. There is 2 windows : the fb2k window which shows me that spectrum is displayed in the thumb, and the plugin window which shows me a black screen.
I have a dual screen, is it supposed to be an issue for displaying in fullscreen ?
I made screenshots of the configuration

Hi, does anybody have the same issue than me ?

Quote from: metal_termite on 2024-01-18 21:03:43

1. Shouldn't the configuration window be honoring the user selected dark/light mode?

Yes, but I ran into problems with the standard way of implementing this because the dialog is not a foobar2000 settings page. I'll go back to it later.

Quote from: metal_termite on 2024-01-18 21:03:43

  2B. Peak mode for curve type

Noted.

Quote from: pqyt on 2024-01-19 05:27:10

Quote from: metal_termite on 2024-01-18 21:03:43

1. Shouldn't the configuration window be honoring the user selected dark/light mode?

Yes, but I ran into problems with the standard way of implementing this because the dialog is not a foobar2000 settings page. I'll go back to it later.

Does it mean that the config window has to be rewritten from scratch?

I haven't investigated it yet. Driver issue? I regularly run fb2k with 3 screens without any problems.

You might have to handle more exotic ones manually.

Quote from: marc2k3 on 2024-01-20 12:10:50

You might have to handle more exotic ones manually.

And that is the case. It took 3 lines of code for this but one control needs more work...

My pr for foo_midi uses the same code used here.

Quote from: marc2k3 on 2024-01-20 14:22:32

Quote from: marc2k3 on 2024-01-20 12:10:50

You might have to handle more exotic ones manually.

And that is the case. It took 3 lines of code for this but one control needs more work...

My pr for foo_midi uses the same code used here.

I'll have a second look. Like I said, I ran into problems during initial development and I didn't wanted to waste time on it then.

and the Channels button.

Quote from: pqyt on 2024-01-20 17:21:29

and the Channels button.

Heh, I didn't even notice that. :P

I recently applied dark mode support to the colour picker and have an issue with the right hand slider where I can't style it. :/

Improved: The curve is no longer visible as a flat line if no track is playing.

v0.7.0.0-beta-1, 2024-01-21

* New: The cover art of the playing track can be used as background image.
  * Opacity can be specified.
  * The dominant color of the cover art can be used as a filler.
* New: The dominant colors of the cover art can be used to generate a gradient.
  * Color scheme "Artwork" turns on the feature.
  * Between 2 and 256 colors can be selected.
  * Lightness threshold determines which light colors will be ignored.
* New: The Curve visual has a peak line.
* New: Dark mode support.
* New: Fading AIMP peak mode, a combination of AIMP and Fade Out mode.
* Improved: Curve mode can use a horizontal gradient.
* Improved: The curve is no longer visible as a flat line if no track is playing.

You can download it only from GitHub (https://github.com/stuerp/foo_vis_spectrum_analyzer/releases/tag/v0.7.0.0-beta-1).

This beta release contains a couple of eye candy additions and requests. Bugs can be expected but it has been stable in everyday use.

Hopefully I can focus on some analysis features now.

Quote from: darkflame23 on 2024-01-07 18:47:11

Quote from: pqyt on 2024-01-07 17:10:06

Quote from: darkflame23 on 2024-01-06 15:49:18

A slope control would be nice. I usually have my frequency analysers (SPAN or Prism) set to 3, 4.5 or 6dB slope towards the highs to read "flatter".

Do you have any documentation or articles I can read because I don't understand what you're asking?

A standard analyser with no slope/weighting will make White Noise look "flat", but most musical program signals follow something closer to a Pink Noise spectrum (a 3dB per octave roll off) or even more. Music on standard analysers will always show more level in the bass than looks natural. More advanced analysers will have a dB slope control where you can adjust it to your liking. I'd highly recommend downloading Voxengo SPAN and TDR Prism (both free plugins), having a play, and reading their manuals to understand it a bit better. Prism is state of the art (I was on the beta team).

https://www.voxengo.com/product/span/

https://www.tokyodawn.net/tdr-prism/

The Prism manual explains it really well:

https://docs.tokyodawn.net/tdr-prism-manual/#Analyzer_Weighting

Also, I've already implemented the weighting functions, frequency tilting, and even ones derived from Winamp's Classic Spectrum Analyzer plugin here (https://codepen.io/TF3RDL/pen/poQJwRW)

Quote from: pqyt on 2024-01-21 16:05:57

v0.7.0.0-beta-1, 2024-01-21

* New: The cover art of the playing track can be used as background image.
  * Opacity can be specified.
  * The dominant color of the cover art can be used as a filler.
* New: The dominant colors of the cover art can be used to generate a gradient.
  * Color scheme "Artwork" turns on the feature.
  * Between 2 and 256 colors can be selected.
  * Lightness threshold determines which light colors will be ignored.
* New: The Curve visual has a peak line.
* New: Dark mode support.
* New: Fading AIMP peak mode, a combination of AIMP and Fade Out mode.
* Improved: Curve mode can use a horizontal gradient.
* Improved: The curve is no longer visible as a flat line if no track is playing.

You can download it only from GitHub (https://github.com/stuerp/foo_vis_spectrum_analyzer/releases/tag/v0.7.0.0-beta-1).

This beta release contains a couple of eye candy additions and requests. Bugs can be expected but it has been stable in everyday use.

Hopefully I can focus on some analysis features now.

Installed the beta.

Can you please direct me to what settings I should apply so that the plugin does not paint the background or has it not been implemented?

See attached screenshots for the things I tried (next to old channel spectrum) ...

It's not implemented yet even though there is a background mode None. I have working code for the desktop window. I still have to experiment with a child window before I add the code to the component.

Thank you @pqyt for the continued development😃

So if I wanted the peak to be a distinct color that was different from the bars or the curve, how would would I set up the graph? Is that possible?

I guess I'm not sure what the % value input means nor the smoothing dropdown.

Quote from: pqyt on 2024-01-21 18:54:30

It's not implemented yet even though there is a background mode None. I have working code for the desktop window. I still have to experiment with a child window before I add the code to the component.

One other thing ... As you can see I'll be sticking to curve mode. In curve mode there's always a vertical line on the left side in the same colour and width as the curve line itself. How can I get rid of that vertical line?

Another nice to have. Please add an extra Apply button in the Configuration that applies the changes you made in the configuration but keeps the Configuration panel open (until you click OK).

Thanks a lot for the new release.

Crash report: When the component is activated in a window, toggling full-screen mode on and off crashes the program.

Quote from: Defender on 2024-01-21 19:14:49

Another nice to have. Please add an extra Apply button in the Configuration that applies the changes you made in the configuration but keeps the Configuration panel open (until you click OK).

Erhh, why? All changes are live. "Cancel" returns to the previous configuration set. Every 1h of feature development requires 1.5h of UI development because of that.

Quote from: pqyt on 2024-01-21 19:27:29

Quote from: Defender on 2024-01-21 19:14:49

Another nice to have. Please add an extra Apply button in the Configuration that applies the changes you made in the configuration but keeps the Configuration panel open (until you click OK).

Erhh, why? All changes are live. "Cancel" returns to the previous configuration set. Every 1h of feature development requires 1.5h of UI development because of that.

Because it's nice to see what the changes you make in configuration panel do for the visualisation. If the thing you changed does not work for you, you can revert it without opening the configuration panel. Not that it is relevant but most plugins/addons I use have this functionality.

What is not clear about 'live'? Every change you make is immediately applied to the component, even while playing a track. So no, there will be no Apply button.

I have working code for the desktop window. I still have to experiment with a child window before I add the code to the component.

Quote from: MG240 on 2024-01-21 16:27:10

Crash report: When the component is activated in a window, toggling full-screen mode on and off crashes the program.

Fixed in the next release. Direct2D really wants the correct multi-threading settings...

Maybe a similar thing: when in Layout Editing Mode (DUI), trying to cut/copy the Spectrum Analyzer element and then paste it again into a splitter, also crashes foobar (v2.1.1 / 32-bit)

Quote from: anamorphic on 2024-01-22 16:12:28

Maybe a similar thing: when in Layout Editing Mode (DUI), trying to cut/copy the Spectrum Analyzer element and then paste it again into a splitter, also crashes foobar (v2.1.1 / 32-bit)

Crashes also in CUI.

Quote from: TF3RDL on 2024-01-08 00:29:55

Quote from: darkflame23 on 2024-01-07 18:47:11

Quote from: pqyt on 2024-01-07 17:10:06

Quote from: darkflame23 on 2024-01-06 15:49:18

A slope control would be nice. I usually have my frequency analysers (SPAN or Prism) set to 3, 4.5 or 6dB slope towards the highs to read "flatter".

Do you have any documentation or articles I can read because I don't understand what you're asking?

A standard analyser with no slope/weighting will make White Noise look "flat", but most musical program signals follow something closer to a Pink Noise spectrum (a 3dB per octave roll off) or even more. Music on standard analysers will always show more level in the bass than looks natural. More advanced analysers will have a dB slope control where you can adjust it to your liking. I'd highly recommend downloading Voxengo SPAN and TDR Prism (both free plugins), having a play, and reading their manuals to understand it a bit better. Prism is state of the art (I was on the beta team).

https://www.voxengo.com/product/span/

https://www.tokyodawn.net/tdr-prism/

The Prism manual explains it really well:

https://docs.tokyodawn.net/tdr-prism-manual/#Analyzer_Weighting

Also, I've already implemented the weighting functions, frequency tilting, and even ones derived from Winamp's Classic Spectrum Analyzer plugin here (https://codepen.io/TF3RDL/pen/poQJwRW)

Implemented in the next version.

Quote from: pqyt on 2024-01-21 18:54:30

I have working code for the desktop window. I still have to experiment with a child window before I add the code to the component.

I almost have it working. I didn't copy your code but used this article from the same guy in your composition repo readme.

https://learn.microsoft.com/en-us/archive/msdn-magazine/2014/july/windows-with-c-embracing-the-windows-composition-engine

It uses a IDCompositionSurface rather than a swap chain/bitmap. It was easy enough to get working in a "clean" fb2k window but my attempts at mangling it in to main project have failed so far due to my incompetence. I'll have a another go tonight. :P

Quote from: pqyt on 2024-01-21 16:05:57

v0.7.0.0-beta-1, 2024-01-21

* New: The cover art of the playing track can be used as background image.
  * Opacity can be specified.
  * The dominant color of the cover art can be used as a filler.
* New: The dominant colors of the cover art can be used to generate a gradient.
  * Color scheme "Artwork" turns on the feature.
  * Between 2 and 256 colors can be selected.
  * Lightness threshold determines which light colors will be ignored.
* New: The Curve visual has a peak line.
* New: Dark mode support.
* New: Fading AIMP peak mode, a combination of AIMP and Fade Out mode.
* Improved: Curve mode can use a horizontal gradient.
* Improved: The curve is no longer visible as a flat line if no track is playing.

You can download it only from GitHub (https://github.com/stuerp/foo_vis_spectrum_analyzer/releases/tag/v0.7.0.0-beta-1).

This beta release contains a couple of eye candy additions and requests. Bugs can be expected but it has been stable in everyday use.

Hopefully I can focus on some analysis features now.

Installed the beta.

Can you please direct me to what settings I should apply so that the plugin does not paint the background or has it not been implemented?

See attached screenshots for the things I tried (next to old channel spectrum) ...

@Defender ,

Done. Implemented in beta 3. I'll need a volunteer with a layered UI to confirm it works.

Quote from: pqyt on 2024-01-28 12:37:19

@Defender ,

Done. Implemented in beta 3. I'll need a volunteer with a layered UI to confirm it works.

Sure! Where can I get beta 3?

I like the plugin a lot, but unfortunately I went back to the previous version, the one without artwork management, because especially with radio and spin disc streaming I have scary slowdowns both in the graphic effects and in the rotation of the spin disc.

Spectrum Analyzer 0.6.0.3

(https://i.postimg.cc/3yhzL8Mq/Screenshot-2024-01-28-183757.png) (https://postimg.cc/3yhzL8Mq)

v0.7.0.0-beta-3, 2024-01-28

* New: Brown-Puckette constant Q transform.
* New: Background mode "None" does not draw a background resulting in transparent element.
* New: Full Screen mode for Columns UI.
* Improved: Bar width and peak indicator thickness get rounded to pixels for a more visually pleasing result.

You can download it only from GitHub (https://github.com/stuerp/foo_vis_spectrum_analyzer/releases/tag/v0.7.0.0-beta-3) for now.

(v0.7.0.0-beta-3): Resizing visualization window crashes the program.

Seems like I really need to try your method. Using that link I posted, I got as far as making transparency working on startup but it goes to poop after a resize.

edit: just to be clear to anyone else stumbling across this, transparency works fine in released versions of JSP3. This is just a failed experiment trying to use newer windows APIs. :P

Quote from: marc2k3 on 2024-01-29 11:39:04

Seems like I really need to try your method. Using that link I posted, I got as far as making transparency working on startup but it goes to poop after a resize.

edit: just to be clear to anyone else stumbling across this, transparency works fine in released versions of JSP3. This is just a failed experiment trying to use newer windows APIs. :P

I fixed the resize bug: multi-threading issue.

One remaining issue: when the parent window restores from a Minimized state the background transparency is lost. Recreating the buffer may fix it but I first have to find a way to get notified of the change in state. WM_SIZE is not sent to child windows after a restore because they did not change size.

I don't claim to be any soft of expert in GUI programming but the requested pseudo transparency effect is not something host is resposible for. If you add support for that invention, you are supposed to handle the background rendering of the element behind you.

v0.7.0.0-beta-3, 2024-01-28

Beta 4. Solid background applied (so no alpha background issues). No more foobar crashes so far.

(v0.7.0.0-beta-4)
Is it possible to fix this artifact on the right and bottom borders when resizing the component's window?

Quote from: Defender on 2024-01-29 22:06:11

Beta 4. Solid background applied (so no alpha background issues). No more foobar crashes so far.

I think I'm going back to the previous render code. There's too much going wrong and I don't have the setup to properly test the transparent background. It's not worth the effort at this point, IMHO.

Quote from: pqyt on 2024-01-30 05:24:53

Quote from: Defender on 2024-01-29 22:06:11

Beta 4. Solid background applied (so no alpha background issues). No more foobar crashes so far.

I think I'm going back to the previous render code. There's too much going wrong and I don't have the setup to properly test the transparent background. It's not worth the effort at this point, IMHO.

Too bad. It kinda looks cool when it's working. Only thing missing is a solid redraw response to de-minimizing.

Edit: I tried to find a workaround to enforce repaint but so far no success. I have no way of detecting that foobar is minimized or just restored from being minimized. Splitter code just halts all execution when being minimized. And there's not something like a time function I can set as a timer to detect gaps because of prior minimization. Only can use something based on a playing track but not on a paused track. So the alternative is to send a request for repaint every second, which looks like shit everywhere  else in the skin.

I've configured the refresh rate limit to 20 Hz or 60 Hz (my screen refresh rate) but the bars animation looks not so smooth. I wonder if it's possible to improve the up/down movements of the bars, maybe by synchronizing them with the display.

Thank you for your hard work on this plugin, so far the best one for foobar2000 v2 :)

I've configured the refresh rate limit to 20 Hz or 60 Hz (my screen refresh rate) but the bars animation looks not so smooth. I wonder if it's possible to improve the up/down movements of the bars, maybe by synchronizing them with the display.

I've found a super-smooth spectrum bars animation but it's in javascript, maybe you can find some ideas in it:
https://github.com/hvianna/audioMotion-analyzer/tree/master

Yeah, i noticed that too.

There was a change in v0.6.0.2, i believe it was:
Fixed: Finally found a (the?) correct way to use the sample window duration of foobar2000.

IMO, this resulted in a visual downgrade, it looked really smooth before that. It would be great having the option to use the old behavior.

Anyway, thanks for this amazing component.

Quote from: Xin-Hong on 2024-01-30 20:12:51

Thank you for your hard work on this plugin, so far the best one for foobar2000 v2 :)

I've configured the refresh rate limit to 20 Hz or 60 Hz (my screen refresh rate) but the bars animation looks not so smooth. I wonder if it's possible to improve the up/down movements of the bars, maybe by synchronizing them with the display.

I've found a super-smooth spectrum bars animation but it's in javascript, maybe you can find some ideas in it:
https://github.com/hvianna/audioMotion-analyzer/tree/master

Use Average mode smoothing. That normally makes the display less jumpy. The animation rate is high enough but the underlying result are what they are. Smoothing tempers the excess values.

Quote from: Xin-Hong on 2024-01-30 20:12:51

Thank you for your hard work on this plugin, so far the best one for foobar2000 v2 :)

I've configured the refresh rate limit to 20 Hz or 60 Hz (my screen refresh rate) but the bars animation looks not so smooth. I wonder if it's possible to improve the up/down movements of the bars, maybe by synchronizing them with the display.

I've found a super-smooth spectrum bars animation but it's in javascript, maybe you can find some ideas in it:
https://github.com/hvianna/audioMotion-analyzer/tree/master

Use Average mode smoothing. That normally makes the display less jumpy. The animation rate is high enough but the underlying result are what they are. Smoothing tempers the excess values.

Not tested but try this:

Download the latest stable version of the component and save it somewhere. Don't install it yet.

Browse your fb2k profile folder\user-components (append x64 if 64bit) and remove the foo_vis_spectrum_analyzer folder manually

Start fb2k and...

if using DUI, you should see blank spot in your layout where the component once was. fb2k will be clinging on to the old config should you restore the component which you don't want. So to wipe it, click in the blank space and add any other UI element. Now the bad config is gone and you can re-install the component and start again.

if using CUI, open File>Preferences>Display>Columns UI>Layout. One panel will be labelled <unknown>. Remove that and then re-install the component and start again.

v0.7.0.0-beta-4, 2024-01-29
* New: File path of the artwork can be specified as a file path or a title formatting script that returns a file path.

BTW, implementing something like analog-style analyzer (https://codepen.io/TF3RDL/pen/MWLzPoO) mode would require a different way of using get_chunk_absolute() from ones used by both FFT and current Goertzel-based CQT/VQT mode; the previous time is used as time offset and the requested chunk length is equals to a difference between current and previous time

// can also be used in Peak/RMS meters for accuracy (to not miss peaks especially with very low framerate like 10FPS) and consistency with VST analyzer plugins especially the RMS/VU meter
if (_VisualisationStream->get_chunk_absolute(Chunk, PrevPlaybackTime, PlaybackTime - PrevPlaybackTime)) {
  ProcessAudioChunk(Chunk);
}
PrevPlaybackTime = PlaybackTime; // where PrevPlaybackTime variable is initialized to 0 upon starting up the instance of it, starts the song, or upon seek, which all coefficients of sDFT and analog-style spectrum analyzer are reset to zero every time either of these happens

if (_VisualisationStream->get_chunk_absolute(Chunk, PlaybackTime - WindowSize * (ReactionAlignment/2.0+0.5), WindowSize)) {
  ProcessAudioChunk(Chunk)
}

My I ask for a feature ?
In some Spectrum Analyzers there is an option to center the spectrum (in foo_uie_vis_channel_spectrum for example). I guess it's something like that:

20 kHz --------------- 20 Hz ------------ 20 kHz
           LEFT Channel              RIGHT Channel

I don't see this option, is it possible to implement it ?

Also, I'm not alone with a feature request to add Channel Spectrum panel-esque visualization

v0.7.0.0-rc-1, 2024-02-07
[...]
* Fixed (Beta 4 regression): Removed the DirectComposition code that enabled transparent child windows. It was fun while it lasted.
[...]

Quote from: pqyt on 2024-02-07 18:06:05

v0.7.0.0-rc-1, 2024-02-07
[...]
* Fixed (Beta 4 regression): Removed the DirectComposition code that enabled transparent child windows. It was fun while it lasted.
[...].

Fixed (Beta 4 regression) ? No, just removed. So plugin now it looks quite ugly in my skin.

Still decided to test a bit. Returning from full screen 0.7.0.0-rc1 doesn't show the working plugin anymore. See video ...

Quote from: Defender on 2024-02-07 19:42:56

Still decided to test a bit. Returning from full screen 0.7.0.0-rc1 doesn't show the working plugin anymore. See video ...

Unable to reproduce: multiple and rapid switching between windowed and fullscreen mode works perfectly. DUI or CUI?

Quote from: pqyt on 2024-02-07 20:40:39

Quote from: Defender on 2024-02-07 19:42:56

Still decided to test a bit. Returning from full screen 0.7.0.0-rc1 doesn't show the working plugin anymore. See video ...

Unable to reproduce: multiple and rapid switching between windowed and fullscreen mode works perfectly. DUI or CUI?

CUI on fooBar 2.2 preview 2024-02-05 x86.

Issue is that even if you exit fooBar and restart fooBar the plugin is not working.

RC-1 does not work for me (foobar 2.2 preview with CUI). Frequent crashes of foobar when closing the settings dialog of RC-1, after closing foobar and restarting it I have a completely different look than I had set, or only the background is visible in the window... Reset to beta 4.

That's what you get when we developers have to implement boring stuff twice.

Quote from: pqyt on 2024-02-08 17:38:45

That's what you get when we developers have to implement boring stuff twice.

If you're talking about your read/write config overloads for DUI/CUI, you only have to implement one. There is no need for any duplication at all.

I'm not submitting a PR but look at these attached files for how a common config class with one get/set method can be used by CUI and DUI.

CUI user? I found a problem in reading the CUI settings. That's what you get when we developers have to implement boring stuff twice.

Small feature request: Show dB labels on the right side of the screen and even on both left and right sides of the screen, and also show frequency/Hz labels on the top of the screen like you could in original foo_musical_spectrum

Also, replace the Y-axis label setting drop-down menu with two checkbox buttons (one for setting the amplitude scale to dB instead of linear/nth root, another for Y-axis labels) as the option named "Logarithmic" is kinda misleading (it is actually linear/nth root amplitude scale) and there is currently no way to have a linear/nth root amplitude spectrum with dB labels on it to reflect what dB value of the magnitude would be at the point

See showcwt filter in FFmpeg, supports both spectrum and spectrogram display also many frequency scales: linear, log, mel, bark, erbs, etc (it can support any frequency scale actually), all with RDFT so its really fast, I tried sliding DFT approach with goertzel (in another filter implementation) but that one is much (unusable) slower with bigger frame-rate and video dimensions. My additional goal is to extend showcwt filter with synchrosqueezing transform - which give even better frequency vs time resolution.

Thanks pqyt, but could you please revise the Documentation page to cover/explain the myriad of new options in this version??  It's pretty intimidating.  Thanks!

Using a low custom value (0 or 1) in "No. of bins" crashes foobar.
v0.7.0.0.

Yeah, it's just to test the component. I use 8192.

BTW, while this demo (https://codepen.io/TF3RDL/pen/MWLzPoO) currently only supports logarithmic frequency scale, my implementation of VQ-sDFT, SWIFT, and analog-style analyzer actually fully supports arbitrary frequency scale (linear, Mel, Bark, ERB, and even exotic ones) as usual, which makes a lot of sense for niche users

I hate to be a nag but 0.7.0.0 creates its window with white background again. I'd assume it to be highly annoying for anyone trying to use a dark UI as a sudden white flash is blindingly bright.

I have noticed that when I change the value under "Frequencies - No. of Bands", the displayed frequencies on the X-axis shift up or down!
In my case, two test tones with 1000 and 2000 Hz are only displayed correctly on the X-axis with a value of "295". With other values, the test tones shift up or down significantly in some cases. (Version 0.7.0.0 RC-2/foobar mit CUI).

I noticed an odd bug with the new version when there are two color selection dialogs open. For instance, I have two spectrum analyzers in my layout, one for each channel, and I was trying to match the custom gradient from one to the other. If one cycles between them in the wrong order, then one of them will not function properly.

In my case, I needed to add colors to the two given by default. So I clicked "Add", which brings up a dialog. Then I double-clicked a color on the other analyzer's configuration page to open that dialog so I could copy the colors. However, on returning to the first dialog, I found that the tab button no longer worked to move from textbox to textbox, and the resulting color was not saved.

If, on the other hand, I opened that second, base, dialog first to get my source color and then clicked "Add" in the configuration I was editing, I could use everything as normal.

Also, replace the Y-axis label setting drop-down menu with two checkbox buttons (one for setting the amplitude scale to dB instead of linear/nth root, another for Y-axis labels) as the option named "Logarithmic" is kinda misleading (it is actually linear/nth root amplitude scale) and there is currently no way to have a linear/nth root amplitude spectrum with dB labels on it to reflect what dB value of the magnitude would be at the point

Quote from: TF3RDL on 2024-02-11 04:20:06

Also, replace the Y-axis label setting drop-down menu with two checkbox buttons (one for setting the amplitude scale to dB instead of linear/nth root, another for Y-axis labels) as the option named "Logarithmic" is kinda misleading (it is actually linear/nth root amplitude scale) and there is currently no way to have a linear/nth root amplitude spectrum with dB labels on it to reflect what dB value of the magnitude would be at the point

I don't understand. Checkboxes would mean that both options can be enabled. What is this going to achieve?

Thanks for all the work and quick progress @pqty

Maybe this is not a bug and I am just an idiot, but creating a layout with 3 ui elements of this visualizer kills the fps by quite a bit. The fps remains unaffected when I have two of these UI elements, but adding the third is when the performance drops off. I have mine set at 60fps, and adding a third instance causes the fps of all the ui elements to drop into the 10-20fps range.

Why does my layout have three? I have a visualizer tab, and three of those tabs are different schemas of foo_vis_spectrum_analyzer (curve layout, bar layout, etc). Only one of the instance can ever be visually active since they're in tabs, but I guess they're all active in the background? I just assumed if a tab wasn't active that the process was halted in the background.

v0.7.1.0-beta-1, 2024-02-14

* New: Sliding Windowed Infinite Fourier Transform (SWIFT).
* New: Reaction Alignment parameter allow you to control the delay between the actual playback and the visualization.

const bool IsSlidingWindow = _State._Transform == Transform::AnalogStyleAnalyzer || _State._Transform == Transform::SWIFT || _State._Transform == Transform::VQsDFT;
const double WindowSize = isSlidingWindow ? PlaybackTime - PrevPlaybackTime :  (double) _NumBins / (double) _SampleRate;
const double Offset = IsSlidingWindow ? PrevPlaybackTime : PlaybackTime - (WindowSize * (0.5 + _State._ReactionAlignment/2.0));

if (_VisualisationStream->get_chunk_absolute(Chunk, Offset, WindowSize))
  ProcessAudioChunk(Chunk);
PrevPlaybackTime = PlaybackTime;

* New: The X-axis can be displayed on top, below or on both sides of the spectrum.
* New: The Y-axis can be displayed on left, right or on both sides of the spectrum.
* New: Option to enable or disable the rendering of the mirror image of the spectrum (Anything above the Nyquist frequency). Default is disabled.
* Changed: Y-axis mode Logarithmic is now called Linear/n-th root.

* Fixed: Added some missing range checks in the configuration dialog that could lead to a crash.

Quote from: metal_termite on 2024-02-14 20:45:36

Thanks for all the work and quick progress @pqty

Maybe this is not a bug and I am just an idiot, but creating a layout with 3 ui elements of this visualizer kills the fps by quite a bit. The fps remains unaffected when I have two of these UI elements, but adding the third is when the performance drops off. I have mine set at 60fps, and adding a third instance causes the fps of all the ui elements to drop into the 10-20fps range.

Why does my layout have three? I have a visualizer tab, and three of those tabs are different schemas of foo_vis_spectrum_analyzer (curve layout, bar layout, etc). Only one of the instance can ever be visually active since they're in tabs, but I guess they're all active in the background? I just assumed if a tab wasn't active that the process was halted in the background.

There's logic in there that skips the rendering when it is hidden but the spectrum calculations continue with every frame. I'll look at a way to optimize it.

However, a correct one for both reaction alignment (as I've found by using Desmos graph like this (https://www.desmos.com/calculator/0xuclhlowd) and this (https://www.desmos.com/calculator/ozaublqxqt)) and any transforms that would require you to feed only new samples would be something like this:

IsWindowVisible works for tabs. No use for other windows that cover it though.

except for the division by 2: there's no need for it if the input parameter is adjusted accordingly.

Comparing a hobbyist giving away dozens/hundreds of hours of their own free time and expecting nothing in return isn't really comparable to the planned obsoloesnce employed by mega corps to get you to buy more.

@pqyt, I have come here 5 years before you, got no penalties, and post only when the topic worries me, not to waste time, traffic, or database records. Is that typical behavior of a troll? No. But labeling someone negatively as a troll just because their feedback is not about praise is very typical of an immature person. It is bad enough that the limited accessibility of your solution pet project casts a shadow on other freely made components and the player itself, there is no need to get personal. But if that is what you want, then I'd rather do it offline.

Sneak preview:

(https://github.com/stuerp/foo_vis_spectrum_analyzer/blob/vNext/Resources/Preview.png?raw=true)

@Brazil2, I confirm that this component does not work on Windows 7 x64.

Small suggestion for the preview picture:

1) Option to mirror the left channel (so frequency runs from high to low instead of the default low to high)
2) Option to disable the right side y-as display for left channel and the left side y-as display for right channel

Result something like the attached picture ...

component 0.7.1 on my Foobar2000 2.1 as well. But after calling it from the View/Visualizations menu, the player crashes.

Quote from: Kraeved on 2024-02-18 14:15:31

component 0.7.1 on my Foobar2000 2.1 as well. But after calling it from the View/Visualizations menu, the player crashes.

I'm now getting crashes as well with version 0.7.1.0 beta. It began with crashes on exit of foobar2000 and now it crashes at start, I can't run foobar2000 anymore. :( I've put back my profile backup and I'll stick with version 0.6.0.3 for now.

Does fb2k crash or does it hang?

Another sneak preview:

(https://github.com/stuerp/foo_vis_spectrum_analyzer/blob/vNext/Resources/Preview.png?raw=true)

edit: opening/closing the configure dialog or restarting fb2k sorts it out so I guess you create your brush on init and don't change.

* New: Multiple graphs.
  * Each graph can be configured to show the analysis of one or more channels.
  * A graph can be flipped horizontally or vertically.
  * Graphs can be stacked vertically or on a horizontal line.

Again, this version has seen a lot of abuse, probing and poking but is definitely not bug-free. Since your config will be converted upon first use, make sure you have a backup of your config.

1. Color source. What's the intended behavior of setting a Color Source to None? For example, Configure > Styles > Graph Description > Color source: None. I cannot discern a difference between Color Source None and Color Source Solid. I assumed it would hide the element, but it doesn't.

2. GPU usage. I've noticed the most recent beta registers more GPU usage (per Task Manager), about 7%. Even when playback is paused the usage fluctuates that high. No changes were made to the config from the prior version. My setup has two spectrum windows running simultaneously. Freezing one does cut the usage in half. Anyway, just thought this might be relevant to report since the usage seems to have doubled or more from the prior version.

Edit: Another thing I've noticed. When using only the stock vis components, if I minimize foobar2000, the GPU usage is reduced to 0%. When I add foo_vis_spectrum_analyzer components to my setup and minimize fb2k, the GPU usage remains active when minimizing the app. Perhaps setting them to automatically freeze/unfreeze when minimized/unminimized? Idk I'm not a dev 😅

3. Custom font size for styles that included text labels. Would this be a good idea? My implementation of your component is typically very narrow and long. The new graph labels appear quite large in comparison.

4. Full screen. Double-clicking the component for full screen mode doesn't display the component with the active setup; it renders the default layout with (I think) color scheme Prism 1.

5. If I've already requested this forgive me: Implementing profiles apart from color schemas that can be renamed, loaded, deleted, saved, and accessible across the various instances of the component. This would encompass saving all tweaks to the various settings.

Anyway, I've finally deleted all my other third-party spectrum components. This has become my daily driver spectrum analyzer. Well done, and thank you!
Edited: Supplied more feedback.

1) In the top/left corner I see "Stereo". If I delete it, it still shows a 'cursor'. Can that be removed?

2) In a future update is it possible to add a fill option for artwork? A lot of my artwork is small so the images have a window-boxed border. The fill option (like in ESLyrics for example) will take care of that.

Quote from: Majestyk on 2024-02-26 05:50:38

1) In the top/left corner I see "Stereo". If I delete it, it still shows a 'cursor'. Can that be removed?

Already fixed in the next release.

Quote from: Majestyk on 2024-02-26 05:50:38

2) In a future update is it possible to add a fill option for artwork? A lot of my artwork is small so the images have a window-boxed border. The fill option (like in ESLyrics for example) will take care of that.

Already implemented but not yet exposed to the GUI.

foobar 2000 2.1.2 preview 0219 with v0.7.0-rc-1 Spectrum not displayed or crashes.
Fourier Transform No. ofbins 32768 and 65536 ->Not Displayed. (PGGB-RT 352.8/384KHz Resampling）
Sample rate based -> Crash foobar 2000.

I can easily reproduce the crash on a clean instance and changing the bins to sample rate based. This is bog standard 44100 - nothing fancy like the post above.

Yeah, I see you got in 3 minutes before I posted. I was too slow.

Something else: flicker on resize - mind you, standard fb2k console and artwork panel are not good in that regard either. :D

What happens if you reset the component's configuration? I haven't had a crash for a while.

Edit: Confirmed for non-radix-2 FFT's. I'll issue a fix immediately. 32768 and 65536 should work.

Quote from: pqyt on 2024-02-27 10:58:34

What happens if you reset the component's configuration? I haven't had a crash for a while.

Edit: Confirmed for non-radix-2 FFT's. I'll issue a fix immediately. 32768 and 65536 should work.

It now works with RC-2, but I think that Spectrum is not working correctly when using the PGGB-RT Plugin in the part that was changed from 0.7.0.0 to 0.7.1.0.
32768 and 65536 did not work correctly on rc-1 when using the PGGB-RT.
After the PGGB-RT Plugin reads a source such as FLAC, it performs resampling in pre-processing, the source changes from FLAC to PGGB-RT, and the sample rate and bit depth are also changed.
I think that 0.7.0.0 took PGGB-RT information without problems with this operation, but 0.7.1.0 seems to make Spectrum based on information from the original FLAC source.

pic 1: Pre-Processing PGGB-RT (Original Flac 1.4.3 24/96KHz)
pic 2: Playing with PGGB-RT (32/384KHz)

Quote from: Majestyk on 2024-02-26 05:50:38

1) In the top/left corner I see "Stereo". If I delete it, it still shows a 'cursor'. Can that be removed?

Already fixed in the next release.

Quote from: Majestyk on 2024-02-26 05:50:38

2) In a future update is it possible to add a fill option for artwork? A lot of my artwork is small so the images have a window-boxed border. The fill option (like in ESLyrics for example) will take care of that.

Already implemented but not yet exposed to the GUI.

I can't imagine what I could have changed between those versions that would cause a different usage of the sample rate. The sample rate is taken from the audio chunk as supplied by fb2k, over and over again; I assume post-processing.
Before the first audio chunk arrives 44100Hz is assumed.

Maybe I'm doing something wrong (I haven't been using this long) but my style color is always reset when I reboot fb2k. For example if Bar Spectrum is set to Fire, when I reboot it's set to Prism 1.

Although if I go back to Styles after a reboot, and click on Bar Spectrum, it will say Fire and give me the Fire colors. It just won't give me those colors unless I manually click on Styles/Bar Spectrum after a reboot.

Quote from: pqyt on 2024-02-27 19:39:11

I can't imagine what I could have changed between those versions that would cause a different usage of the sample rate. The sample rate is taken from the audio chunk as supplied by fb2k, over and over again; I assume post-processing.
Before the first audio chunk arrives 44100Hz is assumed.

pic 1: This image shows the same song in 0.7.0.0 with foobar 2000 2.1.2 preview 0219 and the PGGB-RT plug-in in the same state.

The source is 384KHz, so the range up to 192KHz and up to the upper Spectrum analyzer limit setting of 96KHz is well displayed, but I thought the previous 0.7.1.0-rc2 did not display above 48KHz (up to 96KHz) (see previous See Pic 2 in post).
I have had similar symptoms since Beta1, but had repeatedly reverted back to 7.0.0.0, which is why I was late in reporting it.

pic 2 PGGB-RT file details dialogue
Unfortunately, the file information in PGGB-RT seems to bring the 24/96 Original Flac information.
If it is taken from Audio Chunk, it will be displayed in the same way as Spectrum in v0.7.0.0, regardless of the PGGB-RT information.
Furthermore, v0.7.1.0 only showed up to around 22KHz when playing 16/44KHz FLAC resampled to 32/352.8KHz on the PGGB-RT.

It would be best if I could read the source code directly and report back, but I am also a developer and I am traumatised to read and write source code because I am mentally beaten.

Sorry to add another report on v0.7.1.0 rc-2, but I have set the colour of the Spectrum Bar to Foobar 2000 Dark Mode, but after saving, I quit Foobar 2000 once, and after that, when I start Foobar 2000, the colour of the Spectrum Bar is displayed as Prism 1. The colour of the Spectrum Bar is displayed as Prism 1.
The colour of the Spectrum Bar is set to Prism 1, but in Configure it is set to Foobar 2000 Dark Mode, so as soon as the Bar Colour is selected, it reverts to the original colour.
However, when the Foobar 2000 is restarted again, the colour is Prism 1.

Config Reset has also been tried, but the same symptoms occur.

The source has been available since the early versions.

Quote from: pqyt on 2024-02-28 05:42:39

The source has been available since the early versions.

We are sorry that you were offended.
I will continue to use v7.0.0.0.

It is very hard for me to read and write source code due to depression at work, but I will try to follow it when I am feeling better.

Don't worry, I'm not offended. I was just pointing out that if you have any insights or advice on the math I'm willing to listen. I think I know how to develop but I'm not an audio engineer.

@pqyt
V.7.0.0 works great on both installed (1.6.17) and portable (2.2 preview x64) FBs on my W11Pro PC but none of the 7.0.1-xxx releases do even if configured identically.
Any idea what could be the cause?

The following is a report of the difference in display between v0.7.1.0 rc-2 and 0.7.0.0.

I assume the color changes are not intentional?

What I see is:
- the peak indicators are rendered completely wrong. They're suppose to be only 1 pixel high.
- The text is rendered weird.

What changed is that the rendered data is transformed using D2D to support mirroring and flipping. Since this all happens on right angles this should basically only mean a sign or an offset change in the coordinates. The transformations are built into D2D.

Are your GPU drivers up-to-date? What happens, as a test, if you flip the graph vertically or horizontally?

I'll see how far I get with the built-in tone generator I put in for debugging.

v0.7.1.0-rc-3, 2024-02-28

* Improved: Tweaked the background painting again to prevent flashes when resizing the component.
* Fixed (Regression): The selected gradient color scheme was not activated after startup.

You can download it only from GitHub (https://github.com/stuerp/foo_vis_spectrum_analyzer/releases/tag/v0.7.1.0-rc-3) for now.

Quote from: pqyt on 2024-02-28 08:02:58

v0.7.1.0-rc-3, 2024-02-28

* Improved: Tweaked the background painting again to prevent flashes when resizing the component.
* Fixed (Regression): The selected gradient color scheme was not activated after startup.

You can download it only from GitHub (https://github.com/stuerp/foo_vis_spectrum_analyzer/releases/tag/v0.7.1.0-rc-3) for now.

"The selected gradient color scheme was not activated after startup."

This is still not fixed. Oddly, it was working yesterday when I installed it but today it's back to not remembering again. When I launch fb2k I have to click on the Style I'm using to get it to work. The other color sources work fine.

EDIT... It's just the Custom Color Scheme that doesn't work. The others do.

With 2-channel stereo, no peak indicator is displayed in the right channel.

Thanks for your great work!

Testing rc3. Upgraded from beta 2 to rc3. It had issues with the beta2 layout it inherited. In my best laymans guess, it looked like it wasn't correctly rendering elements that had opacity less than 100% 🤷 I used the reset button, the issues persisted. I removed the component's UI element and readded it, which seemed to resolve the issue.

There does seem to be a bug with the reset button. To reproduce: context menu > configure > Styles > Click reset button. The configure modal window will flash, then if you go back to the styles section you'll see the list of styles has a duplicate list of entries. You can keep doing this behavior and the list of styles will keep incrementing a duplicate list indefinitely.

Quote from: metal_termite on 2024-02-29 18:35:26

Testing rc3. Upgraded from beta 2 to rc3. It had issues with the beta2 layout it inherited. In my best laymans guess, it looked like it wasn't correctly rendering elements that had opacity less than 100% 🤷 I used the reset button, the issues persisted. I removed the component's UI element and readded it, which seemed to resolve the issue.

There does seem to be a bug with the reset button. To reproduce: context menu > configure > Styles > Click reset button. The configure modal window will flash, then if you go back to the styles section you'll see the list of styles has a duplicate list of entries. You can keep doing this behavior and the list of styles will keep incrementing a duplicate list indefinitely.

As you can see, I just released 0.7.1.0. I'll look into it.

Any more details on the opacity problem: which element? Which opacity value?

Thank you for v7.1.0.
Unfortunately the Xaxis text is broken.

I have just noticed that the text is OK with a separate Spectrum for the right and left channels, but not with a Spectrum that contains both stereo channels!
After resetting and setting up the settings again, the problem occurs again...

Testing 0710 release after having stuck with 0600.  I noticed a bug in 0710's bar spectrum color scheme display--when Prism 1 is selected, although the gradient in the dialog shows red on top and dark blue on bottom, as it does in version 0600, during actual playback red is on the bottom of the bars and dark blue at the top.  See attached images.

You could say "well just hit the "Reverse" button in 0710 to correct it," but this produces a display visually unlike the correct rendition in 0600 (blue range becomes too indistinct towards the bottom).
Hopefully this was just an oversight and would be an easy fix?

Your right picture: if the settings are:
- Distribution: Linear
- Scaling: Linear
- X-axis: Decades
then everything is working as designed.

Quote from: pqyt on 2024-03-01 18:21:05

Your right picture: if the settings are:
- Distribution: Linear
- Scaling: Linear
- X-axis: Decades
then everything is working as designed.

Unfortunately, it doesn't look any better for me with this setting...
Maybe it's because of CUI , or because I have two instances installed? I'm at a loss...

You understood me wrong: why are you using linear Scaling mode? Most spectrum analyzers use Logarithmic by default.

great, the freezing has been fixed... for non-fullscreen mode... sorry to say this, but this component is a bugfest

great, the freezing has been fixed... for non-fullscreen mode... sorry to say this, but this component is a bugfest

Unfortunately I have another bug report for 0710.  When the X-axis frequency scale (distribution linear, scaling logarithmic) is set for an upper limit past about 24 kHz, instead of an expected fall-off before that point, a space/"notch" appears and frequency bars start appearing again where none should be.  In version 0600, this does not happen--a fall-off occurs and then no more activity is shown.  This is with normal music, not a test wave, etc.  The images below aren't from the the same exact moment but are representative of an entire song.  They show the X-axis set for 26 kHz max, first from 0600 and then 0710:
(https://i.imgur.com/QxaD4oP.png)   (https://i.imgur.com/4SCxVPQ.png)

for @pqyt does it make sense to have default settings of this component having the same color gradient, foreground and background colors as fb2k's built-in spectrum visualization something like this (https://youtube.com/watch?v=G6YZKf_XZYg)^{(this YT video shows the colorscheme matching the fb2k built-in Spectrum in dark mode, but this color scheme depends on the current DUI/CUI colorschemes just like built-in visualizations in foobar2000)} instead of a custom gradient one like the original foo_musical_spectrum?

^When the color scheme is "Artwork" and a track does not have an album cover, the color scheme of the graph will be different from the color scheme of other layout elements.
In this case, I think it makes sense to define a default color scheme (i.e. when there is no cover).

When no artwork is found, it falls back to a gradient of black to white.

What do you mean: different from other elements? Do those elements also have the Gradient / Artwork color source?

v0.7.2.0, 2024-03-03

* New: Analog-style spectrum analysis. Based on https://codepen.io/TF3RDL/pen/MWLzPoO.
* Improved: Performance optimization. Rendering will stop when the main window is minimized.
* Improved: Small performance optimization in SWIFT.
* Changed: The grid lines can be displayed without an X or Y-axis.
  * X-axis and Y-axis mode "None" still disables everything.
  * The X-axis or Y-axis labels can be controlled with the top, bottom, left and right settings.
  * The X-axis Line and Y-axis Line style have been renamed to Vertical and Horizontal Grid Line.
* Fixed: The style list box in the configuration dialog was not cleared before it was filled again after a reset.
* Fixed (Regression): Gradient brushes are created again with the colors in the same order as shown in the configuration dialog.

You can download it from Components (https://www.foobar2000.org/components/view/foo_vis_spectrum_analyzer) repository or upgrade from within foobar2000.

* New: Analog-style spectrum analysis. Based on https://codepen.io/TF3RDL/pen/MWLzPoO.

I'm thinking of compiling the next versions with Advanced Vector Extensions 2 (AVX2) instructions enabled. This would mean that the CPU in your computer should be released in 2013 or later (10 years ago, Intel Haswell).

Is that an unreasonable requirement?

I'm hoping for a civil discussion...

BTW, since I have the version 0.5.0.1 of this component, would the configuration of this component be reset if I upgrade this to the latest version (currently v0.7.2.0) as it might have breaking changes down the line since the old version of this I've have?

Quote from: sveakul on 2024-03-02 08:34:26

Unfortunately I have another bug report for 0710.  When the X-axis frequency scale (distribution linear, scaling logarithmic) is set for an upper limit past about 24 kHz, instead of an expected fall-off before that point, a space/"notch" appears and frequency bars start appearing again where none should be.  In version 0600, this does not happen--a fall-off occurs and then no more activity is shown.  This is with normal music, not a test wave, etc.  The images below aren't from the the same exact moment but are representative of an entire song.  They show the X-axis set for 26 kHz max, first from 0600 and then 0710:
(https://i.imgur.com/QxaD4oP.png)   (https://i.imgur.com/4SCxVPQ.png)

Did you disable the "Common / Suppress mirror image" flag? It was a feature request to show the amplitudes of frequencies above the Nyquist frequency. Default is to suppress the mirror image.

This plugin becomes better and better, thank you :)

I have a strange behaviour with bar mode and alpha transparency, it looks like the LED mode don't manage transparency like bar mode.

Bar mode:
[attach type=thumb]29547[/attach]

LED mode:
[attach type=thumb]29549[/attach]

Request:
For me the LEDs are a bit too thick, is it possible in a future developpement to reduce or adjust their size like this example ?
[attach type=thumb]29551[/attach]

Thanks