Problems with m4l docs
Among the many, many problems with m4l docs, there is this;
The autopattr object does not work with Max for Live’s parameter system
3. Add an autopattr object to your device
Another big, big problem is that descriptions of pattrstorage parameter mode lead one to believe that presets are stored in the set _file_, whereas they are actually stored in a separate file in the _set folder_. This is a major source of concern for file management and performance.
M4L is a wonderful program. Shouldn’t it be wonderfully documented?
I think this is quite clear. I notice that you left out the sentences below it:
"The autopattr object provides an easy to way manage the state of standard Max objects, but it will not work with the parameter system, so objects that are attached to an autopattr will not be seen by Live. If you want a pattr parameter to appear for modulation etc, you will need to add a pattr object for each instance."
Perhaps the problem is that you assume that the only reason you’ use pattr would be for stuff exposed to Live. Not everyone works in that way (Me, for example). In any case, it’s just a matter of adding pattr objects, which isn’t a big whoop. How would it please you to make it clearer?
You are correct in that I didn’t read the rest of that entry. Sorry about that.
I guess I would prefer not having to reread the docs several times before understanding them. I can’t really get more specific than that without rewriting things. Clearly "the fault may lie in ourselves", without a doubt, but this is definitely not the first set of docs I’ve ever read.