@David-Healey That's where I use it (the blank part above it the bottom of my property editor)
But it's now back, I just needed to remove it and re-insert, probably a compromised window XML...

As the title say:

@Chazrox I thought I fixed it about 2 weeks ago. It was a line that was already there so I simply uncommented it and it was working nicely in Hise. But I suspected it made my plugin unstable/causing crash, so I just went back a step.

I'm not 100% sure it was the real cause, but since the line was commented, I think @Christoph-Hart had a good reason...

Why not just verify if it's on the disk or not and pull it from the server?
Assuming plugins are connect to the internet for your license system in the first place...

EDIT: or even simpler, pull it at the same time you pull the plugin's license...

@Lindon Yup that's because it needs to be thought more as "container" rather than strictly "installer". PKG or ZIP are containers so -> notarisation

4 over 4, that's enough stats for me

@David-Healey yup me too, I will just hold this a wee bit if somebody sees it differently

Currently, when we enable midi learn from right-click -> Learn MIDI CC, we can actually learn multiple CCs (the last one isn't replaced as it is reflected in the MIDI learn panel).

In the dropdown, only the last one is showing, but all previous CCs are still functional until you remove the last CC. Then they all disappear at once.

So something is off. Should we able to only learn/assign ONLY one CC, or should we keep the multi-CC capability and reflect this in the dropdown menu as well?

To me, there's no point in having multiple CCs for one slider, because you get jumping values as soon as you touch a different controller... But, that's just me...

I am in the middle of making a PR for this, so I'd need your opinion guys

SOLUTIONS:

1. Keep only one:

• Easy, just replace the last attributed CC with the new one

2. Keep multiple:

• I would then:
  -> Tick them all in the Assign MIDI CC sub-menu
  -> Expose all "Remove CC#"
  -> Add a "Remove All CC"

I thought at one point the "full mod range representation" has been made available so it covers the full range of lastModValue (like in the above post)

Was I dreaming?

@brucerothwell IPP is not needed for Hise, so yes, you can always drop it. For windows it only needed for accelerating convolution reverb and a few other things.

When you say Hise 4.1, do you mean you haven't built it from the develop branch? the current version i 4.9.
You also need to pull the JUCE submodule from git into your the Hise folder.

Then compile Hise and let see what you get

Once you have a recent and stable Hise base, you can try export your project again

@dannytaurus Yup I am

@brucerothwell Yep, I use it everyday (26.5)

@Phelan-Kane not my expertise field, but would that help?
https://forum.hise.audio/topic/14270/how-do-you-set-up-external-modulation-slots-c

@dannytaurus Yeah, keeping the colours tidy in your code is easier in the end. Then you can set the component colours from script when needed and everything updates automatically if you adjust something instead of copy/paste in all components...

I tend to to everything I can in paint routines, the less components in the tree, the happier I am!
That being said... In order to reduce CPU load, I still tend to keep fixed drawing (bg, mask, etc...) in separate panels so the LAF function job is only constrained to what is really necessary. I also keep all the math constants externally, unlike the example...

Other issue with the "multiple panel masking technique" is that when you want to move it, it can be very annoying, unless adding them all in an holder panel, which is one more component...

@dannytaurus

HiseSnippet 1342.3ocsW80TabCDWGvkhcZxjzoe.tgmNmRM1TCAlLcpwFC3g+XO1jj19BUVmNaUNKcUmLfaGloez5mm9T+FztR24y2ELoTll6AXzpc2e+zpc0ttqTPnQQBIxp34SCoHqO2t+TtZTyQXFG0dej0ysOEGonRmXQMlFhihndHKqkOTKvpvJHy2e8cMvAXNgNWDB8NAiPOgMlolKMr9wrffCvdzyYiyncs5sIBdSQfXBvmksqfBwjKwComg0psjM5HbzHj0qr2kPH90p4uYURsp01Y6A6Vk3SFr4l6V40daR8Fr8.Jc2c7QVOokGSIj8UXEMBYsRCg2z9iDWyiA3crH1f.pdQUTe.4XwGHB7zGQsTTyQr.utyBTQHvKcmG1VNNr8k1mx7XoxmG9dgYCm4VjM.ZsTd5sbN5UMK8pjgdKfRVYnzJwT5k18IRVnZ9NZ97EIRuGFEuIZo+z1tofqnbU4w3KoGHgEsg0ReLg5tckJq6.+ozaJVDtxhTNWgkNcwbZPUmu0YlkCoplhwgBNrvcs3sWCrYtIDgjSkGyGbuVkpQdC8XQgA3oPp4kMT76057pocQwhR5Pmlc5cVqdWzu8O1BrsR4J5MhIX4HppKb6o5IlnXbpq+DNQwDb2gkJ9aEKnQuwgWzryIcdaOsw236W078lhEFV1GRs2KHvMUE.yBwVc9EGJoTMY2RCnQVuTYYozWOS2M1LUy8R0TMhEoOmmHH3fFhIbuH2JkJKodSHTO2LllEacL.L18TrZT4neQpb0J37pr.WBPNgQo7KwtYD8qRbUNlknSBEKSuIDy8LTYlpwLYiMbhXimD.Y6Ng.OzArH8Eltj2M9eQkCXCGoFp8TISH0Shu9D8MAbOsd5o+8LO0H2RyEbDUamVhQujvPJvq4iChnq4LFXTdbycUECWOcTk50iRTX9v.pa7Yb8j3w5IAgTmaXKjMyUfCe3mpE.igzqOKbe2iwOOAp.TBmH3UB3nSSNOLeG27I65Px6vASntkJUr.j3liUUtYqs78qTwTCW3+9o91h2ZJlfOFO.tbblUl3H3o0r5hRoHvkLqhbcn3EnjoPJeMnQN33jhPIMTWC5BfbqttOwgwm.iSahCBF.8GbuKdIL6tDKeD5ixtExiOHBuPxrPL.yyPiyDJZGtqAmh2Vz4C2x2eg6k3q.pbgaqalJ+XF5xmLd.Ul8TpUDZXjuKj882EJaSRR7KtYTTvayYpNgT9805Dk7LstiUBq.UUl9UOOoyT+.lGUhXP+nmZmd0hLjNYXAms2oSczaauOVgm4Jvq.RgTohoODV6SuBF8HtUXA68oQWpDg.XocGPVe1CB3aRmP4OFTeZ5h5+TcXrnv9reM2.Oiwy0G8C0Uza.fV0NNYWe9SQ+Iwn+rYso0IbFvW0NN4CkySyQFwpes9wu4BlVej4wurpjEpUyePaLQoDbCVuvNe9ZVLUYv72w0obLjEnml4DJVx0SKDe5dpc+i57dmS2q+wnH7Uz17tRJTan0fEcpXLvArD7k0Rn6NlBLfjvS2RH+TS5YKS1.RhyMihdNDdDSMM6rm+uMJ0CkhuztKSQFsXNtzB3Hjn9ofiICf9L6V99vC2yI3J1G78eZl1DEOZzPXTBICRXrOax39PWEBEPmCot5GQfKasol0Uzq0Qf9TtmYweCeIaVUu1JYypy1DJjHRwEj3GIzi3tpQBvIt4mCT.9cIvZmp4dYHtFDxQufPx6p6X3lOVC+lGqg0drFt0i0vserF95Gqg67uan9Ij8lnDiiKaPnS61x7RtkUKyaLlrUz+.THMMq.

R0 = CORNER_SIZE

@dannytaurus I have two ways to treat this in one panel. The first one should be THE way but is broken for so many years, the second is dirty but works nicely:

• Mask -> still broken (I’ve made a quick fix but it still crashes exported plugins)
• a first drawRoundedRectangle larger than the green one, and with thicker line landing precisely on the outer edge of the green one. So you need it thick enough, and compute the precise coordinates, This way it is acting like an outer mask. Then draw the green one normally on the top.

@dannytaurus Or spare a component by drawing the path in a bigger area

@dannytaurus I reckon this has been added quite recently with the intention to remove the noise.
So if it always worked before I see no harm in disabling it.

@David-Healey Same...

@David-Healey Noice!
Have you had a look at the PR count lately?
AI's in the place...