[jitter] Re: Re: unbelievable

Just one small clarification to this thread. Vade is almost correct,  
however to be precise, the number object does not actually have the  
cost of *drawing* when hidden, but rather what happens is that it  
schedules a "qelem" (which fights for the same number of queue slots  
as jitter), and that qelem checks to see if the object is visible  
before actually drawing. It is the number of objects that have been  
added to the queue that in effect reduce framerate. So eliminating  
hidden UI objects which are rapidly updated is important still, even  
though technically they don't render themselves.

Of note, we've changed the way UI updating works in Max 5, so  
hopefully some aspects of this will improve.

Evan's suggestion of separating the video engine from UI in two  
different processes is *highly* recommended for complex UI with  
faster and more accurate movie playback. Not always the easiest thing  
to do, but for those of you looking for maximum performance, it may  
be worth the effort.

-Joshua