@observantsound 🙏

@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.

Finally got it working. I had to add several flags to guard against my save to file function running and overwriting the stored CC values.

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.

@manued12 said in Looking for HISE help – Simple Sample Mapping + Looping:

Files are already correctly named and prepared

If they are named well all of the steps except the looping can be done in about 30 seconds using the token parser.

So you're basically paying someone to loop your samples - I would suggest looking into auto loopers like LoopAuditioneer first - because anyone taking the gig is going to be doing that ;)

@Sifres @dannytaurus I've started to add this because its already a popular method to use a slider to make peak meters. Coming soon! 👍

@BWSounds In that case try a different xcode version, one up or down from your current one - not sure which I'm using, it's been a while.

Also only use the JUCE6 branch, JUCE8 is currently broken.

@GUJIAN No, but you seems to be trying to use Rhapsodist in the second image and the template in the first image.

Thank you! That all makes sense

@griffinboy

I realized that these plots are a little misleading.

The VCS3 filter is highly nonlinear and "bubbles" and so taking a measurement of frequency response is quite difficult since the filter is moving around on it's own accord all the time...!

Here is a more detailed FFT that shows how the filters do match more closely than the graphics in my paper would suggest.

.

Black is the slow accurate VCS3, Red is my optimized VCS3.
Not oversampled.

c4000_fb9_m42__one3_c050_k2.png
c10000_fb9_m42__one3_c050_k2.png
c2000_fb6_m42__one3_c050_k2.png
c10000_fb9_m42__one3_c050_k2.png

When oversampled, I found the proposed model to be perceptually close to the slower accurate model. The resonance and cutoff and gain values differ slightly, but the important aspects of the filter are retained.

Update!

Dual SVG capabilities for buttons such as this.
(shown compiled in HISE)
DualSVGButtonWorkingExample.gif

Both import methods and settings panels are identical but are independent from each other between button states.

Screenshot 2026-07-05 at 9.10.52 PM.png

Screenshot 2026-07-05 at 9.14.27 PM.png

And If you didnt already know...
You can also do some pretty nice LED's with the app as well! 👍

Screenshot 2026-07-05 at 9.17.58 PM.png

Screenshot 2026-07-05 at 9.17.25 PM.png

Screenshot 2026-07-05 at 9.18.37 PM.png
They're available now in the preset menu.

@ustk I'm indeed still on the latest stable release...
I read it as 4.10 instead of 4.1 so I was convinced I was on the latest version.
I'll compile from the latest develop branch instead and try again.

So what state is the mod matrix actually in?
Do some things work but others don't?
I'd just like to know what to look out for, if the documentation isn't super up to date.

What are PRs?