@ulrik maybe this will help, I found this in the Juce forum :
https://forum.juce.com/t/pluginval-nans-found-in-buffer/39636/5
And in the thread there's a github page link which explain the procedure to debug an issue with pluginval :
https://github.com/Tracktion/pluginval/blob/develop/docs/Debugging a failed validation.md
@ulrik have you tried with another DAW ?
@DanH @d-healey hold on, I must have made an error while switching versions with git because I checked again and with the latest commit (Jan. 12), compiling is working. No more ad hoc error...
So I'm off to bed, apparently I'm too tired to work properly today...
@danh So I tried the latest develop and the issue is still here, even if I enter my Apple Dev ID, even if I use the ENABLE_HARDENED_RUNTIME=0 flag in my project.
In the autogenerated projucer file, the HARDENED_RUNTIME is set to "enable". If I disable it, I'm able to start compiling my project into Xcode but I hit the "outdated Projucer version" fatal error.
@danh I'll try the latest develop this afternoon, with the apple dev ID to see if I still get the error.
Yes, this one :
@yall said in delay problem:
I don't know anything about it I should know how it works
Take a look at the documentation here Scriptnode 101.
I'll add some chapters soon.
@d-healey aaah another there-must-be-something-wrong-but-I-don't-see-it bug 
You're right, thanks David, I wonder what we would do without you...
Sorry @Christoph-Hart , never mind.
@Christoph-Hart I stumbled upon a weird crash while organizing/refactoring some of my old scripts :
I made a mistake in a loadUserPreset function and called basically this :
inline function onbtn1Control(component, value)
{
Engine.loadUserPreset("-- Factory --/-- Init --");
}
I didn't put a if (!value) return; at the begining and with this, HISE crashes when compiling the script.
It does not crash when writing the call outside the button function...
(The preset does exist in the project folder).
Here's the code :
Content.makeFrontInterface(200, 100);
const btn0 = Content.addButton("btn0", 30, 0);
const btn1 = Content.addButton("btn1", 30, 30);
btn1.setControlCallback(onbtn1Control);
inline function onbtn1Control(component, value)
{
// Comment these two lines and compile to crash HISE
if (!value)
return;
Engine.loadUserPreset("-- Factory --/-- Init --");
}
//Engine.loadUserPreset("-- Factory --/-- Init --"); // Does not makes HISE crash
HiseSnippet 872.3ocsVs0SaCCE1oPPKcangzdF4wSEIJj.rKRnownW1p1.pVYS6MjwwkZgicksCrpo8ed+C1NNIPSgNtTokm74x2we93y43zUqnLiQoQdAGMZHC48D+dij1AMFP3RTmlHuE82mXrLMNW0diFRLFVLxyatO3T3ELOJ662uaOhfHorwpPnuo3T1m4Ib6Xsc28SbgnMIlcDOoj2auaGpR1PITo.elyODMjPOibJ6.hysJ9HuEZEysJcOKwxLfO6ohG0af5BYt+eia3mHXNgHTOHP4pQMFvEwcu7rZPHu46N9jOW9I+496yi4WoebF3YYFviQTNG3U41nTzCfRdknz74TZI+dTMencrEGedreGIbgzm.o5xTI2WTEdE+FJvCoc8DxYr1ZP3JD01LLbMbTX3p6TsJjtMV7IVYH9s3KwPhi2K0ZUxZq3rrxZ3s.DS5ez+z+nB+2xAvIutgYctpUhFDg3D3JslR5rTn0EXtTvkLb+TI0xUR7DNTipRFpjvdsF9bhHksZ0eVMXiM.Fjj.Zw1ALCCauPgcQwfIxXrCCW.ZUXplXFf+XmdspFv6iq8hhfDDnY1TsD1+fVxSAnqKTj3uZX5tZHh1ZqTuNtMgBWuiv0quAH0QxsvxUVcmf.GE1GRvlrXmuMU+U0pyZrZpfPIUVbx0BZozxAJK6PYsrL.rW3qape+oZqHSJX5oZ10GpuMf0joImvzky+NGgB0Iq9W39U8SyKcJ4nR5xFGNjUH2VIhcU0t02rWAUT6AcMUJXH3pMqmYwhdl7ZRDGBxB9tBYTF2KObBcewFMEresSShk35aKHCPvgLsk6xCdMYmCC9x6hC7axLmYUCyXaQoLj5tK99Cjmu2xvVMxsnfv2W3QWC9xYSduwDFX1lJNUPrSNvyMYuv.TGLwTF2jDogaGUdx+CXJX3sNE79Rwk76xszASmiUlBGckJ+G3XwaGO0uU+9LpcLAm2u82m0GJtis+KpTKWd59Dql6tjOHMoG7jIkA6tTxDF28cEW0Rtb3kkO8Xx3Lg+.eEFibxdEFitzHJgP0pio48GtWmdTlFfSxrGiCf+J.jwW0Y36GtdHJAdn7XJ0c7qCMtSGyly.lslALaOCXd4Lf4Uy.lWOCXdyshw8OJuO0pRxaG.EcakMgxyqkj.UVYUgn+RtVzJC
Not a problem if you write your scripts correctly but I thought of mentionning it...
@yall if you're still learning HISE - we all are but - you should really subscribe to David's patreon page. You'll get solid basic fundations and your level will increase dramatically : https://www.patreon.com/davidhealey/posts
@trillbilly But if that's what you want, with simple maths you'll be able to do :
When Knob1 moves from 0 to 1, Knob2 moves only from 0 to 0.5...
@harris-rosendahl I just finished a project containing 3-4 scriptnode modules. You can maybe encounter a few hiccups here and there while developing but it works fine in the finished product.
Take a look at the develop branch commits, Christoph has made a bunch of scriptnode improvements.
@nesta99 and don't try to do everything at once, do it little bits after little bits 
@dustbro I'm on the Dec. 22 commit but I'll try this one, thanks !
@iamlamprey i got this error too in VS17.
What I did, I revert HISE to the commit I used to build the plugin, screenshot and noted down the details, deleted it from the project and came back to the latest commit where I rebuilt the scriptnode module. Luckily it was a small one
@dustbro said in SNEX nodes - Waveshaping / Saturation / Distortion?:
Same here. I can compile script FX that do not contain SNEX nodes.
Do you get the "frozen" icon on your compiled nodes ? Here I can wrap the network, compiling it doesn't show any errors (seems to go well) but HISE is not using the compiled node.
BTW I didn't try to compile a SNEX node yet because I'm not smart enough ATM to understand how to write SNEX code 
@Lindon @iamlamprey I don't know if that will be useful to you but, recently I also experienced crashes while opening a somewhat old project of mine. Turns out the culprit was a scriptnode fx module (not really a complex one...).
I deleted it and was able to open the project with the latest HISE version.
@iamlamprey @dustbro here you go :
@christoph-hart said in Scripnode 101:
Use the Parameter Range Editor
Editing the parameters using the right-click context menu is just the fallback and there is this range editor that allows you to change the parameter range more quickly:
Apart from the ability to drag the min and max value as well as the skew factor with the mouse, there's a handy context menu which allows you to quickly set it to different presets, or in this case, simple copy the target range to the source range (so that you don't have to edit the range of the main parameter).
@danh I went for that solution either : on windows there's no problem, the user can select where he wants to put the samples during installation ; but on mac you can't do that in an installer and I thought it would be nice to allow the user to copy the sampleLibrary and locate it afterwards.
So in a matter of design constistency and customization I wrote a fully functionnal check location/locate samples system... only to discover I can't get rid of the locate sample dialog 
well... back to square one I guess.
Thanks anyway 
