[PD] best way for saving a patch state ? (where to find the[State] object ?)

[Tebjan Halm]

ok, i'll give it a try. but is seems that it needs more performance than 
the simple [State] object, because it is a bigger system of 
abstractions. i'am a very performance freak ...

tebjan

patrick schrieb:

>i recommand highly memento from cvs /rradical. there's even a midi binding
>to OSC. very neat stuff.
>
>pat
>
>
>
>
>
>----- Original Message -----
>From: "Tebjan Halm" <tebjan at gmx.de>
>Cc: <pd-list at iem.at>
>Sent: Tuesday, September 20, 2005 9:55 AM
>Subject: Re: [PD] best way for saving a patch state ? (where to find
>the[State] object ?)
>
>
>  
>
>>thanks for the answer, i see the problems and possibilities now, and i
>>remember, after reading footils.org, that i used the [State] object. in
>>which external is it included ?
>>
>>i have iemlib, zexy, xsample and PeRColate installed so far, but [State]
>>is not into one of them. (windows) ... any additional recommendations**
>><http://dict.leo.org/se?lp=ende&p=/Mn4k.&search=recommendation>?
>>
>> greets
>>
>>Roman Haefeli schrieb:
>>
>>    
>>
>>>hi tebjan
>>>
>>>i'm not sure if there is an easy solution. it also depends on what you'd
>>>      
>>>
>like to do/have. if you only want to store one state, you could use a small
>hack with set-messages: when changing values, you [set $s( a message-box to
>the new value. when you save the patch all values are saved in the
>message-boxes. when loading the patch you trigger all those messagebox with
>a loadbang to set all guis to the state before. but this is a lot of work
>and a little bit messy, since you need for each gui, that you want to save
>the state, at least three additional objects ( [set $1(,[  (, [loadbang]).
>this method does not allow to save different states of the same patch and
>you cannot do it with abstraction (-> biiig patches...)
>  
>
>>>another method would be, to write a state-abstraction, so that each gui
>>>      
>>>
>gets connected bidirectional to one of them. then you need something like a
>chief abstraction - only one per patch. if you want to save a state, the
>chief abstraction tells all state-abstraction in the patch to send their
>values. the chief-abstraction receives all this data and writes it into a
>textfile with an unique name. to recall a saved preset, the chief
>abstraction reads the textfile and sends the data to all state abstractions,
>while they set the guis to the old state. this means that every state
>abstraction needs a unique ID (name or number). this might sound like lot of
>work, but like this you can save as many preset as you want to. (and you can
>reuse the state- and the chief-abstraction in each patch).
>  
>
>>>i use the second method in netpd. i think, the method frank barknecht is
>>>      
>>>
>using with memento is quite similar (i'm not quite sure). the latter is
>quite well documented. so have a look:
>  
>
>>>http://footils.org/cms/show/1
>>>
>>>cheers
>>>roman
>>>
>>>
>>>
>>>On Tue, 20 Sep 2005 01:22:01 +0200
>>>Tebjan Halm <tebjan at gmx.de> wrote:
>>>
>>>
>>>
>>>      
>>>
>>>>hi,
>>>>
>>>>i am sure this i a FAQ. can someone give me a short hint whats the
>>>>easiest way to store one or more patch states ?
>>>>some years ago i was an excessive pd user, but i can't remember all the
>>>>tricks.
>>>>
>>>>thanks for help ...
>>>>
>>>>tebjan
>>>>
>>>>
>>>>        
>>>>
>>>
>>>
>>>
>>>
>>>___________________________________________________________
>>>Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier
>>>      
>>>
>anmelden: http://mail.yahoo.de
>  
>
>>>
>>>
>>>      
>>>
>>_______________________________________________
>>PD-list at iem.at mailing list
>>UNSUBSCRIBE and account-management ->
>>    
>>
>http://lists.puredata.info/listinfo/pd-list
>  
>
>
>
>  
>