Custom browser - custom preset file format???

Christoph Hart

That's the right direction, but I would also try to stay within the HISE user preset system so you get the intended loading prodecure (kill voices, load the preset on a background thread, then unsuspend the audio processing).

With the custom data model you can define the layout of the user preset file as you wish. Note that it will be converted from JSON to XML at some point though (which is a bit weird).

They also want to be able to export a preset, and include any sample content with the preset - ie; bundle the custom loaded .wav file, or the samplemap, with the preset. For personal sharing purposes.

I would detach this from the user preset system. A preset with sample mapping data and samples should be

The preset file
The JSON (or SFZ or whatever) mapping file
The audio samples

all in one folder.

Orvillain

@Christoph-Hart I'm looking at this again. Before I begin, is there a decent snippet anywhere that demonstrates how to do this for a simple plugin?

Also, what are the gotcha's to watch out for? You mentioned killing voices, loading on the background thread, etc...

Christoph Hart

@Orvillain nope, I'm using it in Triaz, but I haven't made a public example yet, but it's a good idea to do so. The problem is that it cannot be encompassed into a nice simple snippet as it requires additional data (preset files) to be useful.

Just from thinking about it there are a few things to watch out for:

initialisation order. Usually you can decide what you restore first by rearringing your script function, but be aware that restoring module states for whole HISE modules will always come after this method.
the function is being executed synchronously in the loading thread (but it should take a lock to prevent simultaneous execution of scripting tasks in the scripting thread). You can safely assume that there are no voices playing during this function call (because it kills all voices when loading a preset).
The XML -> JSON conversion is a bit weird because the data structures are not 100% convertible, so there are a few edge cases to consider here. You'll notice when you run into them :)

Orvillain

@Christoph-Hart

Hey Christoph - I've not really got my head around this yet, and my client is requesting multiple types of preset. They want effect chain presets as well as full state presets. They also want to be able to add meta-data and copy samples along with the preset.

Does that mean I'm going to need custom data models for each type ??

I could really do with a simple tutorial that shows some of this stuff

Orvillain

Here's what I've figured out so far:

namespace PluginUserPresetHandling {

    const UserPresetHandler = Engine.createUserPresetHandler();

    
    inline function onPresetLoad(obj) {
        Console.print("we just loaded a preset!");
        if (obj.presetData.ui)
            UserPresetHandler.updateSaveInPresetComponents(obj.presetData.ui);
    }
    
    inline function onPresetSave() {
        Console.print("we just saved a preset!");
        return {
            "version": "1.0.0",
            "presetName": "This is a magic string for the preset name",
            "presetAuthor": "Drew",
            "presetDescription": "This is a saucy preset",
            "presetTags": ["Fat, Warm, Round"],
            "presetData": {
                "ui": UserPresetHandler.createObjectForSaveInPresetComponents()
            }
        };
    }

    inline function init() {
        UserPresetHandler.setUseCustomUserPresetModel(onPresetLoad, onPresetSave, false);
    }
}

And this will actually produce a file that looks like this:

So that's quite cool.... but something about my preset did sound different, versus how it sounded when I saved it. So I guess there's more data across the modules that I need to grab too.

Lindon

@Orvillain said in Custom browser - custom preset file format???:

@Christoph-Hart

Hey Christoph - I've not really got my head around this yet, and my client is requesting multiple types of preset. They want effect chain presets as well as full state presets. They also want to be able to add meta-data and copy samples along with the preset.

FX Chain presets should be pretty simple to encode in a json data model - what meta-data and samples?

Does that mean I'm going to need custom data models for each type ??

yes

DanH

@Orvillain there’s a mini preset system posted on here a while back by the lunacy guys / Casey Kolb. I’m about to take off otherwise would post.

Orvillain

Okay... starting to get a feel for this system now....

One thing I ran into today was trying to decide whether my menus should have their saveInPreset bool enabled or not. My menus have a callback associated with them that controls the loading of an effect and the binding of parameter knobs.

But because I am eventually going to be aiming at an effect chain preset format.... I figured saveInPreset should be disabled, and I should track the effect data manually.

