@David-Healey I'd probably take vibe coded voodoo over 20+ years of legacy code and technical debt 😂

Like you say, a black box is a black box, so as long as what comes out of KODA works properly, it doesn't really matter what the code is like.

Totally agree of the ecosystem stuff. That's why I never developed for Kontakt (too much licensing overhead) nor used many, if any, Kontakt libraries.

I've looked into all the other systems you mentioned and they all have similar tradeoffs.

The only move I would make from here is likely to pure JUCE. With AI tooling even as good as it is right now, let alone what it will become, that's the realistic and practical direction.

@Christoph-Hart Great, thanks.

Where do I get a copy of the current licence? I was never sent one when I started paying.

@resonant - I think Dave's right there are not any real problems these days getting the plugin into the "system" folders on a Mac (but its been a while since I've done it as Im nearly exclusively on Tracktion these days) so caveat emptor... but every other problem (locations and content) are still there which is what the CR Setup componentry is there to resolve.

@David-Healey

FL Studio is so temperamental

Ugh, indeed. And not really something I can ignore.

I just did a user survey and FL Studio users are 8%, third largest after Live 61% and Logic 14%.

new updates
https://www.knobwebstudio.com/

@David-Healey It seems to have fixed the panel contextual as well! 👍

@GUJIAN The errors about component missing will always happen on the first compile because the components don't exist at that point. On the second compile the errors should go away.

Also Rhapsodist isn't "fixed" yet, so expect breaking changes. Once I've stabilised it I'll make some documentation.

@Lindon

Sorry yes my typo...

Glad you weren't being charged 5% 😂

@dannytaurus Great idea. I'll add this to the HISE/JUCE package updates.

Thanks!

@robJ Thank You 🙏

"OK, that's it. Thank you."

@LucaL check what's in that array, I don't know without seeing the rest of your project

@ustk Haha I am launching HISE with the cli most of the time and there it worked so I never bothered…

hise-cli -hise launch

@Morphoice
Ah, no but that is a reason to reset everything!
Under many conditions, changing parameter values all at once can produce monstruous audio. Like, if the DSP effect has feedback, if you don't clear all the buffers, the audio from before the switch, could blow up under the new parameters. There are scenarios that can sound really horrible or blow out your speakers. I mean, let's say the new preset has different reverb parameters, you'll get all the reverb knobs yanked while it's still playing, and get all that washy doppler... Of course that's not a horrible situation, but you can imagine that certain DSP would produce really loud nightmares. Which is why it's quite sane for Hise to send reset() on a preset change, to clear out all the buffers and start from silence. It's the safest thing to do.

But I agree that creatively, there are situations where this is not what you want. But you can understand why Hise went with the blanket solution.