Scripnode 101

[A Former User]

So the modchain does not have an audible output signal, right?

[Christoph Hart]

@ursbollhalder Yes. It's supposed to be used with a peak node at the end so beyond that point the signal should not matter anymore.

[A Former User]

@christoph-hart Yep... That's what I messed up... I put a simple xfader into a modchain (doesn't make much sense, I know) and had that in a split container and was wondering where the signal was coming from! Oh my !

[A Former User]

@christoph-hart If I mix between a dry and a wet signal with an xfader, is it correct to use the overlap or rms mode to avoid a drop in volume when adjusting the mix slider on top? https://docs.hise.audio/scriptnode/101/drywet.html note to self: RTFM!

And as the last question... can I somehow dynamically load convolution files into my scriptnode house of wonder?!? Similar as to when I load those files into the standard HISE convolution module with a combobox f.e.?!

I have 3 convo containers that filter the incoming signal... etc. It would be nice if I could let the user make those choices in a combobox... see here:

2021-12-09_12-23-25.mp4

Google Docs (drive.google.com)

[A Former User]

So I added a couple of knobs to my scriptFx, as instructed above by @Christoph-Hart...

Now when I add f.e.

const var myKnob = Content.addKnob("myKnob", 30, 20);

and then later on take that line out and recompile, the knob and some xml-graveyard junk is still in there somehow! Also not sure where the xml for the scriptFx-interface would be, so I could frankenstein my way through this for now...

[A Former User]

And here's to my very last question of today:

Is there a reason not to forward the params to the UI but first creating intermediary one on the scriptFX ui? I could think of re-usabilty issues... but what else?!

[Dan Korneff]

@ursbollhalder said in Scripnode 101:

intermediary one on the scriptFX ui?

If you add controls to the scriptFX UI, you can no longer access the DSP parameters from the main interface.

[A Former User]

@dustbro Yeah. It's either main interface to DSP parameters, or...
main Interface to scriptFX interface to DSP parameters?! Right?
With the second option you loose option No.1...

[Lindon]

@ursbollhalder said in Scripnode 101:

So I added a couple of knobs to my scriptFx, as instructed above by @Christoph-Hart...

Now when I add f.e.

const var myKnob = Content.addKnob("myKnob", 30, 20);

and then later on take that line out and recompile, the knob and some xml-graveyard junk is still in there somehow! Also not sure where the xml for the scriptFx-interface would be, so I could frankenstein my way through this for now...

