bada-bump is there any update on this, didnt find any related commit and messing with it in hise beared no luck, dont know if I missed something or if its still in the works?

@Casmat Nope, you just have to match the shadow colour to the background. Experiment though you might get better results using radial gradients for example.

For more complicated functions you could pass an array of parameters and branch to different functions based on the length of the array.

For example

inline function myFunc(params: Array) { switch (params.length) { case 0: return subFunc0(); case 1: return subFunc1(params[0]); case 2: return subFunc2(params[0], params[1]); case 3: return subFunc3(params[0], params[1], params[2]); } }

@Lindon of course it is, thankyou.
I think I tried that with intensity and had to do it the way I posted for it to work so I just went straight to that for inverting.
Need to stop asking questions at 11pm when I’ve been going since dawn.
Thanks

@d-healey said in How to use Modulator.exists?:

Did you try it? I get an error.

That's very interesting. I spent so much time in the C++ i failed to consider if it even compiles in HISE. I assumed it did, but it doesn't in the onInit() callback. It will compile if you call exists() in any of the other callbacks, but will throw an error at runtime.

Perhaps exists() is not supposed to be visible in the API and was accidentally added into the documentation?

@d-healey Thank you!

@aaronventure My dude - thank you! This is fantastic…truly appreciate the detail. This is all new to me and incredibly helpful—cheers!

Great, thanks a lot, guys!

@d-healey Thankyou, I had it in my head that the processor id wasn’t in the inspector for slider packs.
Facepalm.
Thanks as always

Done - https://github.com/christophhart/HISE/pull/680

@Chazrox Thanks! Here's the video link - https://www.patreon.com/posts/making-led-in-112912332

Ok, I've been getting a lot of strange errors form variables called "root". This has been driving me nuts because I am working with a lot of chord and scale information so many times I need a "root"! I'll just have to start naming them something else apparently.

@aaronventure Okay thanks for confirming everyone. I figured a timer would work just as well but I was hoping to avoid having one run in the background waiting for a fade event. I suppose a combination of a broadcaster and timer would work but not fun to implement.

@njAudio03 said in Hadamard Mixing Matrix:

or will I have to do some C++?

https://faustlibraries.grame.fr/libs/routes/#rohadamard https://forum.hise.audio/topic/11250/this-is-my-reverb-in-faust-what-do-you-think?_=1738742996840

if you can make a reverb in scriptnode let me see because I'm really curious. Maybe you could start from the delay template?

@rglides Now I just need to figure out why it wants to keep selecting ambient drum and bass over and over 😅

@ulrik
Oh, this is great! Thank you! :-)

@d-healey I thought in this case the parameter is the address for the data "this.data.test" being a path, not the actual data.
So I was thinking the path variable is static, but it is just rewriting the contents at that path.
Anyway, I fixed it by using .getValue() and .setValue():

p.set("allowCallbacks", "All Callbacks"); p.setMouseCallback(function(event) { altDragAndDrop(); }); inline function altDragAndDrop() { // show "+" cursor when alt/option is pressed local cursor; event.altDown ? cursor = "CopyingCursor" : cursor = "NormalCursor"; this.setMouseCursor(cursor, Colours.white, 1); // alt/option drag copies to clipboard if (event.drag && event.altDown) { Clipboard = this.getValue(); } // releasing the mouse on a panel copies the clipboard to the panel, then clears the clipboard if (!event.clicked && event.altDown && this.getValue() != Clipboard && Clipboard != undefined) { this.setValue(Clipboard); this.repaint(); Clipboard = undefined; } };