Alix Gosse

I'm going pretty used to max/MSP right now and making lot of 1h/2h speed patching challenges.

I want to keep some record of my progress and be able to keep the patch the way it is when I quit my session.

I understand pretty well the concept of snapshots and parameters enable you have to set for some of the objects in max.

But in practice it takes me almost the same amount of time to set all needed objects to parameter enable (enabling snapshot record) than i takes to make the patch.. And I always forget parameters cause there are so many to double check.. Isn't it any mean to set every object (in patcher and subpatch) at once to the "parameter enable" state? Did I miss something? Would it be non-sense for some program behaviour reason? Or is it a lack of a feature?

I'm going pretty used to max/MSP right now and making lot of 1h/2h speed patching challenges.
I want to keep some record of my progress and be able to keep the patch the way it is when I quit my session.
I understand pretty well the concept of snapshots and parameters enable you have to set for some of the objects in max.

all-parameter-enable

Another question on that same matter of workflow. Isn't it any option to select by type of object?

Something like I would like to edit in inspector all integer object size, or color, or parameter enable for that case.

Any function to tell max : please select all siblings integer objects?

Another question on that same matter of workflow. Isn't it any option to select by type of object?
Something like I would like to edit in inspector all integer object size, or color, or parameter enable for that case.
Any function to tell max : please select all siblings integer objects?


about parameters: i would not do it this way. i would 1. try to avoid GUI objects in my final version of the patch wherever possible and 2. regulary use loadbang to put GUI objects into an initial state.

the snapshots, pattr, preset or pp/plugconfig systems in my opinion work all for special cases only.

roman is very right with everything he said :) to give you a hint as for proceeding:

1) pattr-nize all objects/GUI in your patch (with pattr objects)

2) set initial values for these pattr objects (via inspector or argument)

3) send a message "send pattr init" to the [universal 1] object within your parent patch. adding the "1" as an argument to the universal object makes it address all subpatches, too

i suggest doing in depth read-up on the pattrstorage object. this stuff is super powerful!

roman is very right with everything he said :) to give you a hint as for proceeding: 

1) pattr-nize all objects/GUI in your patch (with pattr objects)
2) set initial values for these pattr objects (via inspector or argument)
3) send a message "send pattr init" to the [universal 1] object within your parent patch. adding the "1" as an argument to the universal object makes it address all subpatches, too

i suggest doing in depth read-up on the pattrstorage object. this stuff is super powerful! 

Thanks for [universal]. Even better that option relies on an object instead of max UI !! Many amazing objects I have not discovered yet on max.

Thanks for [universal]. Even better that option relies on an object instead of max UI !! Many amazing objects I have not discovered yet on max.
I'll give deep look on pattrstorage.

All parameter enable?