@ustk said in Saving MIDI CC assignments in user presets?:

@dannytaurus @David-Healey Can't the CC mapping simply be removed from the preset using the handler? Isn't the custom preset intended for this purpose in the first place? Never tried myself that being said...

Just checked and the answer is no, you can't manage what is written... But Claude came with a neat solution:

// (processBeforeLoading, unpackComplexData)
uph.setEnableUserPresetPreprocessing(true, false);

uph.setPreCallback(function(presetData)
{
    // presetData is a JS object; MidiAutomation is a top-level property.
    // Emptying it means applyJSON rebuilds an empty <MidiAutomation> node,
    // so the incoming preset never overwrites the current CC assignments.
    presetData.MidiAutomation = {}; // or just rewrite what you already saved
});

Haven't tried it myself.

Might just drop the preprocessor and remove it all directly.

I can't see a situation where I would ever want CC data in the presets. So a preprocessor is only useful for backwards compatibility, which I don't have any of

There are 3 HISE restore points that run after onInit, so it still needs handling.

From Claude:

Fresh instance in a DAW: FrontendProcessor::restorePlugin runs compileAllScripts() (your onInit applies the file) and then restores the
MidiAutomation node from the embedded project state (FrontEndProcessor.cpp:458). The export always writes that node — even when empty, exportAsValueTree adds it unconditionally — so a fresh instance immediately clears the mappings you just loaded. Your file-load is defeated before the user ever touches the plugin.

Reopening a session: the host calls setStateInformation at some point after instantiation (host-dependent timing), and FrontEndProcessor.cpp:576 restores the session's stale mapping copy over whatever onInit applied.

In the editor: every project load stashes the project XML's <MidiAutomation/> and applies it after script compilation (MainController.cpp:562/577)
— same wipe while you're developing.

Launch the plugin - load the CC mappings from separate file

Handled here, no?

Looking at it now.

Save the preset - the CC mappings save with the preset, so maybe do a post save callback to remove the data

You don't need to do anything here because you're already loading the CCs from the file.

That's true, but if you leave the CC mappings in the preset file then it becomes lies on disk.

Likely to be confusing to someone looking at the preset XML.

Agree on the AppConfig.h, Claude forced it into the commit, I'll remove it.

Save the preset - the CC mappings save with the preset, so maybe do a post save callback to remove the data

You don't need to do anything here because you're already loading the CCs from the file.

So your preprocessor removes step 2 the rest is the same.

I think AppConfig.h is autogenerated when you save the juicer file so probably shouldn't be tracked by git - I could be wrong.

Without the preprocessor:

1. Launch the plugin - load the CC mappings from separate file
2. Load a preset - in post load callback you need to reassign CC mappings because they're overwritten by the load
3. Assign some CC mappings - automatically save the new mappings to separate file here
4. Save the preset - the CC mappings save with the preset, so maybe do a post save callback to remove the data
5. Load the next preset, etc.

With the preprocessor:

1. Launch the plugin - load the CC mappings from separate file
2. Load a preset - nothing to do
3. Assign some CC mappings - automatically save the new mappings to separate file here
4. Save the preset - nothing to do
5. Load the next preset, etc.

Claude came up with a (hacky) way to script around it but in the end I felt like a PR with a new preprocessor was better.

https://github.com/christophhart/HISE/pull/995

(I know there are already too many preprocessors, but this is mainly just for me, only upstreaming in case anyone else wants it.)

So now I just turn this off (HISE_MIDI_AUTOMATION_IN_USER_PRESETS=0) and then I don't have to fight anything in script.

I'm pretty sure if can be achieved using the MidiAutomationHandler and storing the automation settings to a file which you load back in on init.

https://docs.hise.audio/scripting/scripting-api/midiautomationhandler/index.html