Compilation error on dsp network with clone node
-
I have created a Dsp network using a clone node and clone_cable. However, when I come to try to compile it I get this error.
Can anyone help point me in the right direction to fix this?
/Volumes/External SSD/Hise/HISE/hi_dsp_library/node_api/nodes/duplicate.h:172:15 Reference to non-static member function must be called
System Details: Apple M1 / MacOS Sequoia / 15.3 / HISE Version 4.1.0 / Standalone
-
@jmannix Might be related - https://forum.hise.audio/topic/11919/global-cables-flag
-
@jmannix there's a few tricks to get the clone node working properly. First is to always have the number of clones (voices) as your first macro control in scriptnode. The second that comes to mind is basically do all of your processing in a seperate scriptnode network, compile it, then embed that within the clone container. This is far less error prone on compilation.
So for example, if you are making a delay that you want to clone with different delaytimes, make a seperate scriptnode network for just the delay. Compile that network, then embed that within the clone container. Hopefully this is clear and helps with the issues your experiencing, might help if you can share a snippet.
-
@HISEnberg I tried your suggestion of embedding a compiled network in the clone container, but as soon as I try to do that HISE crashes with no error
Actually, if I add a ScriptFX to the module tree for the network containing the clone node then it allows me to add the compiled node as a child.
Is there a way to work on multiple nested networks without having ScriptFX nodes for them in the module tree?
-
Good news! I got it working. It involved a lot of stripping it down and building it back up little by little, saving and compiling with each step. I had a lot of trouble with HISE crashing and compilation errors, but I got there in the end. Thanks everyone for the help!
One thing that helped me was adding a container to the project and putting ScriptFX nodes for the compiled networks in there so I can open them up easily.
-
@HISEnberg said in Compilation error on dsp network with clone node:
This is far less error prone on compilation.
That is a terrifying statement.
-
@jmannix I can't do this any more.