@d-healey @Christoph-Hart And I just added two more 😆
The forum was just giving me a 503 error for an hour, I think it was acting against... ME AS A PERSECUTED PERSON!!!

Yeah alright, I divided the connections into 4 sub groups... I don't intend to modulate them though so all good 👍

@ustk ah yes that's an easy fix.

@ustk Mmm... loading the only network I have with a dynamic blocksize node in another project works...

@Christoph-Hart Strangely it does not happens all the time, I can't reproduce it with a smaller network, but it's usually happening with bigger networks (to be confirmed)

Although a similar issue is when you undo:

sdfgh.gif

@ustk think I've been having the same, will check in the morning

@Christoph-Hart Not a big deal, but as soon as you use sub groups, it forces you to do so for all parameters which you might not want...

@HISEnberg Well my fear wasn't if it work or not in the network and in Hise in general but I reckon a compilation issue with those warnings...
So if no issue with that, perhaps it would be easier for you @Christoph-Hart to just put a message in the range popup or anything telling the user not to worry about.
A warning is here to make you shaking and to remind you that the abyss is closer than you think... 😱

@ustk Infinitely better solution:

fmod(input*3.0, 1.0)

@Christoph-Hart I know you're working a lot on this, but just to know before going further in my new project, would the intensity limitation be achievable or should i rely on a different approach?
I am currently using global_mod nodes but I need a new duplicate of the whole modulation container for each parameter i want to modulate, which becomes insane, not talking about the UI implementation 😨

In the context of an FX, not an instrument...