I searched on every forum on internet and eventually end up fixing this by jumping in late here, but this is a great discussion! The scripting solutions from @d-healey and @Felix W. look like the cleanest way to handle the numeric display logic in HISE.
Once you get those meters working perfectly, it's always fun (and good practice!) to compare your plugin's metering against a real-world reference. If anyone needs a super quick way to check their room's SPL or monitor levels, you can just use a simple online tool like noisemeter.co. It's obviously not for high-precision master bus work, but handy for a quick sanity check against your final output!

This SIMD stuff is quite the pest, getting similar errors on MacOS even after my "fix":

In file included from /Users/user/Documents/altar/DspNetworks/Binaries/Source/Main.cpp:6: In file included from /Users/user/Documents/HISE/hi_dsp_library/hi_dsp_library.h:55: In file included from /Users/user/Documents/HISE/hi_tools/hi_tools.h:148: In file included from /Users/user/Documents/HISE/hi_dsp_library/../hi_tools/../hi_streaming/hi_streaming.h:62: In file included from /Users/user/Documents/HISE/JUCE/modules/juce_dsp/juce_dsp.h:236: /Users/user/Documents/HISE/hi_dsp_library/../hi_tools/../hi_streaming/../JUCE/modules/juce_dsp/containers/juce_SIMDRegister.h:85:32: error: implicit instantiation of undefined template 'juce::dsp::SIMDNativeOps<unsigned long>' using vSIMDType = typename NativeOps::vSIMDType;

And here's an old post from the man himself:

https://forum.juce.com/t/dsp-module-breaks-compilation-on-linux/27346/4

Seems like it's either a JUCE issue, or just the different behaviors of different compilers

@David-Healey Azure signing is no longer offered for individual developers. If you're an incorporated entity of some sort you might have better luck. https://github.com/Azure/trusted-signing-action/issues/42

Since my software is open source I was able to get a signing certificate with http://certum.store/ for $29 after submitting a ludicrous amount of personal information and paying extra for the special card they ship to you. Not exactly recommended, but it was the cheapest I found.

I saw another option for open source developers come up on hackernews that I'll have to look for again.

Thing is, I haven't actually got around to signing my Windows binaries yet, and I have received zero complaints from customers so far... Which is rather surprising.

@David-Healey yes this is where I am arriving at. RNBO scriptnode with the xwax Timecode as the extra node.

@Chazrox I think it's down/up sampling the contents. Have you tried adding a convolution reverb inside of that node? My guess is that it's changing the pitch of the IR sample in that case

@Chazrox said in Multiple Styles for Controls?:

@bwoogie and when you're done with that....🤣

...I'll know right where to find you 🙃

Another blog post and video for you. In this one we'll look at scripts and snippets that are available from the HISE community. I'll show you how to find them on the forum and the correct way to bring them into your own projects.

Leave a comment on the blog post, thanks!

https://audiodevschool.com/hise-community-scripts-and-snippets/

@David-Healey Thanks, David. I did take your courses earlier, they’re true life savers!
It also makes sense that the File.loadAsBase64String() function isn't available on the release version of HISE. I previously compiled HISE following your tutorial, but I ran into the issues I described in this forum post, where the string returned from File.loadAsBase64String() didn’t seem to be a valid base64 string. I’ll compile it again, and hopefully I won’t run into the same error. Thanks a lot!

That's a great question, and you've hit on the key to a proper FX chain! You are totally right—if you're filtering the dry signal, it means your filter is in the wrong place.
To fix it, you need to make sure your Low-Cut/High-Cut filters are only placed inside the 'Wet' signal chain (the one that holds the reverb module). If you have your setup using a Split container (as discussed earlier), the dry signal should be on one side (no filters), and the reverb + filters should be on the other side.
That should keep your dry signal clean!

Always knew Hise was nothing but a superstition...

@David-Healey Thank you so much! I'll check it out now!

@David-Healey In the video you do Engine.setKeyColour(60, Colours.blue) and it seems to work, but I think I forgot about the object. Thanks a lot.

@David-Healey My apologies, was my bad.. I was pointing to the wrong HISE path. Everything is looking good now im sure. :)

@David-Healey Oh weird. Must've deleted it somehow. Fixed.

@Oli-Ullmann A broadcaster might be another option - not sure.

@David-Healey

Hey David, I found that using lazy load in the purge solves the problem. To a large extent, the pre-load time becomes negligible, just like when I have one sample loaded with -1 preload size. I think it’s the best solution for now.

Yay! I was able to get it working. I guess the bounds were off. Thanks for the direction.
b98cf78e-c9f8-467b-a244-fd364454ebd2-image.png

@ustk Yes, I deleted the Binaries folder and tried again and again. HISE already gives a "build failed" error and doesn't say why.

So, when I try to manually open and compile the AutogeneratedProject.jucer file in the Binaries folder, I see that error in XCode.

This is probably a bug with the current commit.

@David-Healey ha how do you think I feel, I'd already used it and got rid of it earlier in the project 🤷