Tarik

I would be very happy if I could store the preset-data of several pattrstorage-objects within subpatchers in one big xml file, created by a pattrstorage-object in the parent patch.

Of course, I could just save a bunch of xml files... but I don't want to!

Is this possible within the pattrstorage-architecture?

pattrstorage-storing-pattrstorage-data-in-subpatchers

just put this attribbute in th pattrstorage in the parent patcher : @greedy 1

or send the pattrstorage a 'greedy 1' message... Documented in the help file ;=)

But I don't just want the "client window" data of the subpatch-pattrstorage-objects to be saved. I also want the "storage window" data to be saved. Then I would be able to recall the different presets of the different pattr-storage objects in different subpatches, and all this data would be saved in one nice big xml file.

I don't think the "greedy 1" attribute will do! (or perhaps I'm just doing something very wrong...?)

Quote: Tarik wrote on Mon, 06 November 2006 16:18

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

> But I don't just want the "client window" data of the subpatch-pattrstorage-objects to be saved. I also want the "storage window" data to be saved. Then I would be able to recall the different presets of the different pattr-storage objects in different subpatches, and all this data would be saved in one nice big xml file.

> I don't think the "greedy 1" attribute will do! (or perhaps I'm just doing something very wrong...?)

Is this still the case? Is it impossible to store a pattrstorage's storage data within a 'master' pattrstorage, one level up?

Quote: Tarik wrote on Mon, 06 November 2006 16:18
----------------------------------------------------
> That's true,
>
> But I don't just want the "client window" data of the subpatch-pattrstorage-objects to be saved. I also want the "storage window" data to be saved. Then I would be able to recall the different presets of the different pattr-storage objects in different subpatches, and all this data would be saved in one nice big xml file.
>
> I don't think the "greedy 1" attribute will do! (or perhaps I'm just doing something very wrong...?)
>
>  - tb
----------------------------------------------------

Is this still the case?  Is it impossible to store a pattrstorage's storage data within a 'master' pattrstorage, one level up?


I'm interested about that too... Saving all the data of a pattrstorage in a "Master Preset", switch to another "Master Preset" then switch back etc... I can imagine a way to do achieve that with "coll" object but maybe there is a simpler way ?

Is it possible to automatically write new .json file (without user prompt) for each new "Master Preset" created ?

I'm interested about that too... Saving all the data of a pattrstorage in a "Master Preset", switch to another "Master Preset" then switch back etc... I can imagine a way to do achieve that with "coll" object but maybe there is a simpler way ?
Is it possible to automatically write new .json file (without user prompt) for each new "Master Preset" created ?
Thanks !

I'm not sure what you are after, but that is possible:

- pattrstorage for each subpatch or bpatcher

- a top level pattrstorage that stores & recalls the state of the different pattrstorages in subpatches

- to automatically write a new json file when you create new preset, you just do "store" to store the preset then "write" or "writeagain" (use trigger to do one automatically after the other)

Try to build a simple patch doing just that before applying to a larger project.

I'm not sure what you are after, but that is possible:
- pattrstorage for each subpatch or bpatcher
- a top level pattrstorage that stores & recalls the state of the different pattrstorages in subpatches
- to automatically write a new json file when you create new preset, you just do "store" to store the preset then "write" or "writeagain" (use trigger to do one automatically after the other)
Try to build a simple patch doing just that before applying to a larger project.

I'll try to explain correctly and clearly what I want to achieve:

- I only have 1 subpatcher with 1 pattrstorage + 1 Top level pattrstorage

- I would like to have a independant "sub" pattrstorage for each Top level pattrstorage slot.

- Top level pattrstorage slot 1 --> sub pattrstorage: slot 1 = 11; slot 2 = 12; slot 3 = 13

- Top level pattrstorage slot 2 --> sub pattrstorage: slot 1 = 21; slot 2 = 22; slot 3 = 23 

- Top level pattrstorage slot 3 --> sub pattrstorage: slot 1 = 31; slot 2 = 32; slot 3 = 33 

Am I obliged to have a new .json file for each Top level pattrstorage slot ? If yes, I tried writing automatically a new .json file based on the Top level pattrstorage slot number but with no success, I think I'm missing something here, I thought I understood how it works but obviously I'm wrong...

Hi Jean-Francois Charles !
Thanks for replying !

I'll try to explain correctly and clearly what I want to achieve:
- I only have 1 subpatcher with 1 pattrstorage + 1 Top level pattrstorage
- I would like to have a independant "sub" pattrstorage for each Top level pattrstorage slot.

for exemple:

- Top level pattrstorage slot 1 --> sub pattrstorage: slot 1 = 11; slot 2 = 12; slot 3 = 13
- Top level pattrstorage slot 2 --> sub pattrstorage: slot 1 = 21; slot 2 = 22; slot 3 = 23 
- Top level pattrstorage slot 3 --> sub pattrstorage: slot 1 = 31; slot 2 = 32; slot 3 = 33 

ans so on...

Am I obliged to have a new .json file for each Top level pattrstorage slot ? If yes, I tried writing automatically a new .json file based on the Top level pattrstorage slot number but with no success, I think I'm missing something here, I thought I understood how it works but obviously I'm wrong...

Thanks again for your help !


Make a simple patch with what you want to achieve (including some data ui objects which state you want to store).

Given your example, I don't see the need for "sub-pattrstorage": you could have a top-level pattrstorage recalling the data in your subpatch.

Or you could have a local pattrstorage in the subpatch, and the "top-level" pattrstorage just recalls the preset number.

Patch?
Make a simple patch with what you want to achieve (including some data ui objects which state you want to store).
Given your example, I don't see the need for "sub-pattrstorage": you could have a top-level pattrstorage recalling the data in your subpatch.
Or you could have a local pattrstorage in the subpatch, and the "top-level" pattrstorage just recalls the preset number.

Pattrstorage storing pattrstorage-data in subpatchers.