Latest version of HISE breaks existing presets....

[David Healey]

@Lindon Yeah I'm not using macro modulators in mine. I'm just using the macro knob's as a way to make one knob on the ui control multiple modulator parameters without me having to script it.

[Lindon]

@David-Healey said in Latest version of HISE breaks existing presets....:

@Lindon Yeah I'm not using macro modulators in mine. I'm just using the macro knob's as a way to make one knob on the ui control multiple modulator parameters without me having to script it.

so pretty much the exact opposite of what I'm doing then....that should be enough of a set of test cases to test if any fix was completed.

[Christoph Hart]

Hmm, it appears that there is a pretty big matrix of all combinations of macros / matrix modulation / plugin parameters to be tested manually.

The commit in question was perhaps the worst thing I did in 2025 but there's no way back now so we have to somehow find a method to fix all cases and add some regression checks going forward.

[Lindon]

@Christoph-Hart wel as I say I can send you my project to use for testing - and if not then I can surely test using it...

[Lindon]

@Christoph-Hart So how are we going? Is this fixed by any chance? Im stuck on an April 2025 release until it is....

[David Healey]

@Lindon Not fixed yet as far as I can tell.

[Lindon]

@David-Healey bummer...

[Lindon]

@Christoph-Hart said in Latest version of HISE breaks existing presets....:

Hmm, it appears that there is a pretty big matrix of all combinations of macros / matrix modulation / plugin parameters to be tested manually.

The commit in question was perhaps the worst thing I did in 2025 but there's no way back now so we have to somehow find a method to fix all cases and add some regression checks going forward.

So still looking for this to get fixed, any chance?

[Lindon]

@Lindon Ok well all that new documentation looks really lovely, but until this is fixed I cant move to any recent version of HISE to avail myself of all its Claude based wonder.... I have to stay on a pre-april 2025 version of HISE to support one of the major projects in the catalogue.

What can I do to help get this kick started?

[JulesV]

Honestly, I experienced the same problem. Presets and saved settings from older projects don't load in the DAW Project with plugins compiled using the current HISE.

I think HISE's backward compatibility has been broken since this new modulation system was added. I have to stay on the January 2025 commit for now.

[Christoph Hart]

Guys I really need more to work with. Just stating "it breaks older presets" or "it seems to be upsetting HISE" gives me absolutely no idea what to look out for. I get it has something to do with macro modulation and plugin parameters, but it's a shot in the dark until I get more context.

• what does break
• ideally a snippet, if not a DETAILED list to reproduce the setup
• what does break mean? crash? values not restored? weird couplings between UI elements?

Ensuring backwards compatibility is the number one priority of all bug reports, so I'm on it as soon as I get enough info.

[David Healey]

@Christoph-Hart I think this one https://forum.hise.audio/topic/14165/latest-version-of-hise-breaks-existing-presets/26?_=1777890110567

[Christoph Hart]

@David-Healey yes I saw that - the reason for this is that HISE registers all macros as plugin parameters in the backend by default which then loop back to update their value.

It should not affect exported plugins though, but it's definitely a weird glitch that I'll look into. Is this a regression? The backend macro -> plugin parameter connection is ancient (about as old as HISE).

[David Healey]

@Christoph-Hart said in Latest version of HISE breaks existing presets....:

Is this a regression?

Yes it didn't happen in earlier versions. It came in this commit I believe.