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

Re: foo_vis_spectrum_analyzer

Reply #76 –
Quote from: Air KEN on
Two of my laptops are experiencing the same symptoms.
Is it a similar environment?

Quote from: pqyt on
Are you running with high(er) DPI settings? While everything is designed to support it I haven't really tested that setup yet.

Ahh ... that (scaling/DPI) could be the cause. I run dual monitors.
The primary with 150% scaling. The secondary with 100% scaling.
foobar2000 runs on the secondary monitor.
I tested the spectrum analyzer window in both displays, it behaves the same.

Re: foo_vis_spectrum_analyzer

Reply #77 –
I did an experiment -- i set both displays to 100% scaling; restarted foobar; playback music and display spectrum analyzer window.
I got the same behavior as I reported earlier ...

Re: foo_vis_spectrum_analyzer

Reply #78 –
I'm not sure I reproduced your problem but something is still wrong:

- At a higher DPI when I change the axis mode, the axes adapt and redraw but the bands of the spectrum are unaware of the change.
- Overall the main interface and the dialog are blurry due to upscaling.

On it.

Re: foo_vis_spectrum_analyzer

Reply #79 –
    Quote from: boxerfan88 on

    • the X axis frequency is not shown
    • the X axis seems to be cutoff at 3kHz -- the spectrum display should run until 40kHz
    Same issue here with no frequency labelling of the X axis, and no apparent change when its mode is changed.  Seems to be cutting off the high end altogether as boxerfan88 notes.  My display is just a W10 125% scale and 1920 X 1080 resolution.

    Re: foo_vis_spectrum_analyzer

    Reply #80 –
    @pqyt

    Reply #74: https://hydrogenaud.io/index.php/topic,125031.msg1035506.html#msg1035506

    my laptop
    Windowws 11
    Display:
    15.6
    1920x1080
    Scale:125%

    This is a standard specification.
    SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD 490 PRO, DT 1990 PRO, HiFiMAN Edition XS, Bowers & Wilkins P7, FiiO FT5, 水月雨 (MOONDROP) 空鳴 - VOID, Nakamichi Elite FIVE ANC, SONY WH-ULT900N (ULT WEAR) (made a Upgrade/Balanced Cable by myself)

    Re: foo_vis_spectrum_analyzer

    Reply #81 –
    Quote from: sveakul on
      Quote from: boxerfan88 on

      • the X axis frequency is not shown
      • the X axis seems to be cutoff at 3kHz -- the spectrum display should run until 40kHz
      Same issue here with no frequency labelling of the X axis, and no apparent change when its mode is changed.  Seems to be cutting off the high end altogether as boxerfan88 notes.  My display is just a W10 125% scale and 1920 X 1080 resolution..[/list]
      The X axis display issue is one thing.

      But could it be that there is some confusion about the settings? The X axis does not control the frequency range. That is done by the frequency settings: either a Hz range or a note range. The X labels just indicate what the possible content of each bin/bar is; what you put in each bin is specified by the Transform and Frequencies settings

      Re: foo_vis_spectrum_analyzer

      Reply #82 –
      Yes, I understand this completely.  But the expectation is that by specifying a frequency range for the X-axis, the display would then show some progressive numerical values along that axis, starting with the lowest frequency specified for the range.  Just as the Y-axis now displays dB reading values through the the height of that axis according to what was specified.

      Not trying to annoy, just letting you know we are on the same page.

      Re: foo_vis_spectrum_analyzer

      Reply #83 –
      Quote from: sveakul on
      Not trying to annoy, just letting you know we are on the same page.
      Oh you're not annoying. I appreciate the feedback. Coding, liking writing, is a lonely job ;-) It's just hard to understand a bug report sometimes because a lot of times seemingly irrelevant context information does not get mentioned.

      Re: foo_vis_spectrum_analyzer

      Reply #84 –
      As for the new constant-Q transform mode, does this component exhibit performance issues/bad framerate (when using 1/24th octave or higher bands and large window size of 300ms max and above) in the same way as my own audio spectrum analyzer?

      As I haven't tested this @pqyt component yet as I'm waiting for this component to get out of the alpha stage (unless on certain situations), so I can't give estimates about the framerate for the CQT visualization and this question is for anyone curious on performance impacts on sliding DFT vs. Goertzel algorithm

      Re: foo_vis_spectrum_analyzer

      Reply #85 –
      v0.4.0.0, 2023-11-26

      * New: Most colors and the custom color scheme can be modified in the configuration dialog.
      * Improved: Each instance of the component now has its own configuration. Note: The fullscreen version is a separate instance.
      * Improved: Added spin buttons to most numeric controls.
      * Changed: Mel scale mapping is now called Triangular Filter Bank scale mapping.

      You can download it from the Components repository.

      You'll notice that the configuration dialog is becoming quite large and complex. Please report any quirks or crashes.

      Re: foo_vis_spectrum_analyzer

      Reply #86 –
      Quote from: pqyt on
      v0.4.0.0, 2023-11-26

      * New: Most colors and the custom color scheme can be modified in the configuration dialog.
      * Improved: Each instance of the component now has its own configuration. Note: The fullscreen version is a separate instance.
      * Improved: Added spin buttons to most numeric controls.
      * Changed: Mel scale mapping is now called Triangular Filter Bank scale mapping.

      You can download it from the Components repository.

      You'll notice that the configuration dialog is becoming quite large and complex. Please report any quirks or crashes.

      Hi, thanks for this great component.
      Some issues I have:
      - still no labels on X axis (no digits nor letter, no Hz,no Notes)
      - because there are no labels (see above) I am not 100% sure but it seems that changing values (like Hz or notes range) has no effect on the display. Ex. I change frequency to 96kHz and play an mp3 file....and to my suprise I see moving bars right to the right end of the component window. How is that possible for mp3 to be able to "play" 96kHz? So either the bars show something different than they should or the changes do not take effect. As somebody has written earlier - it looks likje the display is cut at some low/mid frequency and does not show anything higher no matter what changes in the menu we make.
      Please make x axis values visible (just like Y axis and dB are) so we would know what we really see.

      Re: foo_vis_spectrum_analyzer

      Reply #87 –
      Quote from: wojak on
      Some issues I have:
      - still no labels on X axis (no digits nor letter, no Hz,no Notes)
      - because there are no labels (see above) I am not 100% sure but it seems that changing values (like Hz or notes range) has no effect on the display. Ex. I change frequency to 96kHz and play an mp3 file....and to my suprise I see moving bars right to the right end of the component window. How is that possible for mp3 to be able to "play" 96kHz? So either the bars show something different than they should or the changes do not take effect. As somebody has written earlier - it looks likje the display is cut at some low/mid frequency and does not show anything higher no matter what changes in the menu we make.
      Please make x axis values visible (just like Y axis and dB are) so we would know what we really see.
      I'm afraid I don't have a clue what is wrong. This (and the previous version) has been tested on 3 different computers and 3 different versions of Windows, both x86 and x64. None of the systems behave like yours. The visual is nearly identical to the original foo_musical_spectrum component with the same settings.

      What happens when you embed the component in the main foobar2000 UI instead of using a separate window?

      Re: foo_vis_spectrum_analyzer

      Reply #88 –
      I'm afraid my experiences with 0.4.0.0 are the same as wojak--there is no visible X-axis labelling either by frequency or note.  This is using Foobar 2.1 x64 2023-11-22 preview, Windows x64 at 125% scale on a 1920X1080 display resolution.  The images attached here show what I am seeing, and what my settings are.  The plugin was added as a regular tabbed fixed UI element using Layout Editing Mode, like all my stuff is.

      A new "irritation" of this version is the inablity to change band no. or frequency range quickly by using the delete or backspace key in the setting boxes and typing the desired value--now you must use the small up/down arrow buttons for any change made.

      Re: foo_vis_spectrum_analyzer

      Reply #89 –
      Using different Windows DPI setting than 100% clips the contents of the window and things are only partially visible. At least here easily reproducible.

      Re: foo_vis_spectrum_analyzer

      Reply #90 –
      Reply #80 https://hydrogenaud.io/index.php/topic,125031.msg1035547.html#msg1035547
      As mentioned here, this is the standard specification.

      Set again.
      Windowws 11
      Display:
      15.6
      1920x1080
      Scale:100%

      I was able to display it.
      X axis is OK. There is still a problem with the Y axis.
      Hmm, how do I use it?

      SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD 490 PRO, DT 1990 PRO, HiFiMAN Edition XS, Bowers & Wilkins P7, FiiO FT5, 水月雨 (MOONDROP) 空鳴 - VOID, Nakamichi Elite FIVE ANC, SONY WH-ULT900N (ULT WEAR) (made a Upgrade/Balanced Cable by myself)

      Re: foo_vis_spectrum_analyzer

      Reply #91 –
      Quote from: Case on
      Using different Windows DPI setting than 100% clips the contents of the window and things are only partially visible. At least here easily reproducible.
      It's not here. I just switched one of my screens to 125%, created a new tab and added a new instance of the element. Perfect sizing from the start.

      Re: foo_vis_spectrum_analyzer

      Reply #92 –
      Quote from: Air KEN on
      X axis is OK. There is still a problem with the Y axis.
      Hmm, how do I use it?
      Erhm... the Y-axis is right there in your screenshot. What do you mean by: "how do I use it?"

      Re: foo_vis_spectrum_analyzer

      Reply #93 –
      @pqyt

      For example, the top of the Y axis (-6db) cannot be displayed any further.
      Is it something like this?

      Scale:100%
              
      SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD 490 PRO, DT 1990 PRO, HiFiMAN Edition XS, Bowers & Wilkins P7, FiiO FT5, 水月雨 (MOONDROP) 空鳴 - VOID, Nakamichi Elite FIVE ANC, SONY WH-ULT900N (ULT WEAR) (made a Upgrade/Balanced Cable by myself)

      Re: foo_vis_spectrum_analyzer

      Reply #94 –
      Quote from: sveakul on
      I'm afraid my experiences with 0.4.0.0 are the same as wojak--there is no visible X-axis labelling either by frequency or note.  This is using Foobar 2.1 x64 2023-11-22 preview, Windows x64 at 125% scale on a 1920X1080 display resolution.  The images attached here show what I am seeing, and what my settings are.  The plugin was added as a regular tabbed fixed UI element using Layout Editing Mode, like all my stuff is.

      A new "irritation" of this version is the inablity to change band no. or frequency range quickly by using the delete or backspace key in the setting boxes and typing the desired value--now you must use the small up/down arrow buttons for any change made.

      Yes,
      the inability to manually put desired values into boxes is a shortcoming for me too.
      Plus if we are abe to make the X-axis values visible, it would be nice to also have the ability to see the valuses directly on the bars (which is impossible for me now) - ex. if I put "notes" on the X-axis I would see the notes on the bottom and when going on the actual bars with the mouse I would see the frequencies corresponding with those notes.
       

      Re: foo_vis_spectrum_analyzer

      Reply #95 –
      Quote from: pqyt on
      Quote from: Case on
      Using different Windows DPI setting than 100% clips the contents of the window and things are only partially visible. At least here easily reproducible.
      It's not here. I just switched one of my screens to 125%, created a new tab and added a new instance of the element. Perfect sizing from the start.
      I can match the behavior you see by adjusting foobar2000 compatibility settings and forcing it to use System performed DPI scaling. Then the spectrum isn't clipped and all text goes blurry, like in your screenshot. But with default settings the scaling is unfortunately off. Doesn't matter whether the element is embedded to the UI or just opened quickly as a popup from the main menu.

      Re: foo_vis_spectrum_analyzer

      Reply #96 –
      Quote from: Air KEN on
      For example, the top of the Y axis (-6db) cannot be displayed any further.
      Is it something like this?
      That's just a design choice I made. The bars will never extend higher than 0dB. I chose to let the top of Y-axis start at the top of the window, clipping the 0dB label.
      Either I start a little bit lower, creating a black band on top, or I can move the 0dB label a little bit lower. Or neither...

      Re: foo_vis_spectrum_analyzer

      Reply #97 –
      Quote from: Case on
      Quote from: pqyt on
      Quote from: Case on
      Using different Windows DPI setting than 100% clips the contents of the window and things are only partially visible. At least here easily reproducible.
      It's not here. I just switched one of my screens to 125%, created a new tab and added a new instance of the element. Perfect sizing from the start.
      I can match the behavior you see by adjusting foobar2000 compatibility settings and forcing it to use System performed DPI scaling. Then the spectrum isn't clipped and all text goes blurry, like in your screenshot. But with default settings the scaling is unfortunately off. Doesn't matter whether the element is embedded to the UI or just opened quickly as a popup from the main menu.
      Thx. I will try that later. I really want to get this solved.

      Re: foo_vis_spectrum_analyzer

      Reply #98 –
      Quote from: wojak on
      the inability to manually put desired values into boxes is a shortcoming for me too.
      Some people would call that a UI improvement... Out of the box there's no decent numeric textbox with a spin control and edit functionality. I'm not yet 100% satisfied with the UI yet. I'll see what I can do.

      Re: foo_vis_spectrum_analyzer

      Reply #99 –
      Enhanced Spectrum analyzer (foo_enhanced_spectrum_analyzer)
      -It is displayed inside the frame (above the image)

      SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD 490 PRO, DT 1990 PRO, HiFiMAN Edition XS, Bowers & Wilkins P7, FiiO FT5, 水月雨 (MOONDROP) 空鳴 - VOID, Nakamichi Elite FIVE ANC, SONY WH-ULT900N (ULT WEAR) (made a Upgrade/Balanced Cable by myself)