<![CDATA[Latest version of HISE breaks existing presets....]]>Well this one has me stumped. I update to the latest version of HISE today, I've been on an older version whilst a couple of products were released and supported thru the early adopted process...

For at least one of my projects the preset load seems to be broken, in that it's setting a number of widgets to their max value, e.g MasterVolume is being set to 30 (its dB max) for about 60-70% of the presets...and a bunch of other widgets are similarly affected.

Its a very big project (when are they not these days) so I cant post a snippet...

I did this to try and see where it was happening:

inline function onMasterVolumeControl(component, value)
{
	//
	MasterSimpleGain.setAttribute(MasterSimpleGain.Gain, value);
	Console.print("we are setting the Master volume to:" + value);
};

and got this back from the console:

Interface: we are setting the Master volume to:30.0
Interface: we are setting the Master volume to:-3.499999046325684
Interface: we are setting the Master volume to:30.0
Interface: *******START the post load callback
Interface: we are loading a preset for version:30100.0
Interface: *********END the post load callback

Here's the relevant line in the preset:

    <Control type="ScriptSlider" id="MasterVolume" value="-3.499999046325684"/>

I've triple checked and nowhere else is going anywhere near the MasterVolume widget....

So...something is setting the widget value to 30 for some reason, then the value is being set by the preset load correctly, then this thing is re-applying this 30 dB value....

Theres no timers running or broadcasters...

clueless

EDIT: oh and I've tried resetting the widget to its correct value and resaving the preset, then reloading - no change this "30 maniac" is still doing its thing...

EDIT: OK it turns out its WAAAY worse than this - every preset is doing "this" as well, so no MasterVolumes are being set to their correct values:

here's the console for a bunch of preset loads:

Interface: we are setting the Master volume to:-4.700000762939453
Interface: we are setting the Master volume to:20.0
Interface: we are setting the Master volume to:-4.700000762939453
Interface: *******START the post load callback
Interface: we are loading a preset for version:30000.0
Interface: *********END the post load callback
Interface: we are setting the Master volume to:30.0
Interface: we are setting the Master volume to:17.0
Interface: we are setting the Master volume to:30.0
Interface: *******START the post load callback
Interface: we are loading a preset for version:30000.0
Interface: *********END the post load callback
Interface: we are setting the Master volume to:-4.700000762939453
Interface: we are setting the Master volume to:-5.999999046325684
Interface: we are setting the Master volume to:-4.700000762939453
Interface: *******START the post load callback
Interface: we are loading a preset for version:30000.0
Interface: *********END the post load callback
Interface: we are setting the Master volume to:-4.700000762939453
Interface: we are setting the Master volume to:9.200000762939453
Interface: we are setting the Master volume to:-4.700000762939453
Interface: *******START the post load callback
Interface: we are loading a preset for version:30000.0
Interface: *********END the post load callback

It sort of looks like the preset load code is looking at some other widget.....

]]>https://forum.hise.audio/topic/14165/latest-version-of-hise-breaks-existing-presetsRSS for NodeSat, 09 May 2026 17:00:49 GMTMon, 05 Jan 2026 12:04:05 GMT60<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Tue, 05 May 2026 09:20:12 GMT]]>@Christoph-Hart I think not. As this is showing up in HISE as well as compiled plugins.... see my posts at the start about using Console.print to tell me whats happening...

Sent you the project link to your email

]]>https://forum.hise.audio/post/120097https://forum.hise.audio/post/120097Tue, 05 May 2026 09:20:12 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Tue, 05 May 2026 08:59:11 GMT]]>@Lindon Would it be possible that the single error that both you and @JulesV are experiencing is because of a drift between the plugin parameter value stored in the DAW project and the internal preset?

Whenever you save a DAW preset, it will

  • create a .preset containing the plugin state (exactly as if you would save a user preset)
  • store the values of all registered plugin parameters

and dump that into the binary data blob stored as DAW project.

In a "healthy" plugin, these values should not drift - the plugin parameter value is the value stored into the preset. But if there is a mismatch (either because of a new plugin parameter that wasn't stored or because of some initialisation error at startup, it might create these issues.

]]>https://forum.hise.audio/post/120095https://forum.hise.audio/post/120095Tue, 05 May 2026 08:59:11 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Tue, 05 May 2026 07:42:50 GMT]]>@Christoph-Hart said in Latest version of HISE breaks existing presets....:

@Lindon yes send over.

So your particular problem is that plugin parameters + macros + preset recall is not working (mastervolume +30 = 1.0 normalized)?

yes that about sums it up - I will send it over...

]]>https://forum.hise.audio/post/120092https://forum.hise.audio/post/120092Tue, 05 May 2026 07:42:50 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Mon, 04 May 2026 14:32:38 GMT]]>@Christoph-Hart In the plugin, all controls are set to plugin parameters. Also most of them are set to isMetaParameter. And all controls are initializing with default values

]]>https://forum.hise.audio/post/120062https://forum.hise.audio/post/120062Mon, 04 May 2026 14:32:38 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Mon, 04 May 2026 14:04:17 GMT]]>@JulesV Are you using plugin parameters? And is this affecting only controls that are linked to plugin parameters or all values?

]]>https://forum.hise.audio/post/120056https://forum.hise.audio/post/120056Mon, 04 May 2026 14:04:17 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Mon, 04 May 2026 13:33:15 GMT]]>@Christoph-Hart When I open a project previously saved in a DAW using a plugin compiled with 2024 commit HISE (I only tried in Reaper and Logic on macOS), with the same plugin compiled with new HISE, the saved settings are not loaded in the DAW. The plugin is loaded with the default state.

]]>https://forum.hise.audio/post/120048https://forum.hise.audio/post/120048Mon, 04 May 2026 13:33:15 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Mon, 04 May 2026 12:34:02 GMT]]>@Lindon yes send over.

