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 100937 times) previous topic - next topic
chiglit and 5 Guests are viewing this topic.

Re: foo_vis_spectrum_analyzer

Reply #225 –
Quote from: grimes on
Are you using 64 bit? It claims to be 0.6.0.0 instead of 0.6.0.2
Can you try unzipping the package and copying the 64-bit DLL manually to your profile, please?

Re: foo_vis_spectrum_analyzer

Reply #226 –
Quote from: pqyt on
Something else must be wrong. All version information derive from 1 set of defines. Are you sure the DLL is replaced in your foobar2000 profile? Both 32 and 64-bits show up correctly on 3 different system here.
Yes the dll was replaced in profile/user-components-x64 with the version showing 0602 in its properties and sigcheck and the jittery performance, but showed as 0600 in the Foobar components list.  This was after using the auto-update feature to update.  Actually I did that twice, because after the component list version still showed 0600 I thought I hadn't hit "OK" or something so did the update again from a backup copy.  Maybe there is something wrong with the zip file updater that isn't passing all the info to Foobar.

Re: foo_vis_spectrum_analyzer

Reply #227 –
Quote from: pqyt on
Quote from: grimes on
Are you using 64 bit? It claims to be 0.6.0.0 instead of 0.6.0.2
Can you try unzipping the package and copying the 64-bit DLL manually to your profile, please?
Done, believe me it claims 0.6.0.0 and is possibly 0.6.0.0.

Re: foo_vis_spectrum_analyzer

Reply #228 –
@pqyt - just open the Components page in Preferences and see the version info and about page. The component says it's 0.6.0.0. Only the resource manifest speaks about 0.6.0.2.

And before I reported it to you I had verified that the same bug affects both the binary on component repository and on github.

And it's not a bug in sources as my compile correctly reports 0.6.0.2.

Edit: though I tweak your solution settings to suit my structure and I skip your complex powershell archiving script. I haven't tried to understand what it does.

Re: foo_vis_spectrum_analyzer

Reply #229 –
Quote from: Case on
@pqyt - just open the Components page in Preferences and see the version info and about page. The component says it's 0.6.0.0. Only the resource manifest speaks about 0.6.0.2.

And before I reported it to you I had verified that the same bug affects both the binary on component repository and on github.

And it's not a bug in sources as my compile correctly reports 0.6.0.2.

Edit: though I tweak your solution settings to suit my structure and I skip your complex powershell archiving script. I haven't tried to understand what it does.
OK. I rebuilt 0.6.0.2 as is and re-uploaded it to the components repository. Only the description is wrong. For better or for worse, it is 0.6.0.2. I don't know what went wrong during the initial release.

Re: foo_vis_spectrum_analyzer

Reply #230 –
Quote from: Case on
@pqyt - just open the Components page in Preferences and see the version info and about page. The component says it's 0.6.0.0. Only the resource manifest speaks about 0.6.0.2.

And before I reported it to you I had verified that the same bug affects both the binary on component repository and on github.

And it's not a bug in sources as my compile correctly reports 0.6.0.2.

Edit: though I tweak your solution settings to suit my structure and I skip your complex powershell archiving script. I haven't tried to understand what it does.
Yeah... I have tunnel vision. My own production foobar is still 32-bit and it was fine. My development foobars get the component during the build. Maybe I should take a break...

Re: foo_vis_spectrum_analyzer

Reply #231 –
I have installed the updated build and it's now showing as version 0.6.0.2 in the components list, but the A4@117.90 Hz and B7@440 Hz issue is still there :(

Re: foo_vis_spectrum_analyzer

Reply #232 –
Thanks for your great works!
This is long-awaited component for me.
And, please add left and right reversed setting to x-axis
 for displaying left and right channel side by side.

Re: foo_vis_spectrum_analyzer

Reply #233 –
Quote from: kenzzy on
And, please add left and right reversed setting to x-axis
 for displaying left and right channel side by side.
