Another little weirdness I noticed with the filter. Once a voice ends the filter value jumps to its previous value, this causes artifacts (clicks/pops) with other voices that are still playing.

Peek 2026-04-16 18-06.gif

Another issue I just noticed, CC mods don't work

Peek 2026-04-16 17-58.gif

@duma You open it in Projucer, like when you build HISE

@ustk That's the input value which is between 0 and 127 for a MIDI mod.

@David-Healey Sorry, I didn't describe it clear enough

@ccbl the simmons sds-v has just a sine and a noise oscillator cleverly enveloped and filtered through a SSM2044. no physical modeling at all.

@Christoph-Hart said in Instant crash when loading any faust dsp to the module:

@Lindon damn, alright then. macOS or windows?
macOS arm 64 bit

Personally I use panels in most cases as well.

In your case, I know all of my components begin with a prefix indicating their type.
Examples:

knb: knobs btn: buttons lbl: labels

I do this to be able to assign LAFs. control callbacks, etc. as I want.
Assuming you did something similar, it would be simple enough at the outset of your project to format all the labels as you want:

const var labels = Content.getAllComponents("lbl"); for (l in labels) l.set("editable", false);

Editing the HISE source code is a quicker, more permanent recommendation.

@duma Yes should do

@CBIbanez Have you built HISE from source? If not, that's the first step before you can compile your project.

@David-Healey Thanks! I ended up figuring it out from an old post you advised on as well. lol. Attached the callback to a slider with 'save in preset' loaded that triggers the callback on preset load.

@David-Healey @DanH In fact it's not something that problematic because it can be LAFed easily.
It's just the annoying message "Not Assigned" that I can't get rid of, so I just make it transparent, but I feel like it's a hack and it should be cleaner...

@RedFireTF2 You need to compile from source, but the VST3 SDK will only come into play when you compile your project as a plugin (or if you're compiling HISE as a plugin).

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

Yes, this functionality is broken when you try to run Tools>Convert all samplemaps to monolith + samplemap

@Sifres I just went and looked... That looks SO great.

@pcs800 And strangely enough, today I can compile to the network drive again without issue.
The server must have been low on bluetooth fluid

@pratitghosh if you run the HISE project in Xcode or visual studio and build in debug it’s a lot faster. Then you can use the audio plugin host template from JUCE to launch and test it quicker.