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 119033 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: foo_vis_spectrum_analyzer

Reply #825
Now the dust seems a bit settled with your foo_uie_text component,
can I expect a bugfix for foo_vis_spectrum_analyzer in regard to windows scaling (125/150/175/225/250/350) peakmeter issues?

https://hydrogenaud.io/index.php/topic,125031.msg1045171.html#msg1045171

Thx
Eventually. It may surprise you but I do have a life besides foobar2000 development.
No. I am not surprised.

It's just that I value bugfixes a whole lot more than adding new functionality.
And as a developer I know that when you are "out" of the code for a period of time fixing old bugs becomes more difficult.

Re: foo_vis_spectrum_analyzer

Reply #826
Now the dust seems a bit settled with your foo_uie_text component,
can I expect a bugfix for foo_vis_spectrum_analyzer in regard to windows scaling (125/150/175/225/250/350) peakmeter issues?

https://hydrogenaud.io/index.php/topic,125031.msg1045171.html#msg1045171

Thx
Eventually. It may surprise you but I do have a life besides foobar2000 development.
And as a developer I know that when you are "out" of the code for a period of time fixing old bugs becomes more difficult.
Don't worry, I've been keeping it warm. ;-)

Re: foo_vis_spectrum_analyzer

Reply #827
Quote
International Programmers’ Day celebrates the positive changes that programmers make to improve our everyday lives. It is usually held on January 7, but is also popularly celebrated on September 13, or on September 12 in leap years.
~ https://www.timeanddate.com/holidays/world/international-programmers-day

counting the days
Quis custodiet ipsos custodes?  ;~)

Re: foo_vis_spectrum_analyzer

Reply #828
Hi, this is a great component and it has really come a long way since you started development!

One small request / question since perhaps I missed a setting that already does what I'm looking for:
Is there a way to choose where in the DSP chain the analysis happens? I would love to have the analysis happen before application  of any DSPs in the chain as a configurable behavior.

Thanks!

Re: foo_vis_spectrum_analyzer

Reply #829
Is there a way to choose where in the DSP chain the analysis happens? I would love to have the analysis happen before application  of any DSPs in the chain as a configurable behavior.
Not that I know of, but hey it WOULD be neat to have a "before/after DSP chain applied" image toggle--interesting (and scary?) to see how much the signal has been changed from the original input.

Re: foo_vis_spectrum_analyzer

Reply #830
That is not something a visualization component can affect. And visualization would have no meaning if it worked on data prior to DSPs, it could be entirely invalid in regard to what is actually heard.
If you want scientific measurements of audio files you do not use a realtime visualization eye candy for that.

Re: foo_vis_spectrum_analyzer

Reply #831
And visualization would have no meaning if it worked on data prior to DSPs, it could be entirely invalid in regard to what is actually heard.
For educational purposes, would you mind explaining why that is?

 

Re: foo_vis_spectrum_analyzer

Reply #832
DSP chain can do anything to the signal. You could for example see data from an hour ago. You could see empty visualization yet hear perfect audio. Or in reverse, see perfectly valid looking visualization yet hear nothing or only noise.
Visualization has no meaning if it doesn't match what is being played.
If you want to analyze a static file, use a different tool.

Re: foo_vis_spectrum_analyzer

Reply #833
DSP chain can do anything to the signal.
But wasn't that @sveakul 's original question: why is there no way to access the raw PCM or other encoded format right after the audio stream has been decoded?

Surely it's a software design choice to send that decoded data first through the DSP chain?

Re: foo_vis_spectrum_analyzer

Reply #834
Case, I think you're being overly scientific  ;)  A "FYI" visual reference can have meaning in the fact that it gives perspective as to how applied user effects have "affected" a heretofore original signal.  No scientific analysis sought or expected.

Re: foo_vis_spectrum_analyzer

Reply #835
I tend to agree :)

For my use-case, I am using a DSP chain to correct my Beyerdymanic DT1990PROs' overly aggressive 8khz peak. After doing so, the resulting spectrum has subdued values around that area and no longer look like the original graph. However, it does sound correct and probably is correct according to many, many users around the internet. Why then should I not want to show the original spectrum?

Re: foo_vis_spectrum_analyzer

Reply #836
By going to Common in the Artwork section and activating the "Show artwork on background" flag, if you do not have the panel active the artwork will not appear.





UP

The problem is always present.

Accurate. At the first instance of restarting foobar2000 the images / covers / artwork appear.

But if you jump track the images are not updated.

Re: foo_vis_spectrum_analyzer

Reply #837
Suggestion: Infinite average spectrum/cumulative average graph
X

Like the RMS spectrum in foo_enhanced_spectrum_analyzer, but with infinite averaging that eventually converge to the particular curve when you let the analyzer running for long enough with an equation:
Code: [Select]
for (let i = 0; i < averageSpectrum.length; i++) {
  averageSpectrum[i] = (data[i] + cumulativeIdx*(isFinite(averageSpectrum[i]) ? averageSpectrum[i] : 0))/(cumulativeIdx+1)
}
cumulativeIdx++ // being incremented by one every time you calculate the infinite average spectrum

Of course, since infinite averaging never decays, this infinite average spectrum should be reset on seek or when playing new track(s) alongside the main spectrum and peaks like foo_enhanced_spectrum_analyzer

Re: foo_vis_spectrum_analyzer

Reply #838
Suggestion: Infinite average spectrum/cumulative average graph
[attach type=image]31580[/attach]

Like the RMS spectrum in foo_enhanced_spectrum_analyzer, but with infinite averaging that eventually converge to the particular curve when you let the analyzer running for long enough with an equation:
Code: [Select]
for (let i = 0; i < averageSpectrum.length; i++) {
  averageSpectrum[i] = (data[i] + cumulativeIdx*(isFinite(averageSpectrum[i]) ? averageSpectrum[i] : 0))/(cumulativeIdx+1)
}
cumulativeIdx++ // being incremented by one every time you calculate the infinite average spectrum

Of course, since infinite averaging never decays, this infinite average spectrum should be reset on seek or when playing new track(s) alongside the main spectrum and peaks like foo_enhanced_spectrum_analyzer
Please no. I just want a simple long overdue bugfix instead if new features.

Re: foo_vis_spectrum_analyzer

Reply #839
Please no. I just want a simple long overdue bugfix instead if new features.
I agreed with you, so for @pqyt, better off bugfixing this component first before adding new features