Me too as I haven't (and someone else) able to find the channel spectrum visualization for Default UI that it is compatible with foobar2000 x64 v2.x

I've already have side-by-side channel visualization mode (Visualization type = separate) on my own Channel Spectrum panel remake on Web Audio API as a CodePen project a long-time ago after realizing that there are people who wanting to see a 64-bit remake of foo_uie_vis_channel_spectrum, so I've added that to aforementioned CodePen project and renamed this project from "Overlayed channel spectrum + custom FFT" to just "Channel spectrum + custom FFT", and another FR: more frequency distribution mode as in the aforementioned CodePen project (which have similar behavior to Classic Spectrum Analyzer (vis_classic) plugin for Winamp as well as Channel Spectrum panel (foo_uie_vis_channel_spectrum) component for foobar2000 as I've realized that Channel Spectrum panel frequency scaling depends on the FFT size and actual number of bands rather than a true Mel scale)

BTW, I've noticed that my own Web Audio API visualizations especially ones involving simultaneous channel visualizations only react to the Front part of the surround sound, though the mono (one AnalyserNode that connected to the audio source before ChannelSplitterNode) visualization reacts to everything except LFE channels per specifications for the channelInterpretation="speakers" behavior when comes to downmixing, which you can test it by putting a surround sound (or anything more than 2 channels) audio file into the visualizer

Re: foo_vis_spectrum_analyzer

Reply #234 –
Quote from: pqyt on
The sample window duration is now optimized for FFT 4096. There is a relation between the window duration and the FFT size but I haven't found it yet. Higher FFT sizes will indeed show a lot of jitter now for 'pure' signals but music tracks should be fine.
I might be found a relation between window duration (or more accurately, the value of the last argument "requested_length" of get_chunk_absolute() function, which I believe that argument is measured in seconds rather than samples I've thought, hence the length of the chunk in samples depends on the sample rate even if the value of this argument is the same) and FFT size, which is usually measured in samples, it is "fftSize / sampleRate" for the actual length in seconds and hopefully, the sample window duration can be optimized for all window durations (including 65536-samples and above FFT)

Re: foo_vis_spectrum_analyzer

Reply #235 –
Had another look at this, it's getting there, well done with all the hard work.

In order to fully replace Musical Spectrum for me, it'll need the ability to turn off all axis text and lines, so just the main graphic display with no text etc. For full screen I like the axes and text, but when it's smaller as part of a main layout I like to just see the graphics. Forgive me if this is already implemented and I missed it!

Re: foo_vis_spectrum_analyzer

Reply #236 –
Quote from: darkflame23 on
Had another look at this, it's getting there, well done with all the hard work.

In order to fully replace Musical Spectrum for me, it'll need the ability to turn off all axis text and lines, so just the main graphic display with no text etc. For full screen I like the axes and text, but when it's smaller as part of a main layout I like to just see the graphics. Forgive me if this is already implemented and I missed it!
Set the X axis and Y axis to mode "None". Is that what you were looking for?

Re: foo_vis_spectrum_analyzer

Reply #237 –
Quote from: pqyt on
Quote from: darkflame23 on
Had another look at this, it's getting there, well done with all the hard work.

In order to fully replace Musical Spectrum for me, it'll need the ability to turn off all axis text and lines, so just the main graphic display with no text etc. For full screen I like the axes and text, but when it's smaller as part of a main layout I like to just see the graphics. Forgive me if this is already implemented and I missed it!
Set the X axis and Y axis to mode "None". Is that what you were looking for?

Sorted, thank you!
 

Re: foo_vis_spectrum_analyzer

Reply #240 –
New line mode looks great.

A slope control would be nice. I usually have my frequency analysers (SPAN or Prism) set to 3, 4.5 or 6dB slope towards the highs to read "flatter".

Re: foo_vis_spectrum_analyzer

Reply #241 –
Quote from: darkflame23 on
A slope control would be nice. I usually have my frequency analysers (SPAN or Prism) set to 3, 4.5 or 6dB slope towards the highs to read "flatter".
Do you have any documentation or articles I can read because I don't understand what you're asking?

Re: foo_vis_spectrum_analyzer

Reply #242 –
Work in progress: Curve with album art and dynamically created gradient

Re: foo_vis_spectrum_analyzer

Reply #243 –
Quote from: pqyt on
Quote from: darkflame23 on
A slope control would be nice. I usually have my frequency analysers (SPAN or Prism) set to 3, 4.5 or 6dB slope towards the highs to read "flatter".
Do you have any documentation or articles I can read because I don't understand what you're asking?

A standard analyser with no slope/weighting will make White Noise look "flat", but most musical program signals follow something closer to a Pink Noise spectrum (a 3dB per octave roll off) or even more. Music on standard analysers will always show more level in the bass than looks natural. More advanced analysers will have a dB slope control where you can adjust it to your liking. I'd highly recommend downloading Voxengo SPAN and TDR Prism (both free plugins), having a play, and reading their manuals to understand it a bit better. Prism is state of the art (I was on the beta team).

https://www.voxengo.com/product/span/

https://www.tokyodawn.net/tdr-prism/

The Prism manual explains it really well:

https://docs.tokyodawn.net/tdr-prism-manual/#Analyzer_Weighting

Re: foo_vis_spectrum_analyzer

Reply #244 –
Quote from: darkflame23 on
Quote from: pqyt on
Quote from: darkflame23 on
A slope control would be nice. I usually have my frequency analysers (SPAN or Prism) set to 3, 4.5 or 6dB slope towards the highs to read "flatter".
Do you have any documentation or articles I can read because I don't understand what you're asking?

A standard analyser with no slope/weighting will make White Noise look "flat", but most musical program signals follow something closer to a Pink Noise spectrum (a 3dB per octave roll off) or even more. Music on standard analysers will always show more level in the bass than looks natural. More advanced analysers will have a dB slope control where you can adjust it to your liking. I'd highly recommend downloading Voxengo SPAN and TDR Prism (both free plugins), having a play, and reading their manuals to understand it a bit better. Prism is state of the art (I was on the beta team).

https://www.voxengo.com/product/span/

https://www.tokyodawn.net/tdr-prism/
Will do. Thx.

Re: foo_vis_spectrum_analyzer

Reply #246 –
Quote from: darkflame23 on
Quote from: pqyt on
Quote from: darkflame23 on
A slope control would be nice. I usually have my frequency analysers (SPAN or Prism) set to 3, 4.5 or 6dB slope towards the highs to read "flatter".
Do you have any documentation or articles I can read because I don't understand what you're asking?

A standard analyser with no slope/weighting will make White Noise look "flat", but most musical program signals follow something closer to a Pink Noise spectrum (a 3dB per octave roll off) or even more. Music on standard analysers will always show more level in the bass than looks natural. More advanced analysers will have a dB slope control where you can adjust it to your liking. I'd highly recommend downloading Voxengo SPAN and TDR Prism (both free plugins), having a play, and reading their manuals to understand it a bit better. Prism is state of the art (I was on the beta team).

https://www.voxengo.com/product/span/

https://www.tokyodawn.net/tdr-prism/

The Prism manual explains it really well:

https://docs.tokyodawn.net/tdr-prism-manual/#Analyzer_Weighting
Also, I've already implemented the weighting functions, frequency tilting, and even ones derived from Winamp's Classic Spectrum Analyzer plugin here

Re: foo_vis_spectrum_analyzer

Reply #249 –
Quote from: grimes on
I saw it in waveform minibar (mod): Tooltip on_mouse_lbtn_down. The on_mouse_move tooltip is a little bit annoying and is buggy. Thanks for patience.
OK if I implement this with Advanced Settings? IMHO it is not expected behavior.