Content.storeAllControlsAsPreset

[d.healey]

@Christoph-Hart

Why would you want to load a user preset at the beginning?

I don't :) I have a button that when clicked calls the Engine.loadUserPreset() function and that is generating the message. The button has saveInPreset disabled.

[Christoph Hart]

Ah OK, then I'll take a look why it fires that false positive thingie. Better safe than sorry :)

[Christoph Hart]

Just looked, it checks the initialisation state which should be set to false after the initial state has been loaded. So I understand it right that this is happening when clicking a button with the mouse, yes?

[d.healey]

@Christoph-Hart Correct

[d.healey]

I just realised you'd already suggested my getFiles function a couple of weeks ago :p https://forum.hise.audio/topic/1146/viewport/24

[lalalandsynth]

Sub presets could be useful to save lfo shapes , just stumbled upon the need to do that so i thought I would mention it.

[Dan Korneff]

@d-healey said in Content.storeAllControlsAsPreset:

It's also not possible to add sub-folders in the file path.

Was this ever added? I'm playing with Content.storeAllControlsAsPreset() and I can only create a preset in the main User Presets directory. @d-healey Is there a way to set sub-folders?

[d.healey]

@dustbro Not that I know of

[Dan Korneff]

@Christoph-Hart please?

[Christoph Hart]

What if you could just pass a ScriptFile object into these methods:

Engine.loadUserPreset( String relativePathWithoutFileEnding)
Engine.saveUserPreset(String presetName);

Then you can create subfolders, add new files etc. as much as you want.

const var f = FileSystem.getFile(FileSystem.UserPresets).getChildFile("MyFunkySubFolder/AnotherSubFolder/3LevelSubfolder/Mindblowing4LevelSubfolder/Preset.preset");

Engine.saveUserPreset(f);

The old functionality will remain the same (so passing in a String will do whatever it does now).

[d.healey]

@Christoph-Hart Looks good!

[Dan Korneff]

That's perfect!

[Dan Korneff]

my only gripe with saveUserPreset() is that you have to load a preset first.
I had a method where I loaded an empty preset before saveUserPreset(), which was working great on everthing EXCEPT protools :( It didn't like the empty preset.

Is there some method I'm overlooking to load a preset without changing your current control settings? It just seems backwards to me

Content.storeAllControlsAsPreset() was great cause you could skip the whole "load a preset first" thing.

[d.healey]

@dustbro all a preset does is store and restore control settings, so what would be the point of a preset that didn't change the controls when loaded?

[Dan Korneff]

@d-healey that's kind of my point. You can't use saveUserPreset() without first calling loadUserPreset() or else the newly saved preset will be created in an unexpected location.
From my testing, you have to load an existing preset within the sub folder location you want to save to. Then saveUserPreset() makes a duplicate (child? ) of that file and saves the new data to it.
So if you want to save your current settings as a preset, having to loading a preset first (which would change your controls) seems counterintuitive.
Maybe @Christoph-Hart could clarify

[d.healey]

@dustbro ah I see the problem now, I think the changes proposed by Christoph will solve this already.

[Dan Korneff]

@Christoph-Hart said in Content.storeAllControlsAsPreset:

Then you can create subfolders, add new files etc. as much as you want.

@Christoph-Hart Any chance we can get this update on your radar?

[Christoph Hart]

Alright, Engine.loadUserPreset() accepts a file object now, so the minimal setup for loading and storing user presets via the native file browser is:

function load(file)
{
    Engine.loadUserPreset(file);
}

function save(file)
{
    Engine.saveUserPreset(file);
}

// Place this anyway you like (button callbacks, whatever)...
var shouldLoad = true;

if(shouldLoad)
    FileSystem.browse(FileSystem.UserPresets, false, "*.preset", load);
else
    FileSystem.browse(FileSystem.UserPresets, true, "*.preset", save);

[Dan Korneff]

@Christoph-Hart

[Dan Korneff]

@Christoph-Hart said in Content.storeAllControlsAsPreset:

FileSystem.browse(FileSystem.UserPresets, true, "*.preset", save);

@Christoph-Hart Is there a way to default the browser to open the User Presets folder when using this save function? I have FileSystem.UserPresets set, but the system browser opens the last location you've navigated to.