@Lindon Thanks so much. I assumed the forking suggestion wasn't the right move. It's so good to have such a great community with people like you and Dave H. providing expert support. I haven't yet communicated with Christoph but the experience using HISE as a newbie, truly shows how a community like this is a formidable asset
Thanks again.

@David-Healey Thanks. Once I removed IsPluginParameter from all sliders the interaction is gone. Before I removed it from all it interacted with the next one. As I understand, this will eliminate writing DAW automation for the controls. I guess I can start this way and hope for a fix in the future. Should I report it under bugs?
In any case thanks for the help. I did enjoy your Bootcamp and hope to use HISE successfully and start scripting soon.

@Jeetender It will remove DC. Technically DC is 0hz thus HiPass filtering the lowest frequency i.e. 3,4 or 5Hz will effectively remove the DC.
However, it will introduce phase differences similarly to an all pass filter, thus subtracting it from the original will leave audible residue. That should be Okay and is just like any HiPass based on IIR. You can use an FIR, however to be phase linear it'll have to have a fairly long delay.

@Jeetender It will remove DC. Technically DC is 0hz thus HiPass filtering the lowest frequency i.e. 3,4 or 5Hz will effectively remove the DC.
However, it will introduce phase differences similarly to an all pass filter, thus subtracting it from the original will leave audible residue. That should be Okay and is just like any HiPass based on IIR. You can use an FIR, however to be phase linear it'll have to have a fairly long delay.

@Lindon Thanks so much. I assumed the forking suggestion wasn't the right move. It's so good to have such a great community with people like you and Dave H. providing expert support. I haven't yet communicated with Christoph but the experience using HISE as a newbie, truly shows how a community like this is a formidable asset
Thanks again.

Hi, I'm using the HISE Delay in a VI and the Delay time non temposync goes to 20000ms however it seems that beyond 1.5 seconds there's no difference in the heard delay time.
Thus, I was consulting with Claude who suggested that the Delay module's internal ring buffer is hardcoded at 65536 samples — and that's how much audio it can actually remember. To overcome this, it suggested we fork HISE and change the Delay buffer.
Before I go down such a path, is this a correct approach?
My general wish is to continue and flow with HISE code where if I make changes They are introduced to the whole HISE community of users. It does puzzle me why the maximal delay time is so different than what's displayed, to me it seems like a bug.

Why would the HISE delay time knob reach values way longer than what it's capable of and effectively delay by much less?

Is the Delay internal buffer indeed 65536 samples? Where could have Claude found this information?

If the answer is yes, the buffer is hard coded and you can indeed fix this in the HISE code, should I fork HISE or should I introduce the fix in the main development branch?

Thanks for any attention on this.

@David-Healey Thanks. Once I removed IsPluginParameter from all sliders the interaction is gone. Before I removed it from all it interacted with the next one. As I understand, this will eliminate writing DAW automation for the controls. I guess I can start this way and hope for a fix in the future. Should I report it under bugs?
In any case thanks for the help. I did enjoy your Bootcamp and hope to use HISE successfully and start scripting soon.

@David-Healey I did build it from source, however that was a while ago. Since it did work and build a good plugin I wasn't suspecting the HISE build to be the issue.

Newbie here. I managed to create a nice plugin with a single sampler and a few FX.
Created a bunch of sliders to control the FX and all went well and a good plugin was built and all looked promising. It still works.
Going back to the project to refine the GUI with some knob filmstrips strange things started happening. 2 sliders connected to MACROS 1 & 2 started controlling other sliders.
I'm with HISE 4.1.0
Even if I load the project and the XML that I thought I saved before building the good plugin the Interaction continues and eveything I try just move the interacted slider from one to another.
Quite frustrated and I just don't know what to do. Thinking of starting from scratch...
Anyone has any idea?