Preset manager preset name input

[sm_jamieson]

Can we please have a new preset manager text input parameter for the name to be used when the preset is saved. If nothing is connected to the input the module should behave as currently. If a string is on the input when the preset is saved it should be used for the name.
This would allow the preset manager to automatically pick up the current program name from the plugin when the preset is saved.
Which would be *very* useful to me ...

Alternatively, the comma text input is passed to be output but is ignored by the preset manager.
This could be changed so that either the comma text input directly modifies the program names,
of the comma text is used to provide a default name when a preset is stored.

There is currently no way to set the preset names by patching, they have to be typed in.

Thanks.

[woodslanding]

+1, I have been asking for this for years.... My workaround is to keep all preset names in a listbox, and all the actual presets are named 'no name'.

But since they have names, it would be nice to actually use them.

[SylvainT]

+1 to set the preset names by patching

You can easily recover presets names with the "comma text" output of the "patch settings" module, drive the "comma text" input of a listbox.

Presets & Listbox.pat

(18.93 KiB) Downloaded 485 times

Sylvain

[sm_jamieson]

Yes, I have no problem extracting preset names as comma text, and I have used a listbox to store names before.
But Usine is all about patching, and the few remaining things that cannot be patched are REALLY annoying

(As an aside, modules that only have a "toggle" and no absolute state inputs are no good for patching either, as you might
not know the current state so you can decide if you need to toggle or not).

[senso]

for now, I can't find any good solution for an easy patching of preset names inlet.
work in progress...

[sm_jamieson]

Please can you think about this again. Everything should be scriptable in Usine - that is What It Does !

[senso]

The preset manager will be rewritten in the next major release, with many new features.

[sm_jamieson]

It would be cool to have a method in the SDK to get the binary chunk data from various plugins and save it in a new Preset chunk.
Then it would be possible to write our own user module preset manager.
But you would need a way of referencing a particular instance of a plugin.
Unless plugin manager had a new parameter that could be used to dump the current plugin state on a wire.

[woodslanding]

--The preset manager will be rewritten in the next major release, with many new features.--

Backward compatibility, or bulk conversion option, I hope!! I have over 750 HH preset files now, and more every day!

[Ariajazz]

Resizable Preset Manager?

[sm_jamieson]

Now Usine Object exists, how about using Usine Objects to change the preset names ?

[sm_jamieson]

Now Usine Object exists, how about using Usine Objects to change the preset names ?

Well sorry I spoke to soon. I thought I'd check and this is already possible,
e.g. SetObject('patch.obj-presetmod.0',"CrazyBellPatch");
And what a genius way of enabling preset names to be set.

Also, Usine Objects that don't have pins - is an interesting concept.
Of course if we want them to have pins - use a script.
I really like the way Usine is evolving.

Simon.

[senso]

thanks for your comment.
Don't forget that UsineObjects access are generally slow.

[SylvainT]

@Simon,

Did you study the new possibilities provides by new modules : Global Arrays ?
These new features developped especially for a big project closed to Usine is very awsome and you'll certainely find new ways for creating complex preset capabilities for all your workspace.

Sylvain