@Casmat Yes, or adapt your design

Is it possible to use the scriptnode DisplayBuffer with the MatrixPeakMeter FloatingTile?

@Christoph-Hart

Content.makeFrontInterface(600, 600); // Fetch a displaybuffer source reference to the DSP network const var dp = Synth.getDisplayBufferSource("Script FX1"); // Get the first "external" Displaybuffer const var gr = dp.getDisplayBuffer(0); // Set the buffer length to 1024 (about 23ms) // (this correlates with the timer frequency below) gr.setRingBufferProperties({ "BufferLength": 1024, "NumChannels": 1 }); // Get a reference to the FIFO that contains the values const var buffer = gr.getReadBuffer(); const var Knob1 = Content.getComponent("Knob1"); const var t = Engine.createTimerObject(); t.setTimerCallback(function() { // Fetch the maximum value of the last 50ms and display // it on the knob Knob1.setValue(buffer.getMagnitude(0, buffer.length)); }); // Start the timer with ~30Hz. t.startTimer(30);

@d-healey went straight to release version. Will try debug

Hi everyone!
I have the same problem with 2.5.0 (AAX_eStemFormat_Stereo).
Can anyone share a 2.4.1 AAX SDK with me? It would be greatly appreciated.

The performance difference is pretty negligible here.

@d-healey thank you mate

@d-healey Ah! That looks interesting, will take a look! Thanks!

@orange Unfortunately this does not work in ma actual use case.
Because I need to cancel the previous call if a new one has been made in between. Content.callAfterDelay will execute all previous calls with no way to cancel them.
But since it was not in the question I asked this function perfectly does what it promises :)

I'm then relying on a simple timer so I can stop previous call on next one, and use an external variable to copy the parameter. ;)

Unless if it's possible to add a "cancel call" of some sort to the Content.callAfterDelay function @Christoph-Hart?

@ustk Yeah, I'm not throwing away 2 years of work out of spite, I just hate the sunken cost fallacy here...

@d-healey Thank you David Healey, I learn a lot from your YouTube channel.

@DanH https://forum.hise.audio/topic/7621/protools-load-problem/25?_=1687444674577

@Lindon Here's the thread I just found now regarding the auto- scroll issue I meant. Hope it is clearer now. And looks like it's sill a bug.

@TNTHM the compilation isnt the issue, and he's on windows

@TNTHM said in Limiter module not in API?:

@Christoph-Hart Got it. I see that there is a limiter section in the Dynamics module. Is that the limiter we should use?

yep - but bear in mind its a look ahead limiter - and will add delay to your output...

@Sawer said in Auto - Scroll Preset browser:

Hello everyone.

I am using the default preset browser to call states of the plugin, however, the highlighting square does not follow up when I selected a priest that is down to scroll to. Wondering if it is a but or if there's a method to set in the preset to make it follow.

er..... not sure what you are saying...

how to build hise 3.03?

The version numbers are pretty meaningless. Just build the develop branch.

the steps in the github have been stripped to nothing

They've been simplified to 5 steps - https://github.com/christophhart/HISE#windows

there is nothing anymore only a video from 3 years ago

I made an updated video last year (although nothing has really changed)

so what do i choose during install. which IPP,

You don't need IPP but if you are using it you install the OneAPI and if I remember correctly there is an option for OneAPI in Projucer (I explain it in the video I've included below)

@ustk Understood. Thank you.

@Christoph-Hart thanks! :)

I’m running a sample based Synth with 44.1kHz/16 bit (internally obersampling 4x) and I don’t hear aliasing though when I look at the waveform I can see it is distorted a little. So, what’s your experience? Where does it become audible to you?

I have to add that I use to not transpose a sample by more than +/-2 semitones with this synth so I can’t tell how it sounds with more than that