Scriptnode Delay

[DanH]

@Matt_SF Thanks I think I'm getting it to do roughly the same as the sdk node from Master.

This might be a very noob question but is there a way to send a signal path to the left / right channels only? I've got the signal split but they seem to be going straight down the middle....

[DanH]

@DanH oh wait, found the jpanner... but is there a better way? Can you do it within a container for example?

[Matt_SF]

@DanH yes, use a container.split (for L/R) and use send/receive nodes. You can send the signal wherever you want.

[Matt_SF]

@DanH said in Scriptnode Delay:

send a signal path to the left / right channels only?

Oh for this you'll have to setup some sort of dry/wet chain with gain modules and multi/split containers

[ustk]

@DanH I should have used a jdsp.jdelay in your snippet, my bad...

[DanH]

@Matt_SF Thanks mate, think I've nearly cracked it :party_popper:

[DanH]

@ustk ha, not at all, your example was super handy - Can I send an update when its ready for you to look at please?

[DanH]

@Matt_SF @ustk Any ideas where I'm going wrong with this? Obviously a sample rate issue, but I just spent an hour editing the module and the errors only appeared when I reopened the project....

[Matt_SF]

@DanH You have to put the modchains outside the oversample container.

[Matt_SF]

And if youre going to modulate things, I recommend reading through this post (especially the end) :
(https://forum.hise.audio/post/42102)

[DanH]

@Matt_SF Thank you. Do I not need to split the signal into the them though?

Edit - I think I got it

[DanH]

@Matt_SF Ok had a good look through that thread, thanks for pointing me there. So I'm not sure, but I don't think I'm using any SNEX / Expression nodes etc in my scriptnode effect. So I'm confused as to how to compile it now. I followed the steps in the thread (for SNEX nodes etc) to wrap up my main container but it crashed upon 'save & reload' and it won't load the project in the SNEX workbench or the main HISE project in New Layout branch. I restored the file from backup and I'm back to where I started. I'm not sure that was the correct thing to do anyhow.

I'm sure at one point you could right-click the main container and export as cpp class. Is that not a thing anymore? So confusing

[Matt_SF]

@DanH yes there's a lot in this thread. But the part you'll find interesting is where we talked about delays, modulation and frame.nodes.
Don't mind the SNEX compilation for now, the feature is not complete and not fully stable yet. This is aimed to replace the old export cpp function (that's why you can't use it). If you don't have Math.expr nodes or stuff like that you'll be able to export your plugin.
Note : if you used the workbench in your project folder, don't forget to clean the DspNetwork and Additional Code folders, otherwise you'll get a bunch of errors when compiling your plugin.

[lalalandsynth]

I just opened my Ensemble FX in Develop that was made in a previous scriptnode version.
It used the STK Delays and worked just fine.

When opening in Develop they are obviously missing but when I replace them with JDSP they dont seem to do anything?

I was modulating the delay times...slowly , so it worked with the STK but yeah.

Anyone know if there would be a difference between those JDSP and stk delays ?

[Matt_SF]

@lalalandsynth to my little knowledge, there's no difference in the sense that the jdsp.delay is the one you want to use for modulation, as we talked in the thread linked in the previous post.
I can confirm it works just fine for chorus-y effects.
Maybe the issue comes from something else ?

[lalalandsynth]

@matt_sf ok, thanks , good to know , its a bit of a complicated patch but I will look for other problems.