still quite new to pd~(please redirect if this post isn't in the right place), I have been trying for some time to resolve the problem of saving presets and states for the patches I have built.
Allthough I have come to some conclusions (writing qlists through parallel sets of send/returns, saving arrays, ...), I still seem to be stuck, and so hereby cry out for help ...

On the internet I come across things like RRAD or sssad or OSC, but am not really sure what they are, and i usually try to (at least during the learning process) use built in objects and my own patching rather than blindly using better patchers systems and libraries....

Can anyone help me? is there an object or trick (something tells me there might be a solution in arrays) or patching system to be able to save many values (in GUIs but also number boxes) for chosen parameters, without loosing abtraction and dollarsigns structure? If using externals like ssad is really necesary, which should i chose? ......

this is my first post in this forum, hope it's not misplaced.... if i can help anyone, i'm more keen on granular synthesis and audiodigitals than pd~, but hey...
thanks,

gabriel

Try this first - its a couple of methods to saving in the patch. One uses arrays and one uses messaging - check the attachment

Dont forget that using the 'iem' gui elements allows you to set a property called INIT. Right click on them. This will save the current value of each gui element when the patch is saved. Good for quick one shot state saving

But eventually I'd opt for the flexible and neat SSSAD system. Check this: http://puredata.hurleur.com/sujet-3586-patch-saves-presets

hope this helps

http://www.pdpatchrepo.info/hurleur/SiStateSave_v1.pd

using your tips on state saving with tables i (more or less) succesfully implemented a preset saving system for my first complete patch (in attachment).

sssad and other mementos still seem quite out of reach for me now, and it looks like i'll need a lot more learning on lists and data-saving (not very clear in the pd examples ... know of any tutorial etc?) before i can use and understand it.

if you get a chance to look at my patch and tell me what you think (full of errors and not operational. i can't get 2 units running at the same time for example) it'd be great .... thanks for the infos, very usefull,

gab

here's the first part

http://www.pdpatchrepo.info/hurleur/mud.pd

http://www.pdpatchrepo.info/hurleur/mudchanel.pd

Without really investigating fully, it seems to use a lot of cpu without audio running. I think its the fact that the delays (in the loops ) are set to 0ms after the [loadbang] . This will seriously create problems. The patch needs to initialize grainsize with some real values, one of your presets maybe.

I dont think you included [supergaussian] - thats for windowing right? And also [hook] abstraction is missing.

is all the gui stuff actually working?

the GUIs do work, it's about setting diferent min and max values for each chanel, precisely, and then fooling around live. here's the working version (in three pieces: mud, muchanel, supergaussian. i got rid of the 'hook').

thanks

http://www.pdpatchrepo.info/hurleur/mud.pd

http://www.pdpatchrepo.info/hurleur/mudchanel.pd

http://www.pdpatchrepo.info/hurleur/supergaussian.pd

thats a nice patch, well done. I get some cool sounds out of it

as i am very to new to this, i followed a kind of intuitive logic, and i would love to find new ways of producing the kind of drones i have in mind, new aproaches. do you know about any? patchs simple enough for me to understand? i am happy with this patch regarding the quality of the sounds i squeeze out of it, but it's very dull when it comes to live controling, not expressive at all ...

thanks for all,

gab