version 4.1.0

[hvianna]

What's new:

Added:

• colorMode - additional options for coloring analyzer bars: by bar amplitude (level) or bar position (index);
• roundBars - rounded corner analyzer bars;
• isRoundBars read-only property;
• trueLeds - your LED bars now more vintage than ever!
• New level property for registered gradients.

Fixed:

• Avoid drawing the Y-axis scale and unlit LEDs twice, in 'dual-combined' channel layout.

Improved:

• Improved frequency scales labeling (especially for noteLabels) - label sizes were slightly reduced in fullscreen;
• Code cleanup and optimizations.

---

This discussion was created from the release version 4.1.0.

[TF3RDL]

Nice update, but someone commented on the post I've made on r/foobar2000, so I updated my channel spectrum visualization on CodePen to add something like this:

So, I'd like to see the dual-horizontal property for channelLayout that look like this above because foo_uie_vis_channel_spectrum hasn't been updated for a very long time (no default UI support, nor it is compatible with 64-bit version of foobar2000 v2.0 and newer)

[hvianna]

Sure, dual-horizontal is in the plans and you'll be able to choose different layouts: low or high frequencies meeting at the center, or both channels from low to high.

I wasn't sure if that would be a much desired feature, so thanks for letting me know.

[TF3RDL]

Good to know you're focusing on adding new features, as I'd leave the task of porting audioMotion-analyzer as 64-bit foobar2000 component (#50) to someone else as a part of recreating the magical foo_fft_analyzer.

Also, do you need create a separate repository just for a sliding DFT-based CQT/VQT spectrum analyzer (#30) since the sliding DFT requires AudioWorklets, unlike custom FFT, which don't require AudioWorklet and it can be easily accomplished by taking the output of getFloatTimeDomainData()?

[hvianna]

I plan to add a callback interface so user functions can provide data for visualization, as it has been asked before (on #1 and #3). This would allow using different custom transforms implemented as separate modules.

[TF3RDL]

Ah, interesting. Hopefully, the CQT/VQT algorithm and the sliding DFT version is compatible with the proposed callback functions for custom transforms, especially the frequency bands part.

BTW, I think getting the X-axis labels positioned correctly on audio spectrum whose frequency band generation algorithm really depends on FFT size/number of bands/sample rate like my channel spectrum visualization is more difficult to implement accurately as getting a closed-form equation for these frequency band generation output is very difficult or even impossible to get

[hvianna]

Thanks for the gists! I'll have a more detailed look at the code as soon as I have a chance.

[TF3RDL]

BTW, while I'm racing for my CodePen projects (interactive mockups of foo_fft_analyzer, foo_cqt_analyzer, and other Wamoc's audio analysis components for foobar2000) against Crossover's foo_enhanced_spectrum_analyzer in terms of updates, I added FFT bandpower mode to my project that is originally for CQT/VQT visualizations, something like this:

which is a lanzcos-interpolated FFT bandpower reminiscent of foobar2000's default spectrum or even WhiteCap Standalone, which is different from the CQT algorithm like this below:

BTW, even doing an FFT with a non-power of 2 size is faster than calculating a CQT/VQT directly on large number of bands, whereas direct CQT/VQT calculation might be faster than doing a NPoT (acronym for non-power of two) FFT with third-octave or fewer number of bands