Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: foo_vis_spectrum_analyzer (Read 100849 times) previous topic - next topic
0 Members and 4 Guests are viewing this topic.

Re: foo_vis_spectrum_analyzer

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

Thanks for your great work!

Re: foo_vis_spectrum_analyzer

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

Thanks for your great work!
Confirmed. But only when vertically stacked. I'll investigate.

Re: foo_vis_spectrum_analyzer

Reply #477
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.

Re: foo_vis_spectrum_analyzer

Reply #478
v0.7.1.0, 2024-02-29

* Changed: To avoid confusion color source None for the background has been disabled until it can be properly implemented.
* Fixed: Reversing the colors of a gradient did not recalculate the position of the colors. Instead it spread out the colors evenly.
* Fixed (Regression): The peak indicators on the bar graph weren't rendered.

You can download it from Components repository or upgrade from within foobar2000.

Re: foo_vis_spectrum_analyzer

Reply #479
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.

Re: foo_vis_spectrum_analyzer

Reply #480
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.
It's just a bug in the dialog. The listbox is not cleared before it's filled again. The style entries are still uniquely defined. I'll release a point release after the inevitable release bug reports have come in.

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

Re: foo_vis_spectrum_analyzer

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

Unfortunately no, and those assertions were just my best guess, I could be wrong about what aspect of the rendering was dysfunctional. In retrospect I should have recorded a short clip which I will do going forward if I encounter issues like that.

Re: foo_vis_spectrum_analyzer

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

Re: foo_vis_spectrum_analyzer

Reply #483
Thank you for v7.1.0.
Unfortunately the Xaxis text is broken.
I'm unable to reproduce this. I tried different settings and different scaling functions, even with linear scaling like you seem to use.

Re: foo_vis_spectrum_analyzer

Reply #484
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...

Re: foo_vis_spectrum_analyzer

Reply #485
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...
Your right picture: if the settings are:

- Distribution: Linear
- Scaling: Linear
- X-axis: Decades

then everything is working as designed.

Re: foo_vis_spectrum_analyzer

Reply #486
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?

Re: foo_vis_spectrum_analyzer

Reply #487
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?
You're right. That's because the graph is now rendered upside down and then flipped, unless the user selects "Flip Vertically". Sounds confusing but mathematically it makes sense.

I'll reverse the colors before creating the brush. That way the GUI stays consistent.

Re: foo_vis_spectrum_analyzer

Reply #488
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...

Re: foo_vis_spectrum_analyzer

Reply #489
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.

Re: foo_vis_spectrum_analyzer

Reply #490
You understood me wrong: why are you using linear Scaling mode? Most spectrum analyzers use Logarithmic by default.
Yes, I misunderstood that, sorry. If I set Scaling to Linear, the text scale is displayed correctly. Thank you!
I had used the same settings for both Spectrums. Strangely enough, this led to a completely different result for the Spectrum with both stereo channels.

 

Re: foo_vis_spectrum_analyzer

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

Re: foo_vis_spectrum_analyzer

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

You know ... It's beta. And it is called beta for a reason. Nobody requires you to install it and expose yourself to bugs.

Re: foo_vis_spectrum_analyzer

Reply #493
great, the freezing has been fixed... for non-fullscreen mode... sorry to say this, but this component is a bugfest
Great! Looking forward to your bug reports so that I can fix them. Oh, wait,... you're just whining...

Re: foo_vis_spectrum_analyzer

Reply #494
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:
  

Re: foo_vis_spectrum_analyzer

Reply #495
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:
  
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.

Re: foo_vis_spectrum_analyzer

Reply #496
That was it, thank you!  BTW, on my install of 0710 the option to "Suppress mirror image" was un-checked by default.

Edit:  the reversed gradient color bars with Prism 1 issue is indeed fixed with github release 0720-alpha 1, great.  Just installed it on top of 0710 and so far all is well.

Re: foo_vis_spectrum_analyzer

Reply #497
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(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?

Re: foo_vis_spectrum_analyzer

Reply #498
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(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?
The color schemes are in there but I'm not a fan of making them the default.

Re: foo_vis_spectrum_analyzer

Reply #499
^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).