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.

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 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 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.