HISE Logo Forum
    • Categories
    • Register
    • Login

    FFT Analyser Settings...

    Scheduled Pinned Locked Moved Bug Reports
    3 Posts 3 Posters 156 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • DanHD
      DanH
      last edited by

      When I edit the settings they always revert back to their default settings. I've ended up editing the source code to get the changes to stick but though I should flag this up...

      Screenshot 2022-11-08 at 10.58.23.png

      DHPlugins / DC Breaks | Artist / Producer / DJ / Developer
      https://dhplugins.com/ | https://dcbreaks.com/
      London, UK

      1 Reply Last reply Reply Quote 0
      • S
        sinewavekid
        last edited by

        im not sure it's posted anywhere, but i've figured out a workaround like this (using it in a script panel)

        const var pnlAnalyzer = Content.getComponent("pnlAnalyzer");
        const var ScriptFX1 = Synth.getEffect("Script FX1");
        const var analyzerSource = Synth.getDisplayBufferSource("Script FX1");
        pnlAnalyzer.data.buffer0 = analyzerSource.getDisplayBuffer(0);
        
        const var fftSettings = {
           "BufferLength": 8192,
           "WindowType": "Blackman Harris",
           "Overlap": 0.8,
           "DecibelRange": [
              -73.0,
              0.0
           ],
           "UsePeakDecay": 1,
           "UseDecibelScale": 1,
           "YGamma": 0.42,
           "Decay": 0.87,
           "UseLogarithmicFreqAxis": 1
        };
        
        
        pnlAnalyzer.data.buffer0.setRingBufferProperties(fftSettings);
        

        and make sure to have an external display buffer added in the fft module in ScriptFX, but it persists for me!

        ustkU 1 Reply Last reply Reply Quote 2
        • ustkU
          ustk @sinewavekid
          last edited by

          @sinewavekid Yes in order to make the properties of a display buffer permanent, they need to be set from script and applied to the display buffer. That's the normal procedure, you did well 👍

          Can't help pressing F5 in the forum...

          1 Reply Last reply Reply Quote 2
          • First post
            Last post

          28

          Online

          1.7k

          Users

          11.8k

          Topics

          102.7k

          Posts