@Taihongcraft But the node within a soft bypass node

@ustk aaahhhh here you go! haha. I gotta see this...brb.

@Rognvald You can put it all in the interface MIDI processor if you want to keep things simple - just avoid doing any UI stuff in the MIDI callbacks.

// This sort of thing should be avoided in a non-deferred script. Buttons[index].setValue(true); Buttons[index].changed();

However the ideal situation is you separate UI logic from MIDI processing by using separate processors for individual tasks.

You can add the velocity code I described above alongside your current script.

Those reg variables you have should most likely be const. Rule of thumb is if the values are fixed (or it's an array or object) use a const. If the value is going to be dynamic then use a reg.

@dannytaurus said in Quick performance question:

but say I had 100 wavetables that the user can choose between.

At this scale I think there will be significant overhead for all the extra modules, and it will be more logistically complex from a scripting point of view. I would try to use as few modules as possible.

@iamlamprey Looks like the value is being normalized somewhere.

@CatABC Is it necessary to repeat the KS code in the two separate scripts? Can it not work with a single key switch script and a couple of MIDI muters? That might simplify things.

@ustk
Thanks for your help. I set the AllowCompilation flag in the DSP Network’s properties, compiled the network, and exported the DLL. The effect now works — but I’m still getting the prompt:
“You don’t need to wrap the root node. Just tick the AllowCompilation flag in the properties, save this network and export the DLL.”

Do you know why the prompt keeps appearing even after I’ve done that?
I appreciate any guidance.
Thanks again!

Best,

Capture d'écran 2025-11-08 013223.png Capture d'écran 2025-11-08 014654.png Capture d'écran 2025-11-08 175324.png

@ustk Awesome! 😂

@Dan-Korneff Did the same, seems robust enough 👍

@ustk Thanks for the pointer. I added another commit other than the PR to ensure the new props are shown in the Data section of the UI.

@Lindon I havent gotten that one much before. I get whats happening now. 🙏

@Oli-Ullmann By "free-running" I mean not reset on NoteOn events. And yeah, I found the IgnoreNoteOn parameter right after my last post 😂

Thanks anyway! 🙌

@d-healey
Yes, that's right! Thanks for the tip! :-)

@Orvillain Have you enabled the global app data folder on MacOS in project preferences?

@d-healey thanks. I ended up going back to Globals and FixObjectArrays as Im actually using values all over the place...., it makes me shiver a bit but hey .....