Saving MIDI CC assignments in user presets?

[dannytaurus]

@ustk Not sure. To be honest, I just want all the 'CC data in presets' code out of my fork.

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

[David Healey]

I think this is what the custom user preset model is for: https://docs.hise.dev/scripting/scripting-api/userpresethandler/index.html#setusecustomuserpresetmodel

Haven't tried it myself.

[ustk]

@David-Healey Lol

@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
});

[ustk]

@David-Healey @David-Healey So the working solution is

const var currentAutomationState = {"ChildId": "Controller", "Children": []};

const var mah = Engine.createMidiAutomationHandler();

mah.setUpdateCallback(function()
{
	currentAutomationState.Children = this.getAutomationDataObject();
});



const var uph = Engine.createUserPresetHandler();

uph.setEnableUserPresetPreprocessing(true, false);

uph.setPreCallback(function(presetData)
{
    presetData.MidiAutomation = currentAutomationState;
});

The automation state is saved in the instance but you can just save it in a file if you wish so.
I'd prefer not in my case, because if you load multiple instances of the plugin, they'll all react to the same CC...

[David Healey]

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

const var currentAutomationState = {"ChildId": "Controller", "Children": []};

Does this store MPE and Macro assignments too?

[ustk]

@David-Healey Apparently macro yes, but MPE
Here's the automation data object:

[
  {
    "Controller": 6,
    "Channel": -1,
    "Processor": "Interface",
    "MacroIndex": -1,
    "Start": 0.0,
    "End": 1.0,
    "FullStart": 0.0,
    "FullEnd": 1.0,
    "Skew": 3.106283926937945,
    "Interval": 0.0,
    "Converter": "37.nT6K8CBGgC..VEFa0U1Pu4lckIGckIG.ADPXiQWZ1UF.ADf...",
    "Attribute": "HiBoostBWKnb",
    "Inverted": false
  }
]

[ustk]

@David-Healey Just tested with my seaboard and yes, it works for MPE that have been MIDI learnt (Since it's just MIDI in the end...)

[dannytaurus]

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

I'd prefer not in my case, because if you load multiple instances of the plugin, they'll all react to the same CC...

That's a very interesting point!

EDIT: actually, maybe it's fine. The DAW will only send MIDI CC to the active plugin, right?

[ustk]

@dannytaurus If by inactive you mean hidden UI, then Midi is still reaching them

[dannytaurus]

@ustk A DAW will only route incoming live controller messages to the active or record-armed track(s), surely?

So if I have 3 different synths all set to respond to mod wheel > filter, then only the active one will respond when I turn the mod wheel, right?

Regardless of whether the synth UI is visible or hidden. It's based on active tracks, right?

The other 2 'unselected', 'inactive', 'not record-armed' synths won't respond to live controller data

Otherwise there would be chaos! Unless that's what you wanted, and armed ALL tracks for record!

[ustk]

@dannytaurus Oh yes absolutely, active in the sense of "armed track", then 100% yes

[dannytaurus]

@ustk Yes, 'active' is too ambiguous a word to have used in the first place. My bad.

[ustk]

@dannytaurus The honour of badness is mine

[David Healey]

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

So the working solution is

I think there's more to it, at least if you're saving/loading it from a file.

setUpdateCallback is triggered before on init and setPreCallback is only triggered when loading a preset.

So we need it to be that when we make a change to automation we save the the object to a file.
Then at init we load that object from the file using setAutomationDataFromObject
And during preload we pass the object into preset data.

[ustk]

@David-Healey Absolutely, then the mah.setUpdateCallback allows you to easily write the file, that's why I said "or just rewrite what you already saved" in the post above

[David Healey]

@ustk Yeah I've got it working now. I've set it to fall back to the preset's automation if the one loaded from the file is empty. That way I can setup my "defaults" in the preset file.

[ustk]

@David-Healey said in Saving MIDI CC assignments in user presets?:

That way I can setup my "defaults" in the preset file.

Clever!

[ustk]

@David-Healey Till today I wasn't aware of this setEnableUserPresetPreprocessing, this will save me from other situations where I was tinkering with the pre/post save/load in order to keep parameters persistent...
I'll keep that in mind now!