Mari Kimura

I need to be able to let someone (clients) who doesn't own Max full version (many performers) to be able to set and recall parameters in Max Runtime for performance purposes. Since it is not possible for people using Runtime to SAVE, this is a problem for real-life performance. pattr, loadmess, preset, all won't save unless you own a full version...

I made a weird "Text" go-around in order not to have to go to edit mode on stage (for myself) but this doesn't save a new value either, unless you own the full Max.

I need to be able to let someone (clients) who doesn't own Max full version (many performers) to be able to set and recall parameters in Max Runtime for performance purposes.  Since it is not possible for people using Runtime to SAVE, this is a problem for real-life performance. pattr, loadmess, preset, all won't save unless you own a full version...
I made a weird "Text" go-around in order not to have to go to edit mode on stage (for myself) but this doesn't save a new value either, unless you own the full Max.

setting-and-recalling-parameters-in-max-runtime

did you try [pattrstorage] ? i'm pretty sure it allows exactly what you want, even for a runtime application.

Thanks for your reply. I did try pattrstorage writing and reading .json files which you CAN do with Max Runtime, but it still failed to read the data... maybe I'm doing something wrong? First change the data, then store, the write? 

Thanks for your reply.  I did try pattrstorage writing and reading .json files which you CAN do with Max Runtime, but it still failed to read the data... maybe I'm doing something wrong?  First change the data, then store, the write?   


First change the data, then store, the write?

yes ! you also need all wished data to be exposed to pattr system, ie have a scripting name then create [autopattr], or connect [pattr] to each desired ui object. There are 2 "Patcher Storage" tutorials in the Max tutorials. It should work as expected afaik.

 First change the data, then store, the write? 

yes ! you also need all wished data to be exposed to pattr system, ie have a scripting name then create [autopattr], or connect [pattr] to each desired ui object. There are 2 "Patcher Storage" tutorials in the Max tutorials. It should work as expected afaik.


Thanks so much for your help! Well I will have to go back to the tutorial... I used @savemode attribute and set it to '3', and it works fine with Max full version but not in Runtime... Maybe I'm not understanding what I have to do with the @savemode. I could even read the .json file in Runtime but doesn't read the stored data. Again pattr work great in the Max full version. I will study further....

Thanks so much for your help!  Well I will have to go back to the tutorial...  I used @savemode attribute and set it to '3', and it works fine with Max full version but not in Runtime... Maybe I'm not understanding what I have to do with the @savemode.   I could even read the .json file in Runtime but doesn't read the stored data.  Again pattr work great in the Max full version.   I will study further....


ps. The point of trying to do is for a performer who is using Max Runtime to be able to change their various levels (like reverb parameters, mic direct levels) at the dress rehearsal on stage. These balances change, depending on the acoustics of the venue. S/he should be able to set it the way they could recall even if they have to shut down the computer between dress rehearsal and the concert.... A nitty gritty real-life problems... :)

ps.  The point of trying to do is for a performer who is using Max Runtime to be able to change their various levels (like reverb parameters, mic direct levels) at the dress rehearsal on stage.  These balances change, depending on the acoustics of the venue. S/he should be able to set it the way they could recall even if they have to shut down the computer between dress rehearsal and the concert....  A nitty gritty real-life problems... :)


that it doesn't work for runtime is really strange i reckon...

I know... you would think it's the least you can do for the Runtime user :)

One thing to keep in mind upon building the collective/standalone, is to remove the json file linked to the pattrstorage from the search path, otherwise it will be included in the package, and become unmodifiable.

have you tried @fileusagemode 1 in the pattrstorage object?

YESSSS!!!! It worked!! I did try what you both suggested: 1) remove the .json file from the search path when saving in the Max Full version, and 2) use @fileusagemode 1 attribute.

Thank you so much for all of you!!!! Now someone can run Max Runtime and change values and save :) I just have to make sure the instruction is clear (which is a challenge for me :)

YESSSS!!!! It worked!!  I did try what you both suggested: 1) remove the .json file from the search path when saving in the Max Full version, and 2) use @fileusagemode 1 attribute. 

Thank you so much for all of you!!!! Now someone can run Max Runtime and change values and save :)  I just have to make sure the instruction is clear (which is a challenge for me :)

What floating point suggests is of course the best way, and I am happy my ignorance concerning this was cleared!

I'm having many troubles with .mxf files (or standalones) so I was just giving the full Max patch to people who is using the Max Runtime. I'm just too lazy to compile FTM objects that I use -- it needs to be handled separately when building .mxf.... Thanks again!

I'm having many troubles with .mxf files (or standalones) so I was just giving the full Max patch to people who is using the Max Runtime.  I'm just too lazy to compile FTM objects that I use -- it needs to be handled separately when building .mxf....  Thanks again!


Setting and recalling parameters in Max Runtime