@Christoph-Hart said in Adventures In ScriptNode - compiling SNEX nodes:

@Lindon Yes, unless they use certain things which prevent compilation:

global cables modulator slots changes to the DSP network using the scripting API

I think there are a few more edge cases, but these are the most important ones. If none of them apply, then you should export the scriptnode network as dll and use the hardcoded modules instead, this bypasses the entire scriptnode data management with its additional data layer and API access.

Ok thanks - good guidance, in passing... what are "modulator slots" here?

Actually I think I may have found the answer in hi_dsp_library/snex_basics/snex_ProcessDataTypes

@Christoph-Hart

Hi there, I'm looking to integrate a 'header only' library, for use in an external c++ node.

I could find no 'src' folder and so I created it, and dumped my source code for the library in there, but that doesn't seem to be enough, as my external node will not compile!

300133a5-fd75-4e4c-80c1-67594212b9c2-image.png

Is there a place I can put my headers, where they will be picked up by scriptnode?

276f1dea-2c09-4166-94c5-86c84a63ea8b-image.png

The autogenerated includes file has correctly transcribed it, but VS is not able to find the thing!

I see this has been fixed now :)

@ustk said in Scriptnode, how to use getNumParameters ?:

@d-healey Isn't the DspModule the entire DSP or the ScriptFX in question?

Possibly. I did try calling the function on other parts of the network and had the same result.

@dannytaurus said in This script processor has a network that consumes the parameters:

We should just use var everywhere and let the parser/compiler sort it out.

😢 Probably true...

@Matt_SF Thank you!

I think its Allpass vs Linear Interpolation, but you can check the stk docs for a proper reference.

Yeah, I realized I was too lazy to copy the code from the Waveform generator over :)

Noted...