[maxmsp] Re: Drift

Odd how I can scour those examples over and over and still miss most of them.  

Anyway, It appears that I need to give up about 8 ms of latency by moving from 64 to 128 in IO. (Mathmaticaly, shouldn't I pick up about 3ms considering we're measuring input and output?) But I can gain max scheduler resolution by moving from 64 to 32 or so. I'm not to broken up about that, although it feels pretty sluggish to play through.

Am I on the right track? Are we saying is that this is expected behavior if the I/O vector is low enough?


I guess looking back, I had figured that a simple in-to-out mapping  wouldn't take any horse power, so layed the blame on something external as if it might have been msp's fault.  This patch refutes that by telling me that if I set the I/O vector low enough, the latency ramps up as if to say "I can't keep up here"