@ulrik Wow, I wasn't good at Geometry when I am at school :)
Thank you so much hero!

@Fortune There's no official doc at the moment, and yes it's a bit in between JS and C++.
There is the snex_shaper node that is made for, well, shapers...
Though for simple shape algorithms, you might want to start with a simple math.expr node

@d-healey https://forum.hise.audio/topic/2002/multi-input-for-sidechain-ducking?_=1649278421374

Oh, thank you so much @d-healey it works great in this example! Now this image strip can be blended with vector graphics of the LAF rotary sliders 👍

@ustk Yeah I think there is some manual intervention required to regenerate the online doc, I do not have that much power... yet

@pstudioink Thank you for answering, but my question was about a specific function of PluginDoctor, not about how to develop plugins... never mentioned aliasing at all, you've probably mixed answers with another post by someone else

@ustk
really, I give up.

A year on and I just had this same issue for the first time, so I thought I'd update this thread for anyone else in my shoes. I got the same slew of ipp.h errors when trying to compile the master branch with VS2017 and IPP 2021.5.3.585, but I also got it to work by choosing "Static Library" in the Project > Properties > Intel Libraries for oneAPI dialog in VS. I didn't change anything in the HISE Standalone.projucer file (or elsewhere). I opened my finished HISE project and everything worked as expected, including the convolution reverb and analyzer, so I thought I was home free, but trying to export my plugin resulted in yet another slew of IPP errors. I downloaded IPP 2020.0.166 from the archive.org link above, plopped it on my desktop, and tried exporting again. To my shock and joy, it worked immediately. I didn't update any paths anywhere so I guess it just needs to exist somewhere on your computer? Seemed too good to be true but I'll take it.

Also a heads up: If you have both installed and recompile HISE, the VS Project > Properties panel will have two categories for IPP. The 2020 one says "Intel Performance Libraries" and the 2021 one says "Intel Libraries for oneAPI." So if you changed the setting for the new version and then downgraded IPP to recompile, you'll probably need to reenable it since they're different options.

@d-healey Thank you so much dude! I really appreciate that.

@Casey-Kolb Yes, when IPP is deactive the artifacts are gone

@d-healey ok thank you! :)

@ustk Oh, Thank you so much buddy! You guys are life savers...

@harris-rosendahl -for that you will have to build your own pop up...

@dustbro That's great, thank you so much, I will check it asap!

@tomekslesicki I found that oversampling using the setMunimumSampleRate method needs to be "kickstarted" to work, so this is my workaround. I see a visual change in FFT display and EQ when OS is enabled, so that will probably affect other modules as well (like LFO)
This function just flip flops the OS state

const var osflipTimer = Engine.createTimerObject(); osflipTimer.startTimer(250); osflipTimer.setTimerCallback(function() { Engine.setMinimumSampleRate(96000); Engine.setMinimumSampleRate(44100); OSinitial(); }); inline function OSinitial() { local oscombo = OversamplingCombo.getValue() -1; OversamplingCombo.setValue((1-oscombo)+1); counter = counter + 1; if(counter>=2) { osflipTimer.stopTimer(); } OversamplingCombo.changed(); };

@Sawer 👍

@d-healey
Interface
NoteHandling
ChordAttacher

@ulrik Thanks a lot! It is so strange because I tried a very similar method for accessing the properties using [] with no luck. For some reason I was always returning the name of the key rather han the object itself...
You saved me :)

@d-healey I say parser but I reckon it was an object sorter of some kind... @ulrik solution is indeed what I need

Thanks guys!