@d-healey Thanks on. Imma try rebasing Develop for the IDE, and then see about watching Xcode.

@raydonstudio Yeah you're right, the property assignment takes over the script, we all fell into this one day or another... Having an assertion in the console that informs when people are using both might help beginners, @Christoph-Hart ?

@jmannix Thank you for your reply in this thread, @Christoph-Hart — I appear to be having the same issue.

@griffinboy yes it's included within the RTNeural code folder, but it's only available in the translation unit that compiles the RTNeural code (the hi_tools module).

In order to make it accessible on other translation units and your own nodes you have to add this line to hi_tools/hi_tools.h:

#include "hi_neural/RTNeural/modules/xsimd/xsimd.hpp"

The place doesn't really matter, but somewhere around line 150 would be a good spot.

Yes global cables are supposed to work without any special flags, but you have to create the cable in your main script as the compiled nodes do not have that ability.

@Christoph-Hart Thank you. And very cool.

@aaronventure🌈Thanks, mate.

@griffinboy Doing each partial statically will model non-linearity.

@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.

@kameron said in Can't Compile DSP mac M1:

@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

No there were no issue with Xcode 16.2, it was a mistake by Christoph but he has fixed it now
https://forum.hise.audio/topic/11825/commit-ca06fcb-fail-to-export-plugin-on-mac/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).

@kameron No I never solved it, sorry

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).

@Addison-DS faust has most of the DX7 functionality, so you can literally build a DX7 with it
https://faustlibraries.grame.fr/libs/dx7/

@Christoph-Hart Thanks, man!