To my understanding non of the live objects allow dynamic updating or changing because of storing and recalling schemes. Once objects have been made they are expected to remain stable. Of course it is possible to use the regular menu object. When you dump for instance the content in a textedit object as well, with the pattr object (in blob mode) it is possible to store date.
Thanks for your reply.
The thing is I want to have the values showing up on my midi controller and the only way to do that, as far as I know, is with the live.* objects.
I did get the feeling that I should use the pattr object, but is it possible (and how) to get that object to populate the live.menu?
yeah that is what i would do, or similar. however, the problem is, one of the infuriating m4l things is that now this live.numbox is not midi-mappable because we cannot see it in midi map mode. i do the above post way for exposing things to the automation system, but no good for midi mapping. the workaround is convoluted. i posted on the maxforlive ableton forum about it for the op.
This is my solution, as you can simply store anything into a pattr. If you store the menu content as a simple list, and just fire that list into a umenu, the pattr content will be stored in the session....
Set the rounded attribute of umenu to 0 to make its look closer to the live.menu...