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

So the reason why it's crashing is that you're using different ranges for the delay time parameter knobs and their targets. In order to solve it, always make sure that you're using the same range on both ends or it will create a conversion (which in this time, failed).

I'll think about a way to display this to the user so that it doesn't crash silently, but in the meantime, all you need to do to solve this problem is to open the range editor of the target knobs (the one that displays the curve over the knobs) and then right click and choose "Copy range to source". This will make sure that there is no range conversion going on.

@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! 🙂

I just noticed if I load a sample map with 3 groups, it does cycle through all groups, but in reverse. And the same issue with selecting the last group from the menu.

Peek 2022-12-03 18-28.gif

@Christoph-Hart Excellent!

alt text

@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 put a ignore event processor into the midi chain of the global modulator container.

@DanH ok great 👍

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

@Christoph-Hart Good to know. Thank you. I guess I'll leave that for a future plugin update.

@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

@Straticah @ulrik

Useful & Great Solutions guys, Thank you so much! Both of these are exactly what I need, cheers! 🙂

@Lindon

Brilliant thanks

@DabDab said in My plugins , Gui and 3d Work.:

@d-healey doing a very beautiful work for HISE. I hope somebody will make 3D GUI tutorials for Audio Plugins development in future.

If I need a 3D GUI I'll hire someone to do it for me 🙂

I've been pretty busy mixing in Atmos. What would you like to know?

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

@Christoph-Hart @d-healey Thank you for the information - all set.