Linking parameters to SNEX

ustk

@Fortune the parameters are taken by the function:

template <int P> void setParameter(double v)

where P is the parameter index
You might want to use an enum, but it isn't mandatory

Fortune

@ustk Thank you so much, I will check it.

Fortune

@ustk

Adding

template <int P> void setParameter(double v)
	{
		Driven = (float)v;
	}

Solved the parameter link issue. Thank you so much.

orange

@ustk I just wanted to try this snex network compiling with @Fortune s code. What I do is:

Insert a Script FX > Create a new DSP Network File

Then this procedure:

Terminal says "success" but It throws an 'getError' has C-linkage specified, but returns user-defined type 'scriptnode::Error' which is incompatible with C [-Wreturn-type-c-linkage]error, you can see it in the video. Also I can't see the compiled DSP network in the scriptnode.

What is the missing part?

ustk

@orange Well, I'm playing with SNEX sometimes but never exported anything because there are so many reported bugs that are still not fixed... I got a major project that needs DSP/SNEX pending for more than 2 years, but in the waiting I focus my attention on other projects that don't need DSP because I'm not confident at all it'll consistently work for marketable projects one day...
Guys who don't release sample based plugins are still the poor children of Hise

Dan Korneff

@orange it could be a bunch of things. Did you wrap the SNEX node in a DSP network? Also, remove any unused parameters from the main container.
I'll try to make a full video on how to implement this dsp tonight.

orange

@ustk said in Linking parameters to SNEX:

Guys who don't release sample based plugins are still the poor children of Hise

Yes unfortunately. But fx stuff is much stronger than it seems

orange

@dustbro said in Linking parameters to SNEX:

Did you wrap the SNEX node in a DSP network?

What I do is Create a new DSP Network File ? Is this wrapping? This is another short video about how I start.

I'll try to make a full video on how to implement this dsp tonight.

A video would be great and would bring some light to this dark area :)

Matt_SF

@dustbro always getting some errors here but a video about a full working process would be awesome :folded_hands:

@orange in the meantime you'll find some info here : https://forum.hise.audio/topic/4364/snex_node-needs-to-be-wrapped-into-a-compileable-dsp-network
As Christoph explains, you select the SNEX node and click on the small 'cube' icon to wrap it in a DSP network :

alt text

orange

@Matt_SF

	float Drive = 0.1f;
	float getSample(float input)
	{
		return Math.tanh(Drive*input)/Math.tanh(Drive);
	}
	
	
	template <int P> void setParameter(double v)
		{
			Drive = (float)v;
		}

For the above code, I get bunch of errors below:

❌  non-type template argument is not a constant expression

        using FixBlockType = snex::Types::ProcessData<NumChannels>;
                             ^

❌  type 'int' cannot be used prior to '::' because it has no members

                if constexpr (T::hasCompileTimeSize())
                ^

❌  static_cast from 'snex::Types::InternalData *' to 'int *' is not allowed

                return *static_cast<T*>(this);
                ^

❌  type 'typename node<instance<1>>::MetadataClass' (aka 'int') is not a structure or union

Matt_SF

@orange I would love to help you with that but I'm not that advanced
Maybe try to write your saturation formula in a Math.exprnode, wrap it and see if HISE manages to compile it into a DLL, or if it throws some errors again.
Won't help you much - depending on what you want to do - but it might be useful for debugging purposes...

ustk

@orange Since you don't seem to place your node inside a frame2_block, you don't need the processFrame function so remove it and test if it works...

Fortune

@dustbro said in Linking parameters to SNEX:

I'll try to make a full video on how to implement this dsp tonight.

Hey @dustbro, have you got a chance to do it? Following, please :)

Dan Korneff

@Fortune Not yet. I got a little jammed up with the "day job" :beaming_face_with_smiling_eyes:

Dan Korneff

Finally had a second to make a quick video. I apologize for the poor quality and zero planning... but you get the idea

Matt_SF

@dustbro Awesome, man ! Thank you very much for taking the time to do it.
I'm usually facing errors while compiling wrapped nodes, but I'll review my process and report back if I find what I was doing wrong.

Edit : wrapping and compiling dll is working fine here. (Tested with SNEX and Math.expr nodes).
So clearly I was doing something wrong... I just have to find it out.

orange

@dustbro That's very helpful, Thank you!

Dan Korneff

FYI I tried the same code in SNEX shaper and got compiling errors. I think something is wrong with that node.
I was previously able to compile shaper nodes so I'll take a closer look at what's going on.

orange

@dustbro said in Linking parameters to SNEX:

FYI I tried the same code in SNEX shaper and got compiling errors. I think something is wrong with that node.
I was previously able to compile shaper nodes so I'll take a closer look at what's going on.

Yes, that's what I've got the above errors I posted were in the snex shaper node. That node has definitely got some issues. But will try in normal snex node too.

Matt_SF

@dustbro Again, thank you for putting us on the right path :)

I made some tests and found out some things, so I'll leave that here if others are also having problems wilth compiling the DLL.

What I did before, and what generated error when compiling my networks : I always enabled "Allow compilation" of the whole network >> this generates errors. You only wrap and compile into the dll, the nodeor the chain containing the graph. ( @DanH )

I tried to compile more complex networks, but some nodes seem to throw errors during the DLL compilation process. (i.e. the xFader.node).
Also, avoid renaming chains/nodes/etc... during the wrapping process. I'm not sure but HISE doesn't seem to like it.

I managed to compile a SNEX & a Math.exprnode and it's working fine. I also managed to compile a chorus & a delay into a DLL, then compiling the whole plugin, for the sake of comparing performances. For a simple graph, there's not much of a difference (on HISE's perfLabel, there's about 1-2% of performance gain, but it's worth testing it with more complex graphs).

I'll make some more tests during the next days...

EDIT :
I'll update a list of the nodes which produce errors when compiling :

control.xfader
control.converter

Linking parameters to SNEX

14

1.7k

11.8k

103.0k