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

Link Preview Image hise_tutorial/DynamicsFX at master · christophhart/hise_tutorial

The Tutorial project for HISE. Contribute to christophhart/hise_tutorial development by creating an account on GitHub.

favicon

GitHub (github.com)

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

@Mickolos The solution is much simpler than the code you've already written :) It's basically just adding one line.

This is your knob callback

inline function onknbLottieControl(component, value) { pnlLottie.setAnimationFrame(value); }

Within this same callback you use setAttribute to control your module.

inline function onknbLottieControl(component, value) { pnlLottie.setAnimationFrame(value); WaveformGenerator1.setAttribute(WaveformGenerator1.WaveForm1, value); }

The only extra thing you need to do is get a reference to the waveform generator within on init - HISE will create this for you if you right-click on the waveform generator module's header and select create generic script reference. Put this near the top of your script:
const var WaveformGenerator1 = Synth.getChildSynth("Waveform Generator1");

@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

@Dan-Korneff well，I understand！thanks bro！

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

Ah ok I see the issue. I assume you're connecting the button to the module through processor/parameter ID? The button only has two states, 0 and 1, so it will only change the Type parameter between those two values.

If you want it to cycle through more values you'll need to handle it through scripting by using a variable as a counter and increasing it each time the button is clicked, resetting when you get to the max (4) and passing the value to the EQ's Type attribute.

If your EQ has more than one band you'll need to use the band offset to select which band is affected by the button - forum search for "band offset".

@goldee
Of course you can simlply use a sampler to do this.
You can also try something like "micro sidechain" (which is basically inject the noise aound the 0 point) might give you a more natural sounding result

@d-healey I was being daft. The problem I have is that the vast bulk of my instrument is tied up in a ScriptFX Granulator - because using the scriptnode synth module caused me loads of audio issues early on, so I switched to using ScriptFX instead and it's been clean sailing since. Issue is - you can't use these modulators on ScriptFX, the envelope, pitch etc aren't available.

@DanH no, but they are ref counted, so just use the new name and reload the project, then the old ones will disappear.

@pcs800 If you delve into the file and file system APIs you can add a button to open a file browser to allow users to select a IR.

Or if you want a simpler solution you can add a waveform control to your UI, connect it to your effect, and then users can just drag/drop an IR onto it.