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

@d-healey yeah

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

Hey @Orvillan,

No big deal if I didn’t know how to post a snippet. Better to ask than mess around blindly, right? I’m really new to coding, mostly picking it up bit by bit.

I love making my own tools and plugins, experimenting with sounds, and sharing my stuff for free with the community. I started with Synthedit, but it’s not really modernized, so that’s why I decided to switch to HISE.

Honestly, I’m mainly a music producer, graphic designer, and sound engineer, and I want to put all of my passions together to create the plugins that I want to make. Since coding isn’t one of my skills, I have no choice but to learn it step by step to help me further with plugin development, since HISE requires some coding knowledge to work around.

@Christoph-Hart Thanks, I just don't know how to make my problem noticed, it doesn't bother me, but I had no other way out. I could write to you in private messages, but that's even worse than doing it in another post. I heard you, thanks again, and sorry again!

@Christoph-Hart 😂😂😂

@d-healey Thanks David - that worked and I was able to compile the DebugWithFaust version and run it....
Now to try a ReleaseWith Faust.....
Thanks again for your time, help and patience 😁

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

@Christoph-Hart Bump bump

@weezycarter make a minimal test plugin with 4 channels. Then we'll have a baseline.

@Rognvald No problem 🙂

This is a bit cleaner:

inline function onButton6Control(component, value) { if (!value) { return; } // works the same as if (value) but the scope is a little bit cleaner local Knob1_value = Math.randInt(20, 20000); // this is already fine local Knob3_value = Math.random(); // you don't need range here, Math.random() is already within the range you're expecting Knob1.setValue(Knob1_value); Knob1.changed(); // these can be single lines if you prefer Knob3.setValue(Knob3_value); Knob3.changed(); }; Content.getComponent("Button6").setControlCallback(onButton6Control);

If Knob1 and Knob3 already have their own Control Callbacks, you also don't need to independently call these:

SimpleGain1.setAttribute(SimpleGain1.Gain, Knob1_value); // already handled by Knob1.changed(); SimpleGain2.setAttribute(SimpleGain2.Gain, Knob3_value); // already handled by Knob3.changed();

Control.changed() is essentially simulating changing the control with the mouse, so you're basically calling the setAttribute function twice.

@Chazrox me that I'm confused 😁