Thomas Tinkhauser

just-saving-everything

why does everything in the world have to be so complicated ;)

I dont have the time to get fully into this...I managed to save some settings with audopattr working on autoname - but it doesnt save buttons I push, and nothing I change in bpatcher windows...

> why does everything in the world have to be so complicated ;)

It doesn't; just a matter of adjusting expectations.

> I dont have the time to get fully into this...I managed to save some

> settings with audopattr working on autoname - but it doesnt save

> buttons I push, and nothing I change in bpatcher windows...

well, put an autopattr into the bpatchers and don't forget to name the 

But late at night its better to go to bed, next morning the world will 

the pattr system isn't the easiest, but just saving the last state is 

not at all complicated (you just have to know how to do it... ;-)

Thomas Tinkhauser wrote:
> why does everything in the world have to be so complicated ;)
>
> I dont have the time to get fully into this...I managed to save some
> settings with audopattr working on autoname - but it doesnt save
> buttons I push, and nothing I change in bpatcher windows...

well, put an autopattr into the bpatchers and don't forget to name the 
objects you want to store.
But late at night its better to go to bed, next morning the world will 
be less complicated... ;-)

the pattr system isn't the easiest, but just saving the last state is 
not at all complicated (you just have to know how to do it... ;-)

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


>>why does everything in the world have to be so complicated ;)

> It doesn't; just a matter of adjusting expectations.

But in his case even pattr is simpler. My advise if you want serious 

preset handling/state saving avoid the preset object. If you just want 

it quick and dirty, the preset object is wonderfull...

Dayton wrote:
>>why does everything in the world have to be so complicated ;)
>
> It doesn't; just a matter of adjusting expectations.
>
> Try this:

But in his case even pattr is simpler. My advise if you want serious 
preset handling/state saving avoid the preset object. If you just want 
it quick and dirty, the preset object is wonderfull...

Quote: Stefan Tiedje wrote on Thu, 14 December 2006 02:53

----------------------------------------------------

> But in his case even pattr is simpler. My advise if you want serious 

> preset handling/state saving avoid the preset object. If you just want 

> it quick and dirty, the preset object is wonderfull...

Without a doubt. However, "quick and dirty" is usually where people begin. Particularly for prototyping it is useful to use [preset] but, as S.T. states, it is well worth the effort to move up to using [pattr] and [pattrstorage].

Quote: Stefan Tiedje wrote on Thu, 14 December 2006 02:53
----------------------------------------------------
> But in his case even pattr is simpler. My advise if you want serious 
> preset handling/state saving avoid the preset object. If you just want 
> it quick and dirty, the preset object is wonderfull...

Without a doubt.  However, "quick and dirty" is usually where people begin.  Particularly for prototyping it is useful to use [preset] but, as S.T. states, it is well worth the effort to move up to using [pattr] and [pattrstorage].


Not to mention that using interpolation with the preset object would require a whole separate series of number boxes and line objects to interpolate before the numbers get sent to their final destination. Which *does* allow for some interesting effects (esp. with the grain length in line), but they're more to manage than with a well-designed pattr.

Presets are great for quick n' dirty, or for keeping track of gates or other "radio-type" selections where the numbers are all 0 or 1, and interpolation doesn't make any sense.

The little preset object is also a good way to have a selectable array of numbers that is small (maybe to choose a pattr preset or something). It's not used for anything except to send a number from the middle outlet in this case. Just be sure to hook a dummy number box to the left outlet or preset will try to remember everything on the screen!

If you want a little bigger selector, use matrix~ with "one cell per matrix" selected. However, you need to deal with the problem of clicking the same cell and having it disappear.... use a "sel 0 --> set 1" kind of thing. Works well and gives a somewhat larger and clearer representation of the current number selected.

Presets are great for quick n' dirty, or for keeping track of gates or other "radio-type" selections where the numbers are all 0 or 1, and interpolation doesn't make any sense. 

Just Saving Everything!