ScriptNode setup

[toxonic]

hello forum,
i'm trying to export a scriptnode as cpp module, like mentioned in the documentation.
according the scriptnode documentation, the following things have to be done:

"Recompile HISE
Open the projucer file of HISE (either the standalone or the plugin project), change the compile flag HI_ENABLE_CUSTOM_NODE_LOCATION in the hi_modules module and recompile HISE:"

But in the projucer file, the hi_modules section looks like this:

Where should i put that flag, mentioned above?

[d.healey]

All this custom node stuff you're looking at is for importing custom C++ as nodes, that's not what you want.

Just go to Export > Compile DSP networks as dll and any networks in your project that have allow compilation enabled will be compiled into a single dll.

[toxonic]

@d-healey
Ah, okay.... but i'm a bit confused about that:

I thought, it would be possible to compile single networks as a kind of node, which i then can use in other projects (maybe i misunderstood that, i thout that was, what "metanodes" meant) . Is there a way to do that?

If i compile the networks in a single file, what advantage does that have?

I compiled a "test" network, but when i restarted hise, i could not see a difference. Does hise automatically load the compiled version of the network, when i restart the project?

Where can i enable "allow compilation" for a network? I can't seem to find it in the Network Properties.

[d.healey]

@toxonic To use a network in another project you just copy its XML from one project to another.

Compiling to a DLL will usually result in the network using less CPU. It will also make it available in the Hardcoded fx - which is essentially an fx slot for script node patches.

I think the option is in the network properties, you can also set it in the XML directly. In network properties you need to first deselect all nodes, I think.

[Lindon]

@toxonic - right click on the node - the properties show up :

enable "AllowCompilation"

[toxonic]

@d-healey said in ScriptNode setup:

It will also make it available in the Hardcoded fx - which is essentially an fx slot for script node patches.

Mhh, i can't seem to figure it out. I just compiled the "test" network via the generated shell script (after hitting "Compiling DSP networks as DLL") and it was build without issus. I can see the file in /DspNetworks/Binaries/dll but when i restart HISE, i have the choice between "Hardcoded Master FX" or "Hardcoded Polyphonic FX". In both cases, the dropdown menu tells me "No Network". What am i missing?
i'm feeling stupid, asking that much questions, but i can't find any ressources or tutorials on the internet... any hints?

I think the option is in the network properties, you can also set it in the XML directly. In network properties you need to first deselect all nodes, I think.

Silly me, i meant, i can't find the option in the Node Properties. Where can i find the Network Properties?
How could i enable compilation within the XML file?

Sorry for all these questions and thanks for your help. :)

[d.healey]

@toxonic

[toxonic]

@d-healey and @Lindon
Oh my goodness, that took some doing! ;-)
Thank you, for you quick responses!

Just one more question: In the HISE preferences you can set a "custom node path" , which is meant to store "additional nodes". What's the purpose of that folder?

[d.healey]

@toxonic For importing external c++ as nodes