@HISEnberg Yes exactly! Since Hise is an instrument and PluginDoctor can only run FXs, you need to interface it with MetaPlugin first. You just get a warning in MP because Hise is still an instrument but just ignore it

So it appears I should use a stack with the insert method instead. Mistake in the doc...

Oh in fact I guess I should better make a midi sequence and get the rectangle list...

@Orvillain nice! Do you stick it on release as well?
EDIT: getting a compilation error for release because of the snippet browser.

I just saw this new thread... :-)
Here's some info for you that I noticed recently:
If you use the content callback of a table as follows:

Table.setContentCallback(tableCallback); inline function tableCallback(i) { // Your code }

i returns the index of the point that you control from outside, for example from a panel or a slider.
This was very useful for my use case.

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 👍