Steve Valentin

I am building a undo & save system for a future max standalone. My current approach functions with pattrstorage.

i have several selectable "clips" wich stand in relation to a "main" window with several changeable settings. The settings in this window always are connected to the selected clip and are also beeing temporarily saved inside this clip so that when switching clips the settings are always being fed back to the "main" window. ...Imagine ableton live's clip view and the underlying waveform editor, that was the role model.

Now in order to be able to undo & save these settings permanently per "clip" i would need to send the changing information from the "main" window to one of many pattrstorage objects inside the respective "clip", while inside the "main" window there is only one set of pattr objects since this window remains static all the time and only exists once. 

This would mean that the same set of pattr objects would need to send its information to many pattrstorage objects but never to more than one at the same time., right...?

For example with 3 available "clips" and with clip 1 being selected, the pattr objects inside the "main" window would need to be invisible for clip 2 & 3 and only send to pattrstorage inside clip 1. When selecting clip 2 the pattr objects inside the "main" window would need to be invisible for clip 1 & 3 and only send information to the pattrstorage inside clip 2. And so on...

Is there a way to do this? Thanks for your help!

I am building a undo & save system for a future max standalone. My current approach functions with pattrstorage. 

The setting is the following:
 i have several selectable "clips" wich stand in relation to a "main" window with several changeable settings. The settings in this window always are connected to the selected clip and are also beeing temporarily saved inside this clip so that when switching clips the settings are always being fed back to the "main" window. ...Imagine ableton live's clip view and the underlying waveform editor, that was the role model.  

Now in order to be able to undo & save these settings permanently per "clip" i would need to send the changing information from the "main" window to one of many pattrstorage objects inside the respective "clip", while inside the "main" window there is only one set of pattr objects since this window remains static all the time and only exists once. 
This would mean that the same set of pattr objects would need to send its information to many pattrstorage objects but never to more than one at the same time., right...?

For example with 3 available "clips" and with clip 1 being selected, the pattr objects inside the "main" window would need to be invisible for clip 2 & 3 and only send to pattrstorage inside clip 1. When selecting clip 2 the pattr objects inside the "main" window would need to be invisible for clip 1 & 3 and only send information to the pattrstorage inside clip 2. And so on...

Hi
I am building a undo & save system for a future max standalone. My current approach functions with pattrstorage. 
The setting is the foll

multiple-pattrstorage-objects-inside-multiple-subpatchers-but

If each clip is in a named bpatcher for example clip_1, clip_2, clip_3 etc.. when you select Clip_1 it can send to the main pattrstorage the messages "active clip_2 0, active clip_3 0"

So you can have a message to your pattrstorage with " active $1 $2" and feed this message with the inactives clips.

If only one clip has to be selected in the same time and all others have to be inactivated by thiq selection I use for that purpose a little [matrixctrl] before with the option "only one cell per matrix" so if one cell corresponds to one clip, selecting it will make the matrixctrl to send "0" for all the other and you can format those "0" to inactive all the others clips..

Hello.
 Away from keyboard.
If I understand well.. not sure ;)
If each clip is in a named bpatcher for example clip_1, clip_2, clip_3 etc.. when you select Clip_1 it can send to the main pattrstorage the messages "active clip_2 0, active clip_3 0"

So you can have a message to your pattrstorage  with " active $1 $2" and feed this message with the inactives clips.

 If only one clip has to be selected in the same time and all others have to be inactivated by thiq selection I use for that purpose a little [matrixctrl] before with the option "only one cell per matrix" so if one cell corresponds to one clip, selecting it will make the matrixctrl to send "0" for all the other and you can format those "0" to inactive all the others clips..

Dont know if I am very clear..
I can post a patch later...


Yes of course! This could definitely be a way to do it... Will try that. Thanks!

Yes of course! This could definitely be a way to do it...  Will try that. Thanks!

to explain what I said about the little matrixctl that can be used to inactivated the other clips when one is selected. Still not sure if it's useful in your case but maybe =)

image.png

to explain what I said about the little matrixctl that can be used to inactivated the other clips when one is selected. Still not sure if it's useful in your case but maybe =)


Ah, i see... Interesting. In my case everything is packed into subpatchers. The single clips are all inside their own bpatchers but can check with each other who is selected and who is not. So the solution of the problem by activating and deactivating pattrstorages inside the clips' bpatchers would be perfect because it would be super easy to implement, ...if the clips only were'nt at the verry bottom of the patcher hierarchy... A new problem occurring here is that the pattrstorages inside the single clips wont even see the pattr objects, wich are inside another bpatcher – although the bpatcher holding the pattr objects is actually not inside the same patcher hierarchy but inside a bpatcher that has nothing to do with the hierarchy of the clips. I have no idea how max handles priorities in such a case... (not to my favour at least).

Would there be a way to make these pattr objects visible to the pattrstorrages inside the clips. I tried greedy, that wont help so far.

Ah, i see... Interesting. In my case everything is packed into subpatchers. The single clips are all inside their own bpatchers but can check with each other who is selected and who is not. So the solution of the problem by activating and deactivating pattrstorages inside the clips' bpatchers would be perfect because it would be super easy to implement, ...if  the clips only were'nt at the verry bottom of the patcher hierarchy... A new problem occurring here is that the pattrstorages inside the single clips wont even see the pattr objects, wich are inside another bpatcher – although the bpatcher holding the pattr objects is actually not inside the same patcher hierarchy but inside a bpatcher that has nothing to do with the hierarchy of the clips. I have no idea how max handles priorities in such a case... (not to my favour at least).

Maybe you can have only one pattrstorage at the top of your patch and use (active $1 $2) to select which bpatcher you want to active..Not sure if you need several pattrstorages for that. 

You can then recall things only on the choosen bpatcher with (recall bpatcherX::yyy "preset number")

Maybe you can have only one pattrstorage at the top of your patch and use (active $1 $2) to select which bpatcher you want to active..Not sure if you need several pattrstorages for that. 
You can then recall things only on the choosen bpatcher with (recall bpatcherX::yyy "preset number")

I spent some time trying to imagine how this could work ...i have to say i am not that experienced with pattrstorage.

I can imagine your idea well if i'd have the objects, whose settings need to be saved, inside the clips. It would then be possible to disable the objects inside the unselected clips and have only the relevant objects sending information to one pattrstorage inside the top patcher. So far i understood.

But it would need to be the other way around: Information from objects outside the clips would need to go inside the clips ( rsp. only into the active/selected clip) so that every clip has its own private settings saved.

or am i totally misunderstanding something?

I spent some time trying to imagine how this could work  ...i have to say i am not that experienced with pattrstorage.

I can imagine your idea well if i'd have the objects, whose settings need to be saved, inside the clips. It would then be possible to disable the objects inside the unselected clips and have only the relevant objects sending information to one pattrstorage inside the top patcher. So far i understood.
But it would need to be the other way around: Information from objects outside the clips would need to go inside the clips ( rsp. only into the active/selected clip) so that every clip has its own private settings saved. 

To close this: a solution was, to send values via patrhub object > whenever a clip gets selected it tells the main window its id number wich serves as a prefix to send the information back to the right clip. So kinda similar as schlam proposed but with a little twist. :)

Multiple Pattrstorage Objects inside multiple Subpatchers, but...