I got there in there, but it did require a bit of thought. Because loading the effect networks seems to be asynchronous, so you cannot rely on the parameter knobs to be properly flushed at the right time when calling updateSaveInPresetComponents().

So after a lot of trial and error, I just decided to call it twice!!

    inline function onPresetLoad(obj) {
        local data = obj.presetData;
        if (!isDefined(data)) return;

        if (isDefined(data.ui)) {
            UserPresetHandler.updateSaveInPresetComponents(data.ui);
        }

        local engIds = ["Engine1", "Engine2", "Engine3"];
        for (i = 0; i < engIds.length; i++) {
            local engineIdx = i + 1;
            local smKey = "engine" + engineIdx + "SampleMap";
            local wtKey = "engine" + engineIdx + "Wavetable";

            if (isDefined(data[smKey]))
                UISoundSelector.syncSamplerMenu(engineIdx, data[smKey]);

            if (isDefined(data[wtKey]))
                UISoundSelector.syncSynthMenu(engineIdx, data[wtKey]);
        }

        if (isDefined(data.fxSelections)) {
            for (k in data.fxSelections) {
                local fxName = data.fxSelections[k];
                UIEffectDropDownMenu.syncEffectMenu(k, fxName);
            }
        }

        if (isDefined(data.ui)) {
            UserPresetHandler.updateSaveInPresetComponents(data.ui);
        }
    }
    
    inline function onPresetSave() {
        return {
            "version": "1.0.0",
            "presetAuthor": "",
            "presetDescription": "User Preset",
            "presetTags": [],
            "presetData": {
                "ui": UserPresetHandler.createObjectForSaveInPresetComponents(),
                "engine1SampleMap": PluginSharedData.engineSounds["Engine1"].sampler,
                "engine2SampleMap": PluginSharedData.engineSounds["Engine2"].sampler,
                "engine3SampleMap": PluginSharedData.engineSounds["Engine3"].sampler,
                "engine1Wavetable": PluginSharedData.engineSounds["Engine1"].synth,
                "engine2Wavetable": PluginSharedData.engineSounds["Engine2"].synth,
                "engine3Wavetable": PluginSharedData.engineSounds["Engine3"].synth,
                "fxSelections": captureFXSelections()
            }
        };
    }

This works well, if a little wasteful perhaps.

Part of the reason I wanted to do this is because the menu values are obviously floats, not the text value of the menu. And I knew that in the future if I wanted to add an effect type, and change the order of effects in the menu list, that this would break backwards compatibility. So I basically have a shim that will take a string and convert it to the right integer for the menu as it is in that moment, and then set the menu to the appropriate value .... which then triggers the callback to load the right effect network...

and then that last updateSaveInPresetComponents() call makes sure the parameters match what the preset has stored.

Lindon

@Orvillain this all seems massively complicated for preset saving and loading, what does the existing prest management and a custom tag based browser on the front of it not give you?

Orvillain

@Lindon said in Custom browser - custom preset file format???:

@Orvillain this all seems massively complicated for preset saving and loading, what does the existing prest management and a custom tag based browser on the front of it not give you?

Ultimately it isn't just about preset saving and loading.

They want full customization of the preset data model. They want each preset to have an associated image. They want to be able to import and export presets along with sample content at the same time. Which means I need full path control over the samples when saving. They want rich meta-data based browsing and on the fly searching. When saving a preset, they want to be able to specify various tags and descriptors, and it makes sense to store that stuff directly into the xml. There's probably more they want, but off the top of my head that's all I remember.

Everything they're asking for seems to involve deeper control over the load and save mechanics. But it's actually not that complicated. I'm essentially overriding the HISE automatic system, with a manual system. I'm capturing nearly everything that HISE captures automatically in a single call to UserPresetHandler.createObjectForSaveInPresetComponents() - everything else is custom.

Unless I'm missing something, there's a lot that the stock preset management system doesn't give you.

After spending a fair amount of time trying things out and reading the API, I'm fairly sure I have a decent grasp of how it all works now. There are also pre and post callbacks for loading and there's a post callback for saving too, which I'm going to need to tell the system to refresh the list of presets; or to update the external database, which is probably going to be required too.

Custom browser - custom preset file format???

22

2.2k

13.3k

116.1k