Scriptnode export issues

[crd]

@danh I can't be much help. It must have something to doing with compiling the dll file because my scriptnode stuff is exporting well, without creating the dll. Maybe raise an issue here so Christoph will see it?
https://github.com/christophhart/scriptnode_testsuite

[DanH]

@crd yep exporting without the .dll is fine. Some people seem to be exporting their plugins with .dlls though, I'm just confused as to how lol

@dustbro are you exporting ok with .dlls?

[d.healey]

@danh said in Scriptnode export issues:

Some people seem to be exporting their plugins with .dlls though, I'm just confused as to how lol

I think there is a misunderstanding here. When you go to compile your scriptnode network it doesn't just compile the network you have open, it compiles all of the networks (xml) in your networks folder that have the compilation flag enabled and puts them into a single DLL. If any of those networks has a bug or is uncompilable for some reason then the compilation will fail.

So you need to test your networks one by one to make sure they compile successfully. Those that you don't want to compile must have their compilation flag set to disabled.

[DanH]

@d-healey I put a reverb in a container - basically as simple an effect as I could, to make sure that there wasn't this issue.

[d.healey]

@danh If it's a convolution reverb it's uncompilable.

[DanH]

@d-healey it's not and I tried with a simple chorus yesterday

[crd]

@danh It seemed like yesterday you were able to compile a dll for something ?

The process is definitely finicky. My goal was only to get a version of my project exported for someone I am working with, not to optimize it yet by compiling a dll of the scriptnode network. One thing I was missing (which may or may not be helpful to you) is each part that needs to be wrapped has to be wrapped individually. I.e if you have two timers in a container, each must be wrapped separately. Each wrapped file get's it's own xml file which the network file references. The network refers to all the xml files in the hise dsp network folder, regardless to whether or not they are actually present in your instrument and it will try and compile everything that you haven't manually marked to not be compiled. Definitely tedious but not impossible.

[DanH]

@crd yes I compiled a dll yesterday and today. Compiling doesn't seem to be my issue (one less thing to worry about!) - it's exporting a working plugin that's the problem.

Since I tried with the most basic fx I could do, I'm going to rule out wrapping with wrappers (if that makes sense!).

I see the timer is a SNEX node, which I think all need to wrapped.

In my project I seem to have the option to wrap two containers. Hard to know whether I should or not!

[crd]

@danh So, all of the plugin exported to standalone are crashing when you open them?

[DanH]

@crd yes

[crd]

@danh dumb question, they work when there are no scriptnode stuff in them?

[DanH]

@crd they only crash if I compile the scriptnode stuff to a dll. Otherwise it's fine, scriptnode fx (not dll) all good in the exported plugins

My mose basic test is just a waveform generator plus a script fx with only a chorus node inside. Nothing else in the project.

[crd]

@danh got it. I have no idea ...