@Morphoice if you want a more detailed error message try opening the generated AutogeneratedProject.jucer file from the DSP Networks Binaries Folder.

You can then compile this file as you would compile HISE in VSCode or XCode. This usually yields the correct error message.

Thanks, @sletz, I am aware of the attach primitive. The problem is that no metering signals are available in HISE when the dsp network is compiled.

@Christoph-Hart thanks! I just totally forgot the modulation container exists for these cases!

BTW you can optimize the wet path like this:

99dfcf6c-6697-40ef-b4bb-8dcad3e21327-image.png

Use a multi container, this will automatically split up the stereo channels into LR (the mul node does nothing and the jdelay delays the right channel only. If you don't modulate the delay time you can set the limit to the exact value of the delay time parameter - this will save some memory because the delay won't allocate as much (in this case it's 1-2MB of memory).

@ustk Thanks again for your help! I dove into this and am trying to figure out how I can display it Vertically instead of Horizontally. I've got my samplers stacked vertically on the UI and would like the Xfader Visualizer Panels to display on the sampler it corresponds too. Is this possible?

Or maybe even possible to have it light up buttons instead of panels? Like a small LED "Clipping" style button. Just thinking out loud here...

@Soundavid Thanks, I'll give it a try

@Christoph-Hart @Adam_G haha I don't know if I could have found this one 😂

@Christoph-Hart Ok, I've got it working in the Snippet.

In another project, Im using a Global Modulator to build the Network. Does this matter? I've got my project set with 4 Stereo Channels yet I can only get 1 to show in the Network.

EDIT: I decided to not be lazy and just try it. It seems that was the issue. Switching to Script FX or Global Modulator works.

@Matt_SF Thanks, I'll play around with this

@d-healey this is for copying nodes inside a network. If the clipboard contains one of these snippets, it will show an item in the node popup that will create a new node based on the clipboard content:

6bedc52b-45c2-48a2-836d-822ecf0f8ffe-image.png

The import from snippet function in the scriptnode "homepage" isn't functional yet (and it's a bit useless because you can just import a HISE snippet with a node which is why I never bothered implementing it).

@Matt_SF you really just need to delete the network xml file and I‘d rather let this do the user manually.

Not sure why this should crash, however it might be the case that when you delete a xml network that is still compiled in the dll it will cause issues, so just recompile the dll after you deleted a file.

@Christoph-Hart that's a funny one 😂

@Matt_SF @Christoph-Hart is there any solution to this? I am currently hitting this limitation and I do not know how to work around this.

@Christoph-Hart Any update on this fix?

@Dan-Korneff Thank you Dan! A bit of theory never hurts :)

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