Well, JUCE 8 looks like it'll have full animation features so hopefully HISE migrates over to it once it releases and we can have proper hardware-synced animation without all these shenanigans and workarounds 😆

@d-healey I knew that there was a function thought it was startAsProcess.

Thanks alot, its just to damn hard to find anything in the docs.

Here is a code snippet which gets the current selected Theme in MacOS.

const var b = Engine.createBackgroundTask("GetDesktopTheme"); b.runProcess('defaults', ['read', '-g', 'AppleInterfaceStyle'], function(thread, isFinished, data) { Console.print(data); });

@clevername27 the laf also applies to components within the viewport so just register the laf to the viewport and overwrite the combobox draw methods.

@d-healey Meu muito obrigado, tinha desistido do HISE pelo motivo que preciso de 16 tracks mono para sair na DAW, como peças de drums, mas vou tentar novamente se caso der certo vou entrar no petreon para me aprofundar mais

Some info in this thread too which might be useful (might already be covered in the docs of course) https://forum.hise.audio/topic/6609/choke-group-processor

@oskarsh ahhh, I was changing the "0" for the key. My mistake. I will try this again when I'm back in the studio. I appreciate your help.

Yes, I do need to get through all the docs. Definitely not where I'd like to be.

Goals...

@d-healey Ah that's it, knew it was something simple! Thanks.

@d-healey @Christoph-Hart

-- well whats wrong with it is that it just didnt occur to me.....;-) So ignore me..

@d-healey Brilliant! Thanks 🙏

I would make this rather a polling function like getNumBufferUnderruns() that will get reset after every query so you can ask that from a timer callback, but tucking this onto the ErrorHandler is a good idea.

@Christoph-Hart could you tell me more about the skew factor applied to the gain of the group xfades?

@Christoph-Hart ha you know what I meant.

thanks 🍻

@aaronventure I've added the gin stack blur at some point (it's already using this algorithm in the Graphics functions), however it's still ridiculously slow because it has to do graphics operations on a CPU and this is 1970 style hardware usage.

https://forum.juce.com/t/faster-blur-glassmorphism-ui/43086/7

I've went through the thread a few months ago and was close to port it over into HISE (I also sometimes get the urge of making blurry stuff), but I wasn't too convinced that the overhead justifies the performance gain (it's still being calculated on the CPU and this makes it easily a factor 100 slowdown compared to GPU based blur algorithms).

EDIT: this is the module I was talking about:

Link Preview Image GitHub - sudara/melatonin_blur: Fast cross-platform CPU blurs and shadows for JUCE

Fast cross-platform CPU blurs and shadows for JUCE - sudara/melatonin_blur

favicon

GitHub (github.com)

From revisiting the page, it might be actually worth it trying out how it performs...

@d-healey just what i needed thanks

@Lumi283 that double semi colon at the end probably isnt helping much either...

@Christoph-Hart I think I found the reason it didn't update.
I had 6 slider packs in a separate ScriptProcessor, all of them registered with

SLP1.registerAtParent(0); SLP2.registerAtParent(1); etc...

In the main script I have 6 slider packs connected to the separate script processors slider packs using this connection:

const Data1= Engine.createAndRegisterSliderPackData(0); const Data2 = Engine.createAndRegisterSliderPackData(1); etc... slp1.referToData(Data1); slp2.referToData(Data2); etc...

I chosed that type of connection because I needed a DisplayCallback for each one of those slider packs, I couldn't find any other way to get that type of callback, is there?

Any way, in the external script processor I changed the

SLP1.registerAtParent(0); to use the SLP1.referToData(Data1); method instead, and that fixed my problem.

What kind of connection is preferred if you can't connect them via the Property Editor?