@ustk Sounds great - thanks!

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.

Just a moment...

favicon

(www.patreon.com)

@Christoph-Hart well I was asking because I’ll just do it for myself but it could be a good option as a pre-processor. As you say it is quirky!

@Matt_SF Thank you, that worked - I shall investigate further. Cheers.

@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 ?

@Matt_SF thank you man, this seems to be a good starting point! :-)

@ulrik haha you never cease to amaze :face_with_tears_of_joy: !! Thanks for sharing and take care of yourself !

@Christoph-Hart Yeh I already have safety checks in place I just didn't paste them above. Cheers!

@d-healey Yes I know I can do that but I think I saw @Christoph-Hart use another way to set a random Colour constant...

@d-healey @orange Awesome, thanks! :)

@Dan-Korneff said in Replacing the LinkOSX file:

@orange ok! That's where we need to look. Check the permissions of the file that was previously installed. Who has what permissions when you right click on the file and hit "get info"?

This happen even on an admin account. I think since there is a file, Whitebox doesn't overwrite it.

@DanH said in Replacing the LinkOSX file:

@Dan-Korneff I use a pre-install script to remove any files / folders before installing new ones

That did the trick, Thank you! So for this purpose, first a Pre-Install script to remove the file:

#!/bin/sh rm -rf $HOME/Library/Application\ Support/MYCOMPANY/PLUGIN/LinkOSX exit 0

Then the Post-Install script to replace it:

#!/bin/sh sudo -u $USER mkdir -p $HOME/Library/Application\ Support/MyCompany/TestPlugin/ /usr/bin/rsync -avurpE --remove-source-files /Library/Application\ Support/MyCompany/TestPlugin/ $HOME/Library/Application\ Support/MyCompany/TestPlugin/ sudo find $HOME/Library/Application\ Support/MyCompany/ -type d -user root -exec sudo chown -R $USER: {} + rm -rf /Library/Application\ Support/MyCompany exit 0

@toxonic this has been reported before

@DanH ok great :thumbs_up:

@lalalandsynth Yes the low pass might have a error margin that is relevant in a pitch context (it usually stops smoothing at a difference of ~-80dB but this might be a audible error when you map 0...1 to a 20kHz range.

The linear mode should be fine though.

@MikeB said in A few questions of understanding:

If I have almost 100 knobs (in different panels) that should all look the same, a global LAF is better, isn't it?

If they all look the same and all have the same colours then it doesn't matter. I'd still go with local so that I had control over individual knobs and so it didn't make the HISE UI knobs look weird, but it really doesn't matter.

With a local LAF, I would need an additional 5-10 scripts for each knob for the individual LAF.

You can use the same local LAF object for multiple controls. I put almost all my laf in a single file. See this as an example.

all declarations in one script?
Does it make sense to collect all component declarations in an external script "declarations.js" or better in different scripts at the beginning of the respective function?

As I mentioned I put almost all my laf functions in a single file. I put component declarations into separate files, each with their own namespace. So if I have a set of controls all relating to a mic mixer, then they go in Mixer.js with the namespace Mixer.

@d-healey Ah ok, great ! Thanks

@Lindon

Brilliant thanks

@Christoph-Hart would you have time to look into this soon you think? :)

@Christoph-Hart @d-healey Thank you for the information - all set. I'm running it under Rosetta, and it's fine.