@d-healey Yeah putting the h3x values in quotes seems to have worked...I should have tried that earlier - t-shirt time...

@bendurso It applies to sliderpacks within MIDI processors (like your interface MIDI processor).

<3 Best community ever

@bendurso Man that sucks! Guess I'll have to make due with vst3

@d-healey Thanks Brother

@Fortune could this snippet be modified to cycle midi files instead of sample maps?

hey @Tania-Ghosh did you ever make any progress with this? id like to do something similar

@sjwilliams he also posted a demo project that shows how to use it here https://forum.hise.audio/topic/4621/true-legato-demo-project?_=1687669058934

@d-healey Thank you brother

@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...