Stefan Tiedje

At the moment I use pattrstorage to store the last state of a patch. It 

will initialise to the last values if I reload. Fine, but I'd like to 

use this simple technique for small subpatchers as well, but without 

Here the request: a simplified pattrstorage, with only one "preset" 

called pattrinit. Its sole purpose is to initialise objects exposed by 

an autopattr. These values should be stored (embedded) in the patcher 

itself. I'd like to avoid an external XML file for that. It should be 

possible to hide/expose a part or all of the objects to a parent 

This would just help to get rid of all the loadmess mess I usually put 

up for initialisation. On top of it it should be possible to recall the 

last saved values with an init message...

Let me know if anybody thinks this is a good idea...

This is just an idea:
At the moment I use pattrstorage to store the last state of a patch. It 
will initialise to the last values if I reload. Fine, but I'd like to 
use this simple technique for small subpatchers as well, but without 
creating an extra XML file.
Here the request: a simplified pattrstorage, with only one "preset" 
called pattrinit. Its sole purpose is to initialise objects exposed by 
an autopattr. These values should be stored (embedded) in the patcher 
itself. I'd like to avoid an external XML file for that. It should be 
possible to hide/expose a part or all of the objects to a parent 
pattrstorage (for a global storage)...

This would just help to get rid of all the loadmess mess I usually put 
up for initialisation. On top of it it should be possible to recall the 
last saved values with an init message...

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


pattrinit

Oh, no, just found out autopattr does all, I just thought it was 

Stefan Tiedje wrote:
> This is just an idea:

Oh, no, just found out autopattr does all, I just thought it was 
pattrstorage...

The only difference between "pattrinit" and autopattr/pattr is this 

"init" message, no? When you save a patch, autopattr/pattr remembers 

and restores those values the next time the patch is loaded. Or am I 

Am 02.11.2006 um 19:53 schrieb Stefan Tiedje:

> Here the request: a simplified pattrstorage, with only one "preset" 

> called pattrinit. Its sole purpose is to initialise objects exposed 

> by an autopattr. These values should be stored (embedded) in the 

> patcher itself. I'd like to avoid an external XML file for that. It 

> should be possible to hide/expose a part or all of the objects to a 

> parent pattrstorage (for a global storage)...

> This would just help to get rid of all the loadmess mess I usually 

> put up for initialisation. On top of it it should be possible to 

> recall the last saved values with an init message...

The only difference between "pattrinit" and autopattr/pattr is this  
"init" message, no? When you save a patch, autopattr/pattr remembers  
and restores those values the next time the patch is loaded. Or am I  
misunderstanding?

> Here the request: a simplified pattrstorage, with only one "preset"  
> called pattrinit. Its sole purpose is to initialise objects exposed  
> by an autopattr. These values should be stored (embedded) in the  
> patcher itself. I'd like to avoid an external XML file for that. It  
> should be possible to hide/expose a part or all of the objects to a  
> parent pattrstorage (for a global storage)...
>
> This would just help to get rid of all the loadmess mess I usually  
> put up for initialisation. On top of it it should be possible to  
> recall the last saved values with an init message...


> The only difference between "pattrinit" and autopattr/pattr is this 

> "init" message, no? When you save a patch, autopattr/pattr remembers 

> and restores those values the next time the patch is loaded. Or am I 

You are right. An init message to autopattr which would revert to the 

original values would do it... (and is the better solution anyway)

Its not urgent, I was in a brain smash or something...

Jeremy Bernstein wrote:
> The only difference between "pattrinit" and autopattr/pattr is this  
> "init" message, no? When you save a patch, autopattr/pattr remembers  
> and restores those values the next time the patch is loaded. Or am I  
> misunderstanding?

You are right. An init message to autopattr which would revert to the 
original values would do it... (and is the better solution anyway)
Its not urgent, I was in a brain smash or something...