@Christoph-Hart No, none of my parameter names have whitespace characters. Here's the network I'm trying to compile:

DynamicEQ is another compiled network. It's working well when I have a fixed number of clones, but if I try to make it dynamic like this the compilation fails.

I have created a script FX which uses a clone node. The script has a number of parameters which are forwarded to the clone child, and a clone cable.

I am trying to make the number of clone nodes variable by adding a parameter to the script and connecting that to the NumClones parameter on the clone node.

It looks like it works in the designer, but when I try to compile the script node I get an error:

Should this be possible? Is there something specific I need to do to get it to compile?

Thanks!

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 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?

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

Thanks everyone. I've got HISE building as part of the pipeline, and I can cache the results of that step to speed up subsequent builds.

@Christoph-Hart Is there an example of a script that builds HISE from source code via the command line?

@d-healey No worries, I was hoping I could extract the executable from the official installer from a CI pipeline without any user interaction but I will find a different approach.

Or failing that, to extract the executable without running the full installer?

@d-healey looking at the code, I see that the command line export_ci reads the UseIPP setting from HiseSettings, and according to this https://github.com/christophhart/HISE/blob/cd51dc7bc8d5f539184a4308b41c6b5cabc2aaaa/hi_core/hi_core/HiseSettings.cpp#L1191 it defaults to enabled.

The only place I can see to override that is in the compilerSettings.xml file under /Users//Library/Application Support, which is the file that is updated when you change the setting in the UI. I don't see a way to override it from the command line.

So my guess is, you have disabled it on your build machine and that works because you use the same machine each time. Whereas in the devops pipeline it starts from a fresh install with no compilerSettings.xml file, and therefore defaults to enabled.

@d-healey it sounds like your script is running on the same box each time? I'm using Azure devops pipelines, so it is a fresh Mac agent for each run.

I got it working by manipulating the projucer file before running the build script - to set USE_IPP=0 and remove the extraLinkerFlags, but it's not particularly elegant. Would be better if I could figure out how to set the export_ci command line to disable IPP in the first place.

@d-healey My build pipeline is downloading the latest stable release from https://github.com/christophhart/HISE/releases/download/4.0.0/HISE.4.0.0.dmg and extracting it to a subfolder in the HISE source path rather than building the development branch. I thought that would be quicker and simpler than running the whole HISE build every time. Is that a problem?

@d-healey this is a remote MacOS build agent which is installing from the base OS for each run, so I can't set it via the UI.

I tried appending -D:USE_IPP=0 to the export_ci command line options, which allowed the compile to complete, but now the linker is failing with the following:

clang: error: no such file or directory: '/opt/intel/ipp/lib/libippi.a'

clang: error: no such file or directory: '/opt/intel/ipp/lib/libipps.a'

clang: error: no such file or directory: '/opt/intel/ipp/lib/libippvm.a'

clang: error: no such file or directory: '/opt/intel/ipp/lib/libippcore.a'

The thing is, I'm not passing -ipp on the command line but the build is failing with this error on the build agent:

/Users/runner/work/1/s/HISE/hi_tools/../hi_streaming/hi_streaming.h:74:10: 'ipp.h' file not found

I'm assuming it's because the script is installing HISE fresh on the agent and the UseIPP setting is defaulted to on?

I know that this configuration property is saved in compilerSettings.xml under the users Application Support folder.

Is there a good way to set this when running HISE from the command line as part of a CI script?