I think using Engine.setLatency dynamically can be problematic.

Instead, after the maximum delay value caused by pitchshift is set in Engine.setLatency, the difference can be balanced dynamically with a delay node according to the parameter values ​​that give less delay.

@lijas90 You need to add a generic script reference for the EQ then bypass it in the button callback

const var ParametriqEQ1 = Synth.getEffect("Parametriq EQ1"); const var Button1 = Content.getComponent("Button1"); inline function onButton1Control(component, value) { ParametriqEQ1.setBypassed(value); }; Content.getComponent("Button1").setControlCallback(onButton1Control);

@ryan_nfa Nice :)

@d-healey Ahaha, that's it😹

@Zazzi post a snippet.

@Lindon
Ah, I didn't see that. Thanks to you. :-)

@d-healey ok thanks I will go watch the video.

@Lurch still seems to be trying to build clouds (clouds.h)....

@Mighty23 said in fix_block - I can't understand it:

Can I have some concrete examples?

For example, if you have a very fast LFO, using a frame_block is probably more interesting than a fix8_block to achieve more precise and smoother modulation.

@pcs800 If my memory serves me correct I believe this HISE tutorial shows you how to display compression amount:

https://github.com/christophhart/hise_tutorial/tree/master/DynamicsFX

SOLVED

I just opened an older version of Hise. My fault. I am so sorry 😊

@JulesV I seem to remember getting that too but everything worked fine, the project would compile and export. @Lindon's explanation seems plausible.

@d-healey lol !!

ok so you have to see this then....

its on a different thread....
https://forum.hise.audio/topic/12880/chord-player-inversions-help-with-indexing

@Lindon I was referring to a toggle option, like "Use strings instead of numeric values." So instead of looking for numbers, it would look for and save string values instead. This would only work when it’s enabled, so it won’t break any existing plugins.
But it was just an idea; maybe it doesn’t really make sense.

@d-healey I've experienced this in earlier versions too

@Lindon Thanks!

@ustk said in Network range mismatch:

@Lindon but does the warning stay in certain cases ?

yeah - but very rarely

Thanks so much -- I really appreciate your time and helpfulness.