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

@Christoph-Hart oh awesome! Thanks!

AGI my ass…

Lol very true 😆

@Christoph-Hart Amaaaaazing! Thanks Chris 😎

@HISEnberg said in Third party node modulation output slot:

@ustk nice I basically setup the same system but just using HISE’s version of get/setLatencyInSamples. I’m assuming you are using the JUCE version of this in the C++ node? I believe HISEs API is exactly the same but I could be wrong.

Well my use case is different, I just compute my inner DSP latency for dry/mix situation in a split node, not reporting the whole latency of my project to the DAW...

Regarding what @Christoph-Hart and @griffinboy are saying, could oversampling help here?
Despite the fact it'll eat up some more CPU, of course...

@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