@d-healey @Christoph-Hart Indeed I had to change the flag in the projucer. Now its working again. I make sure to double check that flag in the future.

Thanks for answers :)

@d-healey Yep! Finally... 🥳

@d-healey Got ya - I was posting the code to get the component ID in an LAF function.

@ulrik Wow That's amazing! Thank you so much bro! Yes of course this will does the job for me.

@d-healey said in GPL compliant releases:

Ah I just found the confirmation

Can I put the binaries on my Internet server and put the source on a different Internet site?

Yes. Section 6(d) allows this. However, you must provide clear instructions people can follow to obtain the source, and you must take care to make sure that the source remains available for as long as you distribute the object code.

Thank You @d-healey you've been a great help ! 💪🏼

@Christoph-Hart Two interesting things I noticed with my "fix". Debug builds of HISE give a segfault, and my compiled plugin crashes pluginval. I guess this is related to the leak problem.

However it's much more pleasant to work in HISE when I don't have this slow issue so I'm thinking a pre-processor definition is the way to go until a proper fix is possible.

@musictop I'm not sure, I've never used a synth group.

@orange Because delay is not a fixed value. Unfortunately, it is constantly changing with band split frequency values :/

@ulrik I can't remember but I think so. Try it and report back :) Of course there is nothing stopping them editing them through the file system.

@ulrik youre the man!! thank you very much :D

Perhaps these functions can help (I've never used them)

a07cee40-438b-48d2-8b44-133bce1fefdc-image.png

@trillbilly but it will be a good exercise. Start with just a simple delay line, so you can get the way it works, and then you'll be able to go multiband 👍

@johnmike the maps get compiled INTO your plugin so you cant do this without having to recompile your plugin.

Just call startTimer again with the new interval.

Whatever you do I think sitting back and wait until AI has replaced your skillset is the worst option because then it already has. Also music software is a super small industry with no incentives for big tech to dabble in so we‘ll rather see a development on the text to music technology that will negatively impact the target audience (like what happens on the AI image front at the moment) than a completely automated AI solution for creating plugins.

@Lindon Firstly, I suggest you change the name and ID of the plugin and re-compile it. As I see you've already done that.

So, are there controls that change the values ​​of the parameters that are isPluginParameter enabled? If yes, you should make them also isMetaParameter. Otherwise AU plugin validation fails. Maybe that could be related to VST3 too.

Other possibility is compiled custom .dll nodes. If the target value and controller value ranges are different each other, that causes crash in DAW. So make sure that parameter ranges (including the middle points) are the same.