Scripnode 101

[Dan Korneff]

@iamlamprey That's definitely one way to do it. The issue is I have about 10 areas that need oversampling (each containing 1-3 nodes). It might not be the most economical way to handle a dsp network that is already pushing 100 nodes.
What I really need is a way to access this parameter on the main interface:

[Dan Korneff]

@matt_sf said in Scripnode 101:

With latest versions you can compile a dll with the workbench, then just compile your plugin with HISE and the dll network will be embedded into your plugin.

Can you give some more info on this? I've already created a network in HISE. Do I need to open this network in workbench and export a .dll? How do I do this? I don't see that option:

Is it this one:?

if so, that just makes Workbench crash

[d.healey]

@dustbro said in Scripnode 101:

Is it this one:?

Yes.

@dustbro said in Scripnode 101:

if so, that just makes Workbench crash

@crd Has been having the same issue. Did you compile the latest version of the Workbench?

[Dan Korneff]

@d-healey said in Scripnode 101:

Did you compile the latest version of the Workbench?

I'm using the version from Nov29
Lemme see if there's an update

[d.healey]

@dustbro said in Scripnode 101:

I'm using the version from Nov29

Did you build it yourself?

[Dan Korneff]

@d-healey yes

[crd]

@dustbro the last develop build fixed the crash for me when compiling wrapped nodes.

[Dan Korneff]

@crd said in Scripnode 101:

last develop build

I just compiled the latest develop branch. Workbench is still crashing when I Compile DSP networks

[d.healey]

@dustbro said in Scripnode 101:

when I Compile DSP networks

Did you try a test network with just a core.osc?

[Dan Korneff]

@d-healey Here's the minimal test I'm doing:

[Dan Korneff]

@Christoph-Hart
debug workbench

[crd]

@dustbro wrap the node before you compile it. Christoph explains the process in this thread

[Dan Korneff]

@crd said in Scripnode 101:

wrap the node before you compile it

Did you say "wrap" or "crash"? Cause I can get ONE of those to happen :beaming_face_with_smiling_eyes: :beaming_face_with_smiling_eyes:

[crd]

@dustbro ha :) sorry that does seem like the right steps.

[Dan Korneff]

Through trial and error, I'm able to wrap a node in HISE by closing and reopening between each step.

[Dan Korneff]

This post is deleted!

[Dan Korneff]

now when I compile the dsp network, I get these errors in VS2017:

1>c:\users\dan\desktop\wrap 3\dspnetworks\binaries\source\chain.h(38): error C2923: 'scriptnode::container::chain': 'NV' is not a valid template type argument for parameter 'ParameterClass' (compiling source file ..\..\Source\Main.cpp)
1>c:\users\dan\desktop\wrap 3\dspnetworks\binaries\source\chain.h(35): note: see declaration of 'NV' (compiling source file ..\..\Source\Main.cpp)
1>c:\users\dan\desktop\wrap 3\dspnetworks\binaries\source\chain.h(36): error C2955: 'scriptnode::container::chain': use of class template requires template argument list (compiling source file ..\..\Source\Main.cpp)
1>c:\users\dan\documents\github\hise\hi_dsp_library\node_api\nodes\container_chain.h(127): note: see declaration of 'scriptnode::container::chain' (compiling source file ..\..\Source\Main.cpp)
1>c:\users\dan\desktop\wrap 3\dspnetworks\binaries\source\chain.h(43): error C2955: 'scriptnode::container::chain': use of class template requires template argument list (compiling source file ..\..\Source\Main.cpp)
1>c:\users\dan\documents\github\hise\hi_dsp_library\node_api\nodes\container_chain.h(127): note: see declaration of 'scriptnode::container::chain' (compiling source file ..\..\Source\Main.cpp)
1>c:\users\dan\desktop\wrap 3\dspnetworks\binaries\source\dspnetwork.h(23): error C2923: 'scriptnode::container::chain': 'NV' is not a valid template type argument for parameter 'ParameterClass' (compiling source file ..\..\Source\Main.cpp)
1>c:\users\dan\desktop\wrap 3\dspnetworks\binaries\source\dspnetwork.h(20): note: see declaration of 'NV' (compiling source file ..\..\Source\Main.cpp)
1>c:\users\dan\desktop\wrap 3\dspnetworks\binaries\source\dspnetwork.h(21): error C2955: 'scriptnode::container::chain': use of class template requires template argument list (compiling source file ..\..\Source\Main.cpp)
1>c:\users\dan\documents\github\hise\hi_dsp_library\node_api\nodes\container_chain.h(127): note: see declaration of 'scriptnode::container::chain' (compiling source file ..\..\Source\Main.cpp)
1>c:\users\dan\desktop\wrap 3\dspnetworks\binaries\source\dspnetwork.h(28): error C2955: 'scriptnode::container::chain': use of class template requires template argument list (compiling source file ..\..\Source\Main.cpp)

[Dan Korneff]

Me trying to figure out scriptnode...

[ustk]

@dustbro said in Scripnode 101:

I guess a more direct question is: how do I bypass the oversampling from the Main Interface...

Back before the new scriptnode version, we could just connect a parameter to the bypass button so it was easy for all kinds of nodes to control the bypass.
Now, this is not possible anymore, but I don't know if it is intentional from @Christoph-Hart removing this ability. So if it has been lost during the migration then it might be re-implement, or perhaps with another way to access it...

@iamlamprey Doubling the nodes is not an option. Imagine if you want a selector with x2, x4, x8...

[Christoph Hart]

@ustk Yes this is intentional. The reason is that if you want to bypass nodes, you usually want this process to be click free (like the container.soft_bypass node offers now). But having the overhead of the "bypass smoothing" for every node wastes too much performance.

Now the oversample node is maybe the only node where you still want to connect the bypass in order to change the oversampling (I can't think of a use case where it makes sense to eg. bypass a fix_block node). However I would rather add a dynamic oversample node that exposes the oversampling factor as parameter that can be modulated like any other knob. This will also solve the problem of having to duplicate your signal chain in multiple oversample containers like you described

Doubling the nodes is not an option. Imagine if you want a selector with x2, x4, x8...