Forums > MaxMSP

Pattrstorage inefficient in runtime

May 13 2013 | 4:14 pm

I just want to share the experience that I cannot seem to use [preset] object with [pattrstorage] despite parameter mode enabled in a Runtime patch. The fact is the "dirty bit" indication never goes on, as an application that doen’t sense it has been altered. I remember reading about a max indicator object for that, would that serve as a workaround for not being able to save presets with Runtime?

May 13 2013 | 7:47 pm

did you try @savemode 3 on your pattrstorage?  Seems to work here.

May 14 2013 | 2:31 pm

You have to save an actual pattrstorage file when using Runtime. The patch itself can’t be altered, nor can any application, I believe…settings and presets within applications are always managed by external files that can be modified. (If I’m wrong please advise—interested to know if this is true.)

Look to the "path" message to [thispatcher] and the [sprintf] help file for file location management. It’s a bit tricky to format the messages at first so read the help file carefully and save yourself some fiddling time. Also, use a [thispatcher] in the TOPMOST patch, not a subpatch or bpatcher.

If you’re using a standalone application, you’ll need to use

;max sendapppath

because the [thispatcher] message doesn’t work in standalones. Check the docs for "Messages to Max" and you’ll be all set…and maybe pick up some other goodies along the way…

May 14 2013 | 2:42 pm

I realize I keep asking about this same very precise topic, truth is, it is pretty vast to assimilate. Thank you for the answers, I slowly start to understand.

…except it is of course the big version to run everything through [pattrstorage]

@ Nat no, savemode 3 isn’t working here, was also kind of hard to set but at no point i had it working..

Viewing 4 posts - 1 through 4 (of 4 total)

Forums > MaxMSP