Yes this is standard behaviour - your script is adding a knob, to remove it (in order to have it always appear in the smae place - just delete the knob in theVisual editor...

[Matt_SF]

@ursbollhalder said in Scripnode 101:

And as the last question... can I somehow dynamically load convolution files into my scriptnode house of wonder?!? Similar as to when I load those files into the standard HISE convolution module with a combobox f.e.?!

Not with a comboBox at the moment (at least I didn't find a way). Check this thread : Changing Impulses in Scriptnode.

[A Former User]

@lindon I somehow can’t access the interface editor for the scriptFx. Hitting that icon doesn’t do anything here!

[Lindon]

@ursbollhalder click the interface button and then the unlock button...

[ustk]

@christoph-hart it would be nice to have a downsampling ability too for old algorithms emulation that you can tune like 8khz, 34.125khz, or any other fancy value.
Do you think it is a reasonable request ?

[Dan Korneff]

@Christoph-Hart I had a perfectly working project that now won't export. All of the snowflakes are missing from my compiled nodes.
....and I'm seeing this error when I check the dll info.
Any thoughts?

Looks like this happens from the Dec 8 commits.

[Dan Korneff]

Can someone explain to me the best way to smooth a delay node that is connected to a tempo sync node?

I've tried many combinations of values. I can get tempo sync to modulate the smoothing node, I can get the smoothing node to modulate the delay node, but I can't get the tempo sync to modulate a smoothing node to modulate a delay node.

[ustk]

@dustbro There's a x1000 factor issue. In this snippet, the multiply parameter of the PMA is set to 0.001 so it divides the ms by 1000. I don't know why the smoother doesn't take care of this conversion itself... Bug or intended behaviour, that is the question :)

HiseSnippet 1298.3ocwX8zaaTDEeV6LI0tIEpHGQHeLUJDYWJEj3PbhSLxh5TqroQ8VXxtiim5cmY0tiShAwAtgTOvINzSvG.NxENAW3S.bse.3DUhyH3M6rd+i8VWa2zfODk4Mu4898dueu2L1c7EVzf.gOxnzQC8nHiUwlC4xdM5QXbTq8PF2B2lDHo9Uzh1cnGIHfZiLLJ9oJAFkVBE94EauKwgvsnIhPniELK5CXtLYhzN0+LliSShM8HlaJsuW8VVBdCgiX.fmh3pHOhUexYzCHJ0JfQFKuuMSJ7MkDIM.YrztB6gl8DWv05eLKfcpCUsnFxDLjVbSgisBwJonF8XN1cFE2AHvJcRxBE0Yg0wsY1rX4IYi2NbiJImHc9vnPV3ULC7pkFdUSAubfjQJHsjFR2FaZ4y7jI6nvyMws3PwoKAR6oghVWjwuhaH.E3xsbI8oM8gEwGXi6Ws5lUf+bmOo6.tkjI3UD7CDR5C4abmxeY4Rk+pxUFeqtcycOka7ENNT+b2VUo8m1A2fOv8Tp+lUNm3LfFqHD9Yyo3WdNMcI2RG0oTTvawYxG5Q4uLh.JJUA+2iZsGQRTEhHYfddTeISAAi8nmCrZcYoDdOZPeovC30STy.1hvdfCQlkBo5ah1.xAYpaphCOfIGltuZbd0RyFuZ5z9YEt2F2gIs5kOdKjCdgr1aZ7F0ktFd+tcoVxDvtDt4imZK4bCkYs8rbT6I3eEPVMZYklOtVtMleCNoIvym5Q7oGI53PFtQ.w0ygdHf2MqbpivpuI6KnS143ogvtJM1vpGgyoNAKRC1xy7PqZScnE5Pw.IieVahzmcIzodv.WSXTtEsQD5.YFET8Y50UUqU7ESJ2Nbw+Beh1rlZsQzl0FsYpVzCnxKD98CKGQ+OTLz49fvj7IcurFZGGGwEMDtdrH1KTCBk0Q3LzqmfyrThzZLBo63JF.NIBtFENPXCI.bShEjnF1gH6o5KTyX.hG0eKqXBXFemttqLwnq1zQM3RWUnDdwVwTCXz7K0Jnqpf1psBNVsqEwAcrp9o58PJaFdAVD9zpJotdhSBFxsPY.75g.FXBakRiEEhnj4AGQ7OiJChFVxoV5zbXRqEXXL1ykf5P7gawgadThVAqChDo56gGsBHksY7n.MYtRaxkiI6t0MkTOUCR54kl8oWnC8zRUYmUvGohczXlY85no66Wr8j9t5b56UwsG3HYdNLvISXez7G7fylK.TBuOm.sx1WEdu92Nd3+CO6Y+7T79svOhqnbT6vW8MlGX0QoHwZJSF16ZwrW0VWCz10wAtBgrG09Du3jyLvhKlJUtxBlJC+LMVr1.wlY4u96Z7ze74auy.ovEFiGd07qhR+KyFiZZ.o7HJ8vQXYEb0spVsF5Zv4X7N1SPkUWLjvixsFlgV8twzpbz7Ja98xpGVEWuVC+.3VChekCga5mGJ4MvOwlBOQHKM7lvKPAggcUutTw4tHLAU7m96+4Ot7O+sYmJFN130e7xagMCKfvCPxY9BXt+mGvlhUFWFGa.2SrC71JZq4f5UHy.tLDfBWAi0ym.74uyd+dDAP+s6mZ9dk2L9NMyO1T+02+7fmhdu5uDBnJGsqPz2kD91wE6a5cc7RWWhku3jnoSph4MBk.c07veNjR31p0UpgNWG5X0nWjKylchkk5qB89vX37OycWfy7AKvYt2BblObANy8Wfy7QKvY93odF0uLTDqSM2FDzY+Pxkgwn4BP2L5+.DfbWHE

[Dan Korneff]

@ustk thank you so much!

[Dan Korneff]

@ustk said in Scripnode 101:

There's a x1000 factor issue

Any ideas on how to deal with values over 1000ms?
Say 10000ms? Setting the PMA to multiply by .0001? I can't seem to find a meaningful ratio between the tempo sync time and the delay node time.

EDIT
The skew factor of my delay time knob was set to .3 :/ setting it to 0 resolves the issue :)

[Dan Korneff]

@dustbro said in Scripnode 101:

setting it to 0 resolves the issue

actually causes a $h!t ton of issues... haahahah!
Getting a break point debugging. What should the skew factor be set to for a slider? Is there some kind of general rule to follow?

if (range.skew == 0.0f)
				{
					// You have some weird ranges going on here...
					jassertfalse;
					range.skew = 1.0f;
				}

Found the issue. A couple knobs on my interface had a middle position that was not in their range. oops!

[Dan Korneff]

Is there a node available in scriptnode to invert phase?