I'm still hitting some bugs with this.

@Christoph-Hart I think you should take a look into this because it is a very good point.

So far I haven't really ran into this situation because most of my projects only have one or two presets. But I'm developing a project at the moment that might have 100 or more presets and this will definitely be an issue.

If a user has a set of CCs they like to work with then they likely want to set it up once for the entire instrument (all presets past, present, and future) and forget about it. They don't want to have to redo it each time they add an instance of the plugin.

With this instrument wide setup I don't see a reason to distinguish between daw load or user preset because the source of truth will be a separate file that can be read in both situations.

I'm currently trying to implement a working solution through scripting but I'm running into annoying issues with setUpdateCallback because it fires at init - it fires multiple times when using full instrument expansions. I'm gating it currently with flag variables but still haven't got it working reliably yet, and the code is a tangle.

-- Should also include macros and MPE assignments too.

@Lindon I gotchu on both. 👍

@ustk
Ha ha :-D
I feel exactly the same way!

@Chazrox Yes, been using it, will show up in the next design :)

@ustk Yeah, definitely be good to get the nod from Christoph on a lot of these PRs.

Claude does a great job of making and testing bug fixes, but only Christoph really knows where the dragons are hiding in the code! 😜

@David-Healey I ended up with this problem after following the video so I'll give the appstore method a try

@smm-panel Honesty strikes spams again...

@ustk Hmm.. I think I'll keep away from it for now. Don't need it for a while yet, thankfully.

@ustk said in Claude's ugly code:

@David-Healey You can ask Claude to analyze your previous project styles once for all so it automatically applies it next time

Definitely you can, and it often shows up as a big improvement. I find after time that Claude, Codex (probably other agents too) start to "drift" towards their preferred style of coding anyways. They also have a tendency to over-comment and use special characters which HISE doesn't support. Example:

// ── Backend ─────────────────────────────────────────────────────────────

Which renders like this:
Screenshot 2026-07-12 at 1.04.27 PM.png

I also see it drop things in scripts that are outside a namespace, and the namespace does not always match the script's name. Example file: HiseScriptStandardsForMyAgents.js:

namespace ScriptStandards { // Rules for following strict scripting standards inline function iDontFollowTheStandards(); // .... } iDontFollowTheStandards(); // End of HiseScriptStandardsForMyAgents.js:

I wonder if more rigid guidelines around the HISE scripting standards in the HISE-MCP would help, but most important caveats are already featured in style-guides.ts and in the guidelines. Seems like Christoph did a bang-up job already and agents just have a tendency to cut corners over time to in order to complete the task.

@Yannrog Yes, loop over your list of sample maps and use if statements to place the sample map names into two new arrays.

Then use those arrays to populate your comboboxes.

Just giving this one a bump. Same problem as before.

Each heavyweight function (loading presets, samples, etc) gracefully fades out the audio, suspends the processing and then resumes audio processing. This is a core engine behaviour and you can't do anything about it. Changing this will create audio glitches, incontinuities and crashes.

@observantsound Confirmed here on Linux

@ustk take my money! 😆

@ustk Thank you so much,

This it it.

UPDATE: Auto-Detect + Dynamic GUI Sizing

When you download the HISE package, you will not be required to enter the GUI size anymore as it is auto-detected directly in your project. Thanks @David-Healey

Also, the complete HISE package is dynamic and will change dimension based on changing GUI elements (like an expandable keyboard or effect section). Thanks @dannytaurus

For example: Customer didn't pay for their subscription, grace period ends, they are using plugin now with the keyboard extended. The plugin will pause, popup the activation webview, and the webview overlay will still block the entire plugin, not just the original size.