@d-healey Thank you, I must have missed that in the docs

@DJJD12345 said in xcpretty Not Detected After Install on macOS Tahoe M1: Compiling Fails in HISE Export:

Downloaded it as you described in your video on how to download Hise

There is clearly a mismatch between what I show in the video and what you did. So you need to tell me exactly what you did, step by step. And you need to tell me if you removed all previous versions you'd downloaded before you followed the video.

It is sample accurate if you use it in a frame container. Otherwise it is the ModulationBlockSize that is taken but I am not 100% sure how. Because if an audio block is 512 and the modSize is 16, I don't see how it works...

If the ModulationBlockSize is set, then HISE will split up the incoming buffers and send out parameter values with this control rate, so:

512 samples in, ModulationBlockSize = 16 - calculate all modulation values and send the parameter callbacks - process 16 samples - calculate all modulation values and send the parameter callbacks - process 16 samples ...

Note that the frame container will not make this sample accurate because that's a inner property of the network and HISE has no idea whether you use frame processing from the outside.

That's why it's recommended for high-resolution modulation requirements to use the extra_mod nodes and connect it to the slots - they can fetch the modulation signal from within the node and apply it to the signal (using multiplication) or modulate any parameter with the resolution you want within your network.

@Chazrox said in Need More 'reg' variables !:

can you give me a quick tip on which reg's be change to const?

All component and module references, arrays, and objects.

@CatABC if you change both the low and the highkey downwards you need to change the lo key first and then the hi key, cause it’s not possible to set the hi key below the lowkey

Sorry if this is off-topic.

In a wavetable synth, even if the notes are played at different times, all sounds modulate with the same timing, right?

@Orvillain said in [bug] SlotFX.setBypassed no worky:

What is the benefit of using const, in my situation?

I think the best answer is from Christoph

it yields a huge performance boost (because it can resolve the function call on compile time).
There is absolutely no reason to not declare UI widgets, references to modules (via Synth.getModulator() etc.) not as const

reg is good for accessing script level variables in midi callbacks and anywhere else where you would have had to use a script level var. But the more reg you have (and you only get 32 per namespace) the worse the performance gets. Internally reg is like a predefined array that HISE is keeping track of. So the more values you add the more data it needs to go through each time to you access it.

Another addition to Javascript: Use reg instead of var when declaring temporary variables which are accessed in the MIDI (or audio) callbacks. It tells the interpreter to store this in a fixed size container with faster access times:
If you have a script with lots of variables, the interpreter must search the entire array for every variable access (so the 23 - 40 ms are depending on how many other variables are defined in the script while the access time to reg slots stay the same).

It's also possible since you're storing them in an object rather than as direct references that const gives no performance benefit. But it's still good practice to use a const here. It makes it clear to other developers who might see your code (or your future self) that this variable is not meant to be reassigned, and it also prevents it being reassigned accidentality.

@d-healey Cool, thank you so much! Let me give it a try

We've made it this far....

Screen Recording 2025-11-23 at 1.11.25 PM.mov

@d-healey Mainly because the default method of showing the octave numbers doesn't really work for small and large key sizes, but also partly to avoid using LAF. 😜

Since I know I'll want control over octave numbers in every plugin I create - and I probably won't want to override anything else about the already-very-nice-looking keyboard - it made sense to me to bake it into HISE rather than using LAF every time.

@Lindon Thank you so much 🤞🏻

@d-healey I'll have a look at that thankyou. I may have set it/not set it correctly from one OS to another maybe

@duma figured it out

@trillbilly The plugin should have permission

@dannytaurus Thank you! This is excellent advice and helps a lot, if you don't mind - i'm going to message you privately!