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 and this) 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:

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