@Dominik-Mayer Awesome!!!!!

@clevername27 Use LiceCap

@d-healey You are kind, thank you. I'll donate some code. 🚀

@Simon Thank You

@Lindon
Got it, got it.

Guys, you are AMAZING!

Thx so much!!!!

@ulrik Sweet! Thank you so much!

@d-healey said in Call an inline function from another inline function?:

you should use a value broadcaster in the second namespace - or in both if you're using my fork.

I watched your video about the broadcaster a few days ago, but I hadn't tried it out until now. Hehe. I just tried it, and it worked :)

@d-healey said in Call an inline function from another inline function?:

I think the reason for the crash is because you don't have a reference to the knob in the first namespace.

Edit: I just realized that the crash was due to something else in the main knob (it was the knob I had posted a few days ago about unload and load the convolution reverb to update the setRange). https://forum.hise.audio/topic/11188/audiofile-setrange-won-t-increment/6?_=1734032060483

@d-healey
It's actually not the first time that “fillRect” works better than “fillAll” for me. I can't remember why I changed my mind before, but as I said, it has happened before. Also on the Mac.

@Simon said in vst3 is a folder in Windows?:

@Sampletekk Nope! Despite the deceptively consistent "vst3" naming, they must be separately compiled for whatever platforms you want them to run on.

👍

@njAudio03 Disable IPP in your project preferences.

@njAudio03 Yeah I did try ticking the box and it wasn't the issue. I have literally just figured it out tho! I had already had projuicer on my computer and that was upsetting Hise so i got rid of the duplicate version and it's working now. Thanks for your help.

@d-healey ehh Apple and their stupid ideas :/

@HISEnberg Thank you very much for your help, indeed the problem was the space after "Jucelay." Have a wonderful day!

@DabDab said in I'm having issues converting an SVG:

@ustk Thank you. Got the fundamentals. one last question. How can I do tracking circle?. Increase /decrease just like regular knobman things.

With

Content.createPath()

and

Path.addArc(var area, var fromRadians, var toRadians)

Multiply your arc endpoint (var toRadians) by obj.valueNormalized.

@d-healey nice find! Though this kind of static thing seems simple enough "on paper", like you can do this using higher order filterband in Faust (though it doesn't have triangular filters) but keeping track of data could prove tricky, you'll have to do it in Faust using tables (if it's even possible) because vbargraph is broken in compiled Faust nodes so you can't take it out of ScriptNode).

But then pro-q's matching algorithm constantly shuffles around until it gets to the best fit, and prefers using higher order peak filters... If you compare all other matching algorithms, they still can't beat even the old pro-q2.

@ustk said in Is there a way to get the bounds of the front interface?:

@VirtualVirgin Yeah like Dave, I always start my interface script this way:

const var INTERFACE_WIDTH = 1000; const var INTERFACE_HEIGHT = 623; Content.makeFrontInterface(INTERFACE_WIDTH, INTERFACE_HEIGHT);

So this can be used everywhere

Thanks :) I just added this and it does what I needed.

@ustk said in How can I improve the tracking when using LAF on a slider?:

Forgot to mention that mouseSensitivity is working only for rotary sliders, so just change that and the LAF function and it'll work

Thanks :)
I changed the LAF and the component over to rotary/knob and now the mouseSensitivity does work.
Setting it to 0.35 seems to do the job.