If I want to have PATTR control of a bunch of variables, what is the best way to implement that. What is the still pattr-able substitute for a number box?
Simple example would be 10 objects with editable xposition, yposition, xscale, yscale type information for each object that is then saved as presets with pattrstorage. Would Jit.cellblock still allow me to crossfade between presets smoothly?
Like the existence of any key object is the problem? Interesting, because I always have at least one in there for taking my window output to fullscreen. Or do you specifically mean a key object tied into triggering of quicktime?
Since I've heard conflicting information in the past on this subject, I'd like to be perfectly clear on this.
Is it correct that any lowly number box, even if hidden in some unopened sub-patch whose state has not been changed since the Babylonians, will still be updated by the Max scheduler and thus drain CPU?
I can understand how using [value] and/or [pattr] to display numbers via [prepend set] to a messages boxes would be less prone to GUI updates, but how does this help one with data that needs to be changed by the user as in the previous post? Does dropping an [autopatter @autoname 1] into that same sub-patch cause its state to only be updated when it changes?
BTW, I have noticed significant reduction in frame rates using signal level meters, multi-sliders, pwindows, and all the usual suspects. My solution is to use a 'GUI switch' which is a gate (and gate~) for all of the above so that you can use the GUI's to view all those things you would like to in your patch, but if the frame rates drop too low, you can cut them off and watch the frame rates soar. This is why I'm skeptical that number boxes whose states are not changing will eat up CPU, but I'm no expert.