@Christoph-Hart Yeah in the end it wasn't hard to just jump between Rectangles and arrays

area = Rectangle(fromArray).modify().toArray();

@Christoph-Hart oh yeah a buffer why haven’t I thought about that… I’ll try.
My array is only made of numbers, but I’ll check in case an undefined is hiding somewhere…

@d-healey I will, I just discovered an error I've made that might be an happy accident... Need to test further...

@Christoph-Hart That was it! Thanks Chris! 😎

@Christoph-Hart What's the reason we can't have both regular laf and css playing together on a single control?

@Dan-Korneff That fix is included in the latest commits now BTW.

@ustk said in Network range mismatch:

@Lindon but does the warning stay in certain cases ?

yeah - but very rarely

@Christoph-Hart What about the slider pack limitation of 128?

Could it be extended?
Or perhaps it would be better to use a cable with complex data to send a more precise curve?

@Christoph-Hart Ok cool, I did tried it successfully once but wasn't able to understand why I couldn't anymore... Makes sense...
The doc say something about that flag, but my mind wasn't set to understand the viewer needed it ☺

@ustk I don't think so, behind the scenes they are both running the same batch file. The only difference I've noticed is the Export Wizard is buggy and gives different options than the Old export.

@ustk I'm not sure. Check if it clears the AudioUnitCache folder - Users/username/Library/Caches/AudioUnitCache

@ustk said in Customer hitting a lot of connection errors with my manager application:

Thinking about worfence, it's in learning mode when the problem happened anyway.

So for now it might be the captcha thing, since I've read similar issue online, but it was 2021 with jwt v1, so it's strange.
And I'm definitely not the only one using recaptcha v3 out there.

Disable both and see if the problem goes away.

@aaronventure Thought this one was new… Damn!

@Christoph-Hart said in fx.pitch_shift not working in a multi channel network:

@ustk haha don't use that, I'm probably ditching it again soon.

Other than the glitches, it was doing its job really well. I hope there's a good one to replace it with after ditching this one. Or whatever the problem is with this one, I hope it gets fixed.

@orange Well I'm not sure this applies, because ProTools does load with the previous state of each instance, be it on or off.
While in other DAWs, all instances get initialised with the pref file, be it on or off...
So the default value seems to have no effect on this.

UserPresetHandler.isInternalPresetLoad() might help to decide if it's a DAW state that is restored or not... But a pre/post load callback is for preset loading, so if this applies to instance restoration I don't know, I have to experiment... Maybe it's a matter of creating a flag that authorises or not the loading of the pref file, hopping this won't interfere when first inserting the plugin on a track.

@d-healey The very definition of a theory is that it's the better explanation we have until a better one replaces it... Well, I can live with this one for a while ☺
Thanks Dave 👍

@ustk said in Updated presets extraction... Did I miss something?:

I was still testing things I didn't updated to a higher version number (still 1.0.0).

Good point, you could change the version number in the preset xml to test without changing your project version

<Preset Version="1.0.0">

Let us know if it works.

@d-healey I was thinking about the delete one as well and somehow managed to forget writing it...