So your particular problem is that plugin parameters + macros + preset recall is not working (mastervolume +30 = 1.0 normalized)?

]]>https://forum.hise.audio/post/120043https://forum.hise.audio/post/120043Mon, 04 May 2026 12:34:02 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Mon, 04 May 2026 12:29:46 GMT]]>@Christoph-Hart I know its a long way back but if you look at the first three or so posts in this thread I think that does dumb it down , and explain exactly whats happening.... let me know if thats not enough, I can send the project without the samples - as Im pretty sure they wouldnt be needed to see this problem anyway....your call.

]]>https://forum.hise.audio/post/120041https://forum.hise.audio/post/120041Mon, 04 May 2026 12:29:46 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Mon, 04 May 2026 12:26:15 GMT]]>@Lindon yes but please give me some guidance on what to look for. Also if you can dumb it down so I don't have to download gigabytes of samples, would be great.

]]>https://forum.hise.audio/post/120039https://forum.hise.audio/post/120039Mon, 04 May 2026 12:26:15 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Mon, 04 May 2026 12:25:27 GMT]]>@Christoph-Hart do you want a copy of my project to test with?

]]>https://forum.hise.audio/post/120038https://forum.hise.audio/post/120038Mon, 04 May 2026 12:25:27 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Mon, 04 May 2026 12:20:42 GMT]]>The code that sends the macro value as plugin parameter is already in HISE 4.1.0.

What changed in that commit is that HISE registers a plugin parameter at index 0 for the UI control (basically what the compiled plugin is doing) so before that value was sent out to nirvana (or the DAW if HISE runs as a plugin), but now it loops back to the first UI component that is defined as plugin parameter.

HISE_MACROS_ARE_PLUGIN_PARAMETERS=1

This solves the problem my registering the 8 macro controls as plugin parameters, so changing the first macro just changes the first plugin parameter (=macro) => no op.

So the proper fix would be:

if USE_BACKEND && HISE_MACROS_ARE_PLUGIN_PARAMETERS==0 => don't send the macro value as plugin parameter

if USE_BACKEND && HISE_MACROS_ARE_PLUGIN_PARAMETERS==1 => send it

Note that the compiled plugin is completely unaffected by this. All it would break is the behaviour of HISE to send out macro values as plugin parameter without that flag.

]]>https://forum.hise.audio/post/120036https://forum.hise.audio/post/120036Mon, 04 May 2026 12:20:42 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Mon, 04 May 2026 11:56:39 GMT]]>@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.

]]>https://forum.hise.audio/post/120030https://forum.hise.audio/post/120030Mon, 04 May 2026 11:56:39 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Mon, 04 May 2026 11:54:24 GMT]]>@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).

]]>https://forum.hise.audio/post/120028https://forum.hise.audio/post/120028Mon, 04 May 2026 11:54:24 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Mon, 04 May 2026 11:48:09 GMT]]>@Christoph-Hart I think this one https://forum.hise.audio/topic/14165/latest-version-of-hise-breaks-existing-presets/26?_=1777890110567

]]>https://forum.hise.audio/post/120026https://forum.hise.audio/post/120026Mon, 04 May 2026 11:48:09 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Mon, 04 May 2026 11:44:21 GMT]]>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.

]]>https://forum.hise.audio/post/120024https://forum.hise.audio/post/120024Mon, 04 May 2026 11:44:21 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Mon, 04 May 2026 10:16:30 GMT]]>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.

]]>https://forum.hise.audio/post/120018https://forum.hise.audio/post/120018Mon, 04 May 2026 10:16:30 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Mon, 04 May 2026 08:20:27 GMT]]>@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?

]]>https://forum.hise.audio/post/120017https://forum.hise.audio/post/120017Mon, 04 May 2026 08:20:27 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Mon, 13 Apr 2026 15:09:54 GMT]]>@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?

]]>https://forum.hise.audio/post/119439https://forum.hise.audio/post/119439Mon, 13 Apr 2026 15:09:54 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Wed, 04 Feb 2026 11:16:33 GMT]]>@David-Healey bummer...

]]>https://forum.hise.audio/post/117403https://forum.hise.audio/post/117403Wed, 04 Feb 2026 11:16:33 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Wed, 04 Feb 2026 11:03:00 GMT]]>@Lindon Not fixed yet as far as I can tell.

]]>https://forum.hise.audio/post/117401https://forum.hise.audio/post/117401Wed, 04 Feb 2026 11:03:00 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Wed, 04 Feb 2026 09:24:42 GMT]]>@Christoph-Hart So how are we going? Is this fixed by any chance? Im stuck on an April 2025 release until it is....

]]>https://forum.hise.audio/post/117398https://forum.hise.audio/post/117398Wed, 04 Feb 2026 09:24:42 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Wed, 07 Jan 2026 12:37:03 GMT]]>@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...

]]>https://forum.hise.audio/post/115522https://forum.hise.audio/post/115522Wed, 07 Jan 2026 12:37:03 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Tue, 06 Jan 2026 18:55:51 GMT]]>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.

]]>https://forum.hise.audio/post/115446https://forum.hise.audio/post/115446Tue, 06 Jan 2026 18:55:51 GMT<![CDATA[Reply to Latest version of HISE breaks existing presets.... on Tue, 06 Jan 2026 12:11:44 GMT]]>@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.

]]>https://forum.hise.audio/post/115411https://forum.hise.audio/post/115411Tue, 06 Jan 2026 12:11:44 GMT