Bump Bump :)

@d-healey It's just a simple call to JUCE's repaint() method that causes the UI element to repaint. The difference to the ScriptPanel.repaint() function is that this one will cause the scripted paint routine to be evaluated again.

You're most likely need it if you're using custom LAF that use external data to paint some components so when you change that data you can call the sendRepaintMessage() function - otherwise you would have to do some hacks like changing the width by a pixel or something to trigger a repainting.

@mehmethand Just so you know : I'm on Intel Mac / Monterey / Xcode 13.2.1,
compiling plugins works fine but the message is still there. Don't mind it, it's just a warning, not an fatal error.

@d-healey That would definitely be the one to watch. How I missed this one, we'll never know.

Just leaving this here in case someone needs this : HISE_USE_SVF_FOR_CURVE_EQ.
"hi_modules/effects/fx/CurveEq.h"

I've updated my coarse/fine tuning script to use the new Engine.setGlobalPitchFactor() API function. You can drop this script into any project and connect your UI knobs to it using the property editor, so you get the benefit of this functionality without having to do any scripting.

@iamlamprey Awesome! Let me give this a go!

@orange Oh that's great thank you! This app shows a list of only non-M1 compatible plugins, and my plugin is not listed here.

So, if I understand correctly, on a M1 computer, directly Hise exported plugins are universal binaries for both Intel and M1.

@d-healey Thank you! I will thy that 🙏

@dustbro A 4k monitor (or higher resolution monitors) user can't use the screen zoom in 100%, because the texts are very small with this setting.

So everybody uses higher rates like 150% or even 200%. I think this issue should be solved. @Christoph-Hart

@civet If you can achieve the result you want with a FloatingTile then use that. It's the native widget for this task and saves you work.

@Christoph-Hart said in Now M2...:

If you already have M1 hardware there‘s no reason to update IMHO.

Yes indeed. Maybe next year there will be M3, then A1, F1, Z9... :)

If the architecture is the same with just iterations, no need to follow that :)

@d-healey Ok thanks, I thought that it was a flag something like this format or something VST23AU=1 :)

@d-healey That's interesting and good. I have to do it on mine.

@Christoph-Hart Good to know that thank you!

@d-healey I'm haven't been working with scriptnode so any example will be a good starting point for me, if anyone has the time to do it.

Thanks

@d-healey Yeah but because it only measures the CPU usage of the audio thread (this is how CPU meters usually work in DAWs).

It's basically this: