@JeanC
I don't think scriptnode currently support that...
If your're writing something like a plugin host, you could take look at the audio plugin host in JUCE source code.
@HISEnberg@Lindon Thank you guys for the help! I just re-built the latest HISE on a different Mac which is M2 and is running an older version of MacOS and it is running Xcode 15.3. The compile worked on there. So, I am assuming is must've been an issue with Xcode version 16.2
@HISEnberg no folded nodes are not rendered (anymore).
I found the graphics performance of scriptnode to be pretty much on par with what my eyes can parse. If the network is getting too big with too many cables, the framerate drop is a nice nudge to reorganize stuff (the tools are there).
All control nodes which are stateless (eg. the cable_expr node) are automatically polyphonic, but the others should have dedicated support for polyphonic states.
I just checked in the source code and the input_toggle does in fact only have a monophonic state, but the compare node should be polyphonic. However I just realized that the wrapper code doesn't propagate that info to the UI to show the [poly] suffix like with the other nodes.
So:
input_toggle is polyphonic now
all control nodes properly show the [poly] suffix (it shouldn't have affected functionality though, was just an UI glitch).
@ulrik Ok I found what was causing Hise to freeze, it was my "node templates" that I made the other day, I removed them and now it seems to work again.
Can you tell me what is different about jdelay from core.gain
Not sure what you are asking here. One is a delay and the other a gain, but you know this already ☺
Lol, I meant core.delay.
Hmmm… seems a bit technical for users, no? Many of them are not necessarily confident enough with interface buffers length, so understanding internal blocksize might be confusing… (not trying to be pedantic here)
Good point - I don't make commercial plugins with HISE; they're functional prototypes for other developers and research. Also, I can use the pop-ups myself to easily try different values, and then go back change the dynamic ones to fixed.
There's also a bug where if you add another parameter to a faust node which already has it built, you have to manually rebuild the parameters by clicking the three dots (where you create a new Faust file) and you'll find the option there.
Well, I rebuilt the whole thing and haven't compiled the network and it's working again. Not exactly endlessly repeatable though. I'll have to pull the C++ apart when I get time......