@sletz Interesting! Thank you.

@Lawrence said in Compile Error:

No, I downloaded it from Steingberg as outlined in the instructions

Here are the up to date instructions - https://github.com/christophhart/HISE?tab=readme-ov-file#how-to-compile-hise

@treynterrio Concatenate the ternary operator:

(input < 0.5f) ? 0 : (input < 0.75f) ? 1.0f : 2.0f

@d-healey You can disable the native bar then choose which of the buttons should be shown. This lets them get styled with LAF.

I'm not sure if the ones that remain shown get auto-positioned, if so, it would probably be a good idea to introduce a minimize method which just calls the system function for minimizing, and then for close we can define our own behavior and call quit, and for maximize we can use the new UI rescale method and do all the math for scaling the components manually.

@Christoph-Hart

It works! Thank you!
I'll do a video on this soon in my scriptnode c++ series. I've been remaking the first few videos to make more sense and go into better depth.

@dannytaurus Alright, that's fixed now. I realized that pressing F5 in the code editor will also just save the currently edited file, which also might be confusing, so that's fixed too (I guess in my years of using HISE I never once edited a file without pressing compile afterwards)...

@ustk were-not-worthy-waynes-world.gif

Confirmed here.

When I close and reopen the Synth Group popup module window the Spread param resets to zero.

Seems like a bug.

I'm on develop branch commit db780f4f (Oct 1st).

@ustk said in Updating product and preset procedure:

But anyway if nothing bad can happen loading an older preset, I'm feeling relieved already

Yup as @orange said, if you're only adding new controls, just make sure that the default values are sensible and they will be initialised to those values.

There are more advanced tools available in the UserPresetHandler class, but they are only required if there are breaking changes in your preset design (eg. because you have changed internal ranges or something else).

@ulrik I figured it out...I had my sample maps named like "Elements_Element 004" same way in the code smh...I thought I needed to do that...when I took the "Elements_" off the front of my sample map name it started working! 😬

@dannytaurus said in Standard way to make icon buttons?:

is it common to have several LAF

Yes. You should make use of local look and feel where you can. The golden rule is to avoid repeating yourself, so if multiple controls can share the same laf there is no reason why they shouldn't.

For the few components that can only be styled globally you should use a single global laf object.

Do the width/height css properties do anything for buttons? I see width used for sliders in the docs but when I try to apply it to a button I see no change.

@DanH
Ok, it was easier than expected, There are some graphical glitches but the time in ms is correct.

f5fac53e-6003-4b3e-afe0-e3478c470e17-image.png

@udalilprofile said in Daw:

@orange . I made several copies of the same plugin, just changed the name. One of the three daws discovered.

Have you changed the "Plugin Code" in the Preferences section too?

@DabDab @Ben-Catman Thank you so much

Sorry for the late reply. I just realized that I'm using a 3rd party node for my LUT test.
Here's the full project you guys can take a look:
https://hub.korneffaudio.com/index.php/s/xPcEwQicPH63Fkd

@orange dope! yup I was able to restructure my gain and its working the way I need for it to now...this is good! gonna def check out the other thread...thanks!

@Ben-Catman
Set sample index to -1 I belive that this will do it

see the image above

@clevername27 If you mean this

Link Preview Image HISE | Docs

favicon

(docs.hise.audio)

Then it's not using the choke group processor but a custom script that replicates the behaviour. I think the snippet predates the native module, so I probably should update it to use the best practice.

@Mighty23 That did the trick - thanks! 🙏