Default User Preset not working in compiled plugin

[alhug]

It's working within HISE, but when I compile the plugin, the defined DefaultUserPreset is not being loaded. I tried standalone and also AU/VST.

I don't use any subfolders for my presets. They're all just sitting in the UserPresets folder. Therefore I just put the name of the preset (Default Preset) in the settings. It's working within HISE so I assume this is correct, but I'm not sure why it's not working outside of HISE.

[bendurso]

@alhug Mm I never used that feature. But saving the XML with the desired preset and then exporting the plugin always worked for me.
Maybe someone else knows about that feature.

[Christoph Hart]

The default user preset is loaded when you export or save the project in HISE so that it should always initialize to that state. If you're depending on it to actual load the preset then it won't work (but I don't see a scenario where this distinction is important).

[alhug]

@Christoph-Hart Got it.

I have a label displaying the current preset name and also buttons to load next and previous presets on my UI. I wanted to have the "Default Preset" loaded on startup and the name displayed in the label. Right now I just write a string to the label since there's no preset actually loaded. When I click on my LoadNextPreset button it loads the first preset, which is the "Default Preset", so nothing actually happens from a user's perspective.

I want the "Default Preset" to be included in the preset library so that the user can always go back to the init state when using the plugin.

I was thinking of just loading that default preset on init but what happens if the user manually deletes this preset from the folder?

[Lindon]

@alhug I found its best to not get hung up about what preset is displayed when the user loads the plugin at any given point.

So have a preset (saved in your presets folder) called init - before you compile load this preset. So first time(ever) the user start the preset this gets loaded. If they change the preset to MyFunkyPreset then save the plugin it will reload with this MyFunkyPreset ....

[jeffd]

@alhug

I have this same problem. So if I understand correctly, an instrument made with HISE...
the compiled plugin will never actually load with a preset?

I can get the standalone HISE app to load with one, but not my compiled plugin.

even after scripting : Engine.loadUserPreset("FactoryLibrary/Patches/Default.preset");

[jeffd]

@jeffd
ok i figured out why it wasnt saving the default, i didnt have the preset window coded to save in the preset.

[jeffd]

@jeffd
actually, nope. thats not right either.

ive done something odd. Everything works correctly in the hise editor,
but saving in a compliled plugin, i get odd behavior.
I am selecting a bank and category, yet i am getting the response i coded to tell me to select one.