As @trillbilly says, a preset in HISE only saves/restores the state of controls on the UI. So if you are using a UI control to load IRs and that UI control is set to saveInPreset then everything will work how you want.
I posted a video on Patreon on Saturday showing how to load IRs into the convolution reverb effect using a combo box.
@clevername27 A panel is the most versatile component and they are necessary for styling your interface, for stand colours, images, paint routines, SVG, animations and more .
I know you haven't asked (maybe it serve someone else in this case) but you can also make them interactive like buttons and custom sliders (although this purpose is less obvious since the apparition of custom global/local LookAndFeel), menus, store data and even create a complex interactive component of your own! The choice component of gods 🙂
@Christoph-Hart This keeps happening, all of a sudden it says that the node is not compiled and yet it is.
Previously I seemed to have fixed this with changing the path but the path is now correct and yet it still happens.
What am I doing wrong here , is this a bug or normal and I am just missing why this happens ?
EDIT: this time it works to rebuild it , I wonder why it reports as not compiled though ?
Alright, I've added a warning icon next to the parameter knob if there is a range mismatch between source and target.
I don't want to fix it automatically as there are a few reasons why you would want a different input range (eg. the soft_bypass templates map an integer range 0-4 to 0.0...1.0 of the fader node) but in most cases it's a subtle difference that will make the compiled node slightly less performant (or in this case even crash).
Clicking on the button will show you a dialog with the source and target range and you can easily copy the target range back to the source to make the warning go away (if it's reasonable). Note: if the source range and the target range appear the same, it's most likely a difference in step size that causes the warning.