This is cool. I figured out how to do Automated state-saving in MobMuPlat.

In order to better emulate (virtually via OSC) how my arduino/pi project will actually behave, i.e. the location of hardware knobs can't be set on loadbang, I needed a mechanism for mmp to constantly retain its state. So like hardware knobs they kept their "place".

)aside: the fromGUI toNetwork is Not part of the idea.)

mmp-state.zip

See the zip to demo it.

It only requires that you FIRST make a .txt "state" (ex. mmp-state.txt) file listing all the control addresses you want to save/load and a dummy value for each address.

Works like a charm.

May it serve you well.

Note: the 10s automated save period is completely arbitrary and you could even set it with a knob, slider, textdialog etc.

Peace through sharing,
S

p.s. a todo would be make it automatically harvest the control names/addresses by loading itself (the .mmp) file into a [text] object and just searching for the control classes and write that file as the mmp-state.txt ...perhaps another day

mmp-state-saving.zip

One of the great benefits and allures of Mobmuplat is it allows (via OSC) you to create virtual versions of hardware, ex. arduino, HID controllers etc.

But one of things it does NOT naturally do is retain state. And while loading initial states, via loadbang, is nice, it is very clunky and does Not emulate hardware.

What this (class) abstraction does is:
Read all incoming GUI values (address+values) and writes them to a [text]. If the controller hasn't been changed yet, i.e. it's "new", then it adds a row to the [text]. If it is not new, then it finds that row (via search) and amends it with the new value(s) (that includes multi-value controls like xy-slider and multislider, though the multislider must be in "output all sliders mode"). It then uses menusave to save the [text] and just reads it back in on loadbang.

It takes one creation argument: the period in ms of the metro which sends a bang to the menusave message.

So...

By copying and renaming the abs to whatever you want, for instance, {name-of-main-mmp-patch}-state.pd, then dropping that abs into your main mmp patch it will always be exactly like you left it. Then the next time you open the MMP document, it behaves like hardware, with all the knobs, sliders, etc. being where you left them.

p.s. not going to bother with screenshots. As the zip files are very self-explanatory and include a demo.

Peace through sharing. I hope your day is going well.

Sincerely,
S

Supports:

MMPSlider
MMPKnob
MMPToggle
MMPXYSlider
MMPMultiSlider

Does Not Support:

MMPButton (nonsensical)
MMPLCD (no input)
MMPGrid (non-linear)
MMPMenu (output!=input)
MMPMultiTouch (no input)
MMPPanel (no output)
MMPTable (output!=input)