@Christoph-Hart Interesting, I did not know that! Looking forward to the designers whining at me about Figma pixel-perfect accuracy! 🤣

It might be worth performing this rounding/clamping in the UI fields too, for consistency sake. I totally get it is a JUCE baseline thing, so I'm not going to whinge about sub-pixel accuracy or anything like that.

do you need to add anything to the extra preprocessor definitions when building in projucer to get this stuff to work properly? had to rebuild and figured I'd consult you guys before I move on.

@David-Healey Ok, I will keep that in mind

@David-Healey

WOW AWESOME!

Thank you!!

@David-Healey Yeah, it's gonna be cool!

@resonant Yes, your version clears all extended attributes on a file. Mine only clears the quarantine one.

I would recommend caution using the -cr option without knowing exactly what it's removing.

For my future self, or anyone else who finds it - I ended up doing this with a button instead of a label or panel.

const btnPresetBrowser = Content.getComponent("btnPresetBrowser"); const pnlPresetBrowser = Content.getComponent("pnlPresetBrowser"); // Show/hide panel containing preset browser floating tile inline function btnPresetBrowserControl(component, value) { pnlPresetBrowser.showControl(value); } btnPresetBrowser.setControlCallback(btnPresetBrowserControl); // Update button text when new preset is loaded from preset browser const UserPresetHandler = Engine.createUserPresetHandler(); UserPresetHandler.setPostCallback(function(presetFile) { btnPresetBrowser.set("text", Engine.getCurrentUserPresetName()); });

@David-Healey

SOLVED!

In the property editor you simpl have to set the processID and then set SliderPackIndex to 1 - voila.

Sorry for asking, hope it helps other people

Thank you so much

@treynterrio Try adding it

@cemeterychips realizing I need to take a few coding classes including Davids because I have no idea where to start with this haha! some people pick up crossword puzzles as they age,I guess I'm choosing coding😹 😹 .

@dannytaurus no nothing changed except the plugin version in project settings. the hise version was around half a year newer from the one i last compiled it with on the develop branch

@resonant said in How to detect and fix out-of-phase signals?:

@ustk @Orvillain ok I see.

Another one, is possible to detect pitch with fft in Hise without c++? I think this should be doable with Hise tools.

You'd be far better off getting something off the shelf and getting it into the scriptnode network. I'm not sure what is out there to be honest.

@David-Healey Thanks David!

Btw does the control.timer node sync with project bpm?

@parabuh I gave up trying and switched to Signalsmith which sounds better anyway (but has a bit more latency)

@David-Healey Yes, can't believe I missed that. Thank you David.

@iamsteinco thank you so much sir I will post a complete picture in my daw once its exported into your server

@iamsteinco I'm afraid I didn't get around it on my Mac. I compiled HISE using GitHub Actions.

It's a bit of a process but I eventually got it so that every time I push to my HISE fork on GitHub, it built the app on the GitHub servers. I would then download the ZIP, un-zip it on my Mac and move the HISE.app to my Applications folder.

The 'real' solution was to get a Mac with more RAM. I recently got an M4 MacBook Air with 32GB RAM and it compiles HISE in about 30 seconds now - no sweat!

If you want me to send you the files I used to build HISE using GitHub Actions let me know.

Solved. Thanks everyone.