Hard Clipper

[Christoph Hart]

What's tree best way to share a project with SNEX?

Yeah that's been nagging me for quite some time as I can't embed the SNEX code into the snippet for reasons I already forgot. I'm usually ending up pasting the entire SNEX code along with an example snippet and let the poor reader assemble it manually (the advantage of this is that it makes the SNEX code readable in the forum).

[DanH]

@Christoph-Hart I'm trying to export the project @Dan-Korneff posted above. I've followed instructions on how to compile the SNEX node for export from this thread: https://forum.hise.audio/topic/4364/snex_node-needs-to-be-wrapped-into-a-compileable-dsp-network?_=1683724590086

So:

• set 'Allow Compilation'
• Select SNEX node and Wrap into Compiled DSP Network
• Reload project and choose Export -> Compile DSP Networks
• reload project and select Export -> Export as FX Plugin

However I run into the 'Snex_node Needs to be wrapped into a compilable DSP Network' error every time.

@Dan-Korneff suggested this is an existing bug with the SNEX Shaper node?

[Matt_SF]

@DanH if you 'allow compile network' you don't need to wrap the SNEX node. You need to do that if you don't compile the entire network.
It's either one or the other but not both.

[DanH]

@Matt_SF ok thanks, well doing it or not ends up in the same place. My node looks ok I think, the green icon is 'on' as it's meant to be...

Any chance anyone else can test?

[Dan Korneff]

@DanH I'll try to redo with the SNEX node today. That should work

[ulrik]

@DanH I get the same "Need to be wrapped...." stuff as you

[DanH]

@ulrik Thank you for testing :folded_hands_light_skin_tone:

[Matt_SF]

@DanH @ulrik it's working well here. If you first messed up the DLL compilation, maybe try to redo it in a new project folder (to start from scratch).

@Dan-Korneff well done, it sounds nice :thumbs_up:

[Dan Korneff]

@Matt_SF Wish I could take credit. This is a variable clipping equation from 20 years ago.

[Matt_SF]

@Dan-Korneff well, old doesn't mean bad, so thanks anyway

[DanH]

@Matt_SF just tried in a new project and get the same result...

I get this error message in the dll compilation though, but says process completed and there's a dylib file created and the node looks correct in Hise...

DLL_EXPORT scriptnode::Error getError()
                             ^


▸ Compiling RNBO.cpp
▸ Linking CLIPPER.dylib
▸ Build Succeeded

Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Process completed]

[DanH]

@Matt_SF so you managed to export the project as a plugin?

[Matt_SF]

@DanH yes, it's working just fine. I don't know why it won't work on your computer.
These are the steps I followed (as usual actually) :

• new project, create a scriptFX module
• create a snex_shaper node
• create a new file called "snex_shaper"
• create a new parameter called "soft/hard"
• copy/paste @Dan-Korneff 's code into it
• set allow compilation to "enabled"
• Done

I'm sure you know how to do it though...

If the snex node doesn't work for you, and you still want to use it, try to use a Math.exprnode and put the algorithm @Dan-Korneff used in the SNEX code in it.

[Dan Korneff]

@Matt_SF I get the same issue here when I try to export a plugin after compiling the network .dll of a SNEX Shaper node.

[Matt_SF]

@Dan-Korneff you must not wrap the snex_shaper node, simply leave it as it is and compile the dll :

[Dan Korneff]

@Matt_SF I thought all custom SNEX nodes needed to be wrapped? ‍️

[Matt_SF]

@Dan-Korneff actually, if you want to keep the bare scriptFX module in your project (and in your compiled plugin), you have to :

• disable 'allow compilation' of the network
• wrap the SNEX / expr node
• compile the dll
• compile your plugin.

If you want to use a hardcodedFX in your project (and in your compiled plugin), you just need to :

• enable 'allow compilation' of the network
• compile the dll
• compile your plugin.

(> don't wrap the SNEX / expr node for the 2nd solution)

Edited

[DanH]

@Matt_SF I've tried both ways and still get the same error!

[Matt_SF]

@DanH did you retry in a new blank project ?

[DanH]

@Matt_SF I did, I'll try with most recent commit. Maybe I'll also try with exp node before that actually....