@Christoph-Hart The plotter looks very rough... Are we able to get a better resolution?
It even looks like the resolution is not the only problem but the path construction itself... a stride value not optimised?

Screenshot 2025-11-10 at 13.37.27.png

@dannytaurus

Multiple wavetable synths will use a lot of memory.
Christoph's WT engine creates mipmaps (multiple antialiased copies of the wavetable).
If you have multiple WTs loaded into separate WT engines simultaneously, each one will have multiple copies of the wavetable.

However, this memory is probably still small compared to say, a regular multisampler... However 100 wavetables is gonna get big I can imagine you could pass the GB mark of ram usage.

Can't speak for cpu, you can try it but I'd assume cpu is okay as long as you don't have the inactive synths do any processing when silent.

If you are trying to acheive clickless swapping or something (idk if the WT engine does this already? Or what your goal is with having multiple WT engines - fast loading maybe??? No silence dropout???)
You could just have two WT engines, keep one silent, and use the silent one to load the new wavetable, once ready, volume fade between them. Then you get a seamless handover to a new engine.

@iamlamprey Looks like the value is being normalized somewhere.

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

@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! 🙌

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

@resonant Not on happening on my end but, perhaps just interfacing a control.smoothed_parameter can help.

@Christoph-Hart 😂😂😂

signal detection = mod output (minus smoothing), so still not clear what's the problem, but glad you solved it :)

@Christoph-Hart need your help. This really needed part for big projects.
https://github.com/christophhart/HISE/issues/798

@DanH said in Table -> Disable deletion by right-clicking:

No, nor me. Having curve nodes would be much more up-to-date. Is there anyone here who could write a new table which can interface with the existing Hise modules (LFO / ShapeFX)? For $$....

Seriously though, can anyone help with this?!

@pcs800 Ah ya it is a little hidden. In scriptnode click the arrows icon next to the parameter (on your compressor). Then right click the parameter and select "Copy range to source" and it will set the Macro control to the same values.

example.png

example2.png

@CatABC ok thank you!!! so it's not only on my end. That's reassuring.

@Lindon OK well after another 1/2 an hour randomly dropping nodes into my network ....this seems to work:

9489b406-9561-4d97-a048-640f3bd31219-image.png

@lijas90 said in OverlayMidiPanel: keep dragged MIDI file saved inside the plugin:

The directory always opens when the script compiles, not when I press the button.

You've placed the command inside onInit. This is the callback that runs when you hit compile or when the plugin loads.

You need to place the command inside the button callback. - Check my YouTube channel, I have lots of videos showing button callbacks.