Scriptnode DSP Compilation help (again!)

[DanH]

@crd there’s a thread somewhere with a link @Christoph-Hart posted to his GitHub where you can upload troublesome scriptnode projects so he can see if he needs to update that side of Hise. My one wouldn’t work until he’d pushed a commit after I uploaded it there.

I’ll try and find it later on unless you get there before me

[d.healey]

@crd Are you using a convolution node?

[crd]

@d-healey I am not.

I found the right GitHub page to load issues to:
https://github.com/christophhart/scriptnode_testsuite

Hopefully the minimal snippet I made is enough info for @Christoph-Hart . If I am understanding what constitutes a scriptnode network correctly that is the first of 5 similar networks I am trying to compile.

[crd]

Something seems to be wrong with the export process using the latest develop build and I also think I am messing up the wrap/compile process...

[crd]

Okay now I am having trouble exporting simple test math.expr nodes. I am getting many errors in the terminal window.

[Dan Korneff]

@crd send a snip. I'm using Math nodes with no issues.

[crd]

@dustbro One second and I will make a gif. I think that might be more helpful...

[crd]

This post is deleted!

[Dan Korneff]

@crd hmm... the scriptnode network is empty in the snip.

[crd]

@dustbro
Okay, I've been at this too long and making silly mistakes.

duh. Once the node is wrapped the snippet function doesn't work since it's referring to an external file (?).

All that was in the snippet is the math.expr node with the Hise saturation formula in it. It wraps fine but fails to compile. Here are the first few error messages: Here are the first few errors I am getting:

/Users/christopherdammann/Desktop/git/test5/DspNetworks/Binaries/Source/chain.h:36:35: template argument for template type parameter must be a type

using chain_t_ = container::chain<NV,
^~

/Users/christopherdammann/Desktop/git/test5/DspNetworks/Binaries/Source/chain.h:42:55: unknown template name 'chain_t_'

template struct instance: public chain_impl::chain_t_

[crd]

Here is a screen grab of what I'm getting.

[Dan Korneff]

@crd Make sure you use float values for all numbers.

[crd]

@dustbro Good to know but I don't think that is the issue I'm having. I'm either missing something obvious or there is something up with the latest build that is making compiling not work for me. Possibly both :)

It was all working well for me but I can't remember what build that was.

[Dan Korneff]

@crd Are there any other dsp networks in your dspnetwork folder?
I'm able to compile the math.expr node here.

[crd]

@dustbro I've been trying in a fresh project.

I will start a new thread so I don't high jack this one any further.

[DanH]

@crd feel free to hijack the thread! It's all totally relevant anyway.

So when I 'Wrap into DSP Network' I get a copy of the Script FX (see image). Is that right?

Also the box in this picture 'Create an Embedded Network' - What does that do that's different to starting a new one?

[crd]

@danh I get the same duplication. I'm not sure if it's intentional.

Embedded puts the scriptnode dsp in the project itself rather than create a network file that you can share between projects ? I think it's intended for prototyping. That's my best guess. :)

In the latest build it seems like things that didn't need to previously be compiled like timers now need to be compiled... I'm pretty frustrated. My project used to export fine but now no luck.

[DanH]

@crd yes the whole thing is super frustrating :face_with_tears_of_joy: It can add so much to a plugin but take so much of your life !

[DanH]

@danh I mean I just rebuilt my script fx from scratch, wrapped it into a DSP Network, unloaded it, tried to reload it from the menu and..... crash!

Try to re-open project... crash!!

[crd]

@danh I am having so many crashes it's hard to pinpoint what's what. Sometimes I can wrap and then open the compile dialog (which then fails in terminal). Othertimes after I've wrapped a node then project then crashes immediately when choosing compile all dsp. Previously I worked around this by just removing everything that needed to be compiled but now it seems like more things need to be compiled in order to export vsts.

@Christoph-Hart any ideas about what's going on?