@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.
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.
It worked fine but instead of having an exported vst file in my project's folder I found there a copy of it. I clicked to show info of this file and it said the original VST is located here: /private/var/root/Library/Audio/Plug-Ins/VST3/"my plugin name".vst3
Screenshot 2022-11-30 at 14.58.15.png
So I used that one and inserted to where all my other VSTs are and it worked fine.