Yeah, cool, sure, I'm aware, but thanks for pointing that out anyway though, it's good that we take that into consideration as well in this thread for comparing and checking out preset management systems for Pd. And why not even bring to the table preset features from other systems, like MAX? I'm actually looking into that as well...

I guess I should have mentioned that, but I just wanted to ask for other existing solutions available for vanilla, either as pure vanilla abstractions or anything that uses externals available in our ecosystem.

And while we're at it, it seems to me one could just get the code of preset_hub / preset_node and port the exact same thing and distribute as an external for vanilla, right? I'm assuming it doesn't require any special Purr Data modification. If so, I guess one thing to consider is that thing we recently discussed in the pd-dev list, that for in order of two objects sharing data and info, like I'm assuming preset_hub and preset_node do, you'd need a single binary library, or have something a single [preset] object and use Miller's trick that the argument will call the separate object (as in [preset hub] and [preset node]) - I like this idea better.

I just had a quick look at Purr's system though. It seems a bit more complex than I'd like, taking int consideration the same matter I pointed in the email I sent just before yours came in. But I'm gonna spend some more time on that too (as well as with other systems mentioned here, and maybe new ones yet to be mentioned) and see if I'm missing something cool I haven't thought of yet.

cheers

Em qui., 21 de jan. de 2021 às 14:17, Jonathan Wilkes <jancsika@yahoo.com> escreveu:

Just an FYI-- Purr Data has preset_hub and preset_node from Ivica's Pd-l2ork. I don't think it handles state transitions, but the UX is nice and works seamlessly across abstractions without requiring "$0" for symbolic names.

Best,
Jonathan

On Thursday, January 21, 2021, 2:54:33 AM EST, Alexandre Torres Porres <porres@gmail.com> wrote:

Never really needed fancy preset management other than storing messages in a basic vanilla way. But I've seen people mention how Pd lacks a nice preset system. Not that I know what a fancy one actually needs since I never felt the demand. So I'm here to ask what people use in Pd Vanilla, be it a pure vanilla solution or an external. And also to ask what people miss.

This is what I came up with as a pure vanilla abstraction, it's based on [text] and [savestate]. Here's the thing: https://drive.google.com/file/d/1A0ISEJo5F1E578WHM1doo1n2CJAthonU/view?usp=sharing

In short, the preset abstraction takes messages and stores them. You can have many of these on your patch and use them to recall presets for any parameters. It takes any kind of messages. I'm making use of built-in sends and receives in the number boxes to make the patch cleaner. Just think that you can have separate control of each parameter having its own preset or group all of them together globally, or a group here and another there, whatever... Once you save the patch, the presets you saved get stored in the patch.

As for my current idea for my ELSE library, I'm using an object similar to grab to take messages from [receive] objects. It's a development over this original vanilla abstraction. My first draft is this, I hope that sharing the screenshot give you a nice idea.

You can check what's up in my repository for more details... https://github.com/porres/pd-else/blob/master/Classes/Abstractions/preset.pd

cheers

_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list