@Oli-Ullmann yeah fair enough. These are filters though, so it should work. I made the eq in scriptnode

@Christoph-Hart
Ah ok, thank you. :-)

@iamlamprey same as the other fellows, I just do this in a browser from my dev account...

@dannytaurus JPverb and Greyhole Reverbs developed by Julian Parker have been moved to MIT licence some months ago (don't remember the exact date...) after discussion with Julian himself.

@ustk said in Colour Palette:

colour specific variable type

It's there, kind of.

f1eafd7a-168d-46c2-9892-81fa0de5a6e2-image.png

@pcs800 Awesome! 🙌

@MysticForgeRider when it crashes, does the error report come up?

@ally What's your use case? Almost everything can be tested in the standalone version of HISE, it's not usually necessary to build the plugin version.

@DanH Seems to be working here:

CleanShot 2026-01-07 at 19.47.40.gif

@Ben-Catman Thank you very much! I’m really glad you found it useful. Hope it helps save time in your HISE workflow 😊

@Oli-Ullmann Yes, I've tried everything. But somehow after I restarted my laptop it started to work fine. 🤖

@dannytaurus Yes both Logic and cubase, I will download reaper to see, yes started with a clean build each time

@Christoph-Hart wel as I say I can send you my project to use for testing - and if not then I can surely test using it...

@cassettedeath said in Restoring properties with DAW session:

HISE feels like whack-a-mole sometimes!

That's pretty much what all software development is! 😂

@Lindon thank you ,I will try that now

@pgroslou you can add a second AUDIO WAVE FORM like the one Dave gave you and add it on top of the one in the code I gave you , just disable the opaque settings and alpha the background so you can see both screens, and select the convolution reverb on the processor settings, now you can give the user both options, your convolutions ir or the option of user ir

@David-Healey

Awesome! Thanks for your input David!

Really appreciate your video tutorials also.. I would have likely never attempted plugin dev scripting otherwise, great work ;)

Hise for the WIN

@dannytaurus said in Anyone doing this to declare components?:

Do you mean like this?

Kind of.

I split my scripts into lots of separate files, preferably one file per part of the project - what constitutes a part could be functionality, or it could be UI, I often have one namespace per main UI panel.

For example, I'll have a file called Presets.js which contains the Presets namespace and this contains everything related to preset handling, including the UI.

I'll have another file for handling expansions.

I'll have another one that handles a drop down menu in my plugin's header. This will have items for opening the Settings page, the About page, etc. This is an interesting one because the menu itself shouldn't know anything about the Settings or About pages, it doesn't need to.

But the Settings and About pages are aware of the menu's existence. So using broadcasters those namespaces can watch the menu and if the Settings option is selected the Settings namespace will show the correct panel, if the About option is selected then the About namespace will handle it. Everything is very self contained and links between namespaces/parts of the project are minimised as much as possible.

Here is what the on init section looks like for my current project. Nice and clean 😀

f0136148-47c7-4818-82cf-fc6d90abf1d0-image.png