Scripnode 101
-
@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...
-
@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.
-
@lindon I somehow can’t access the interface editor for the scriptFx. Hitting that icon doesn’t do anything here!
-
@ursbollhalder click the interface button and then the unlock button...
-
@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 ? -
@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.
-
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.
-
@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
-
@ustk thank you so much!
-
@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 :) -
@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!
-
Is there a node available in scriptnode to invert phase?
-
@dustbro Not sure, but doesn't the all-pass filter node do that?
-
@dustbro use a
math.mul
node and set the value to -1 -
@dustbro As @Matt_SF said,
*-1
is the way to go -
Thanks!
Should nodes like Tempo sync and PMA need to be placed in a modulator chain? -
@dustbro no need, you can put them in the graph as is (or put them in a
container.offline
)@christoph-hart said in Scripnode 101:
What the modchain actually does is creating a monophonic and downsampled signal which will not be fed into the original audio signal and thus is suitable for modulation if you put a core.peak at the end of its nodes.
-
@Christoph-Hart is there an equivalent to Engine.getSampleRate() in SNEX? I'm getting an error saying it Engine can't be resolved. Come to think of it, Console.print() doesn't work as well. it's supposed to, right?
-
@dustbro No but you can use the
prepare
function to store it to a member variable:void prepare(PrepareSpecs ps) { sr = ps.sampleRate; } double sr = 0.0;
-
@christoph-hart Thank you!