When I run this patch the message boxes should both display 2.1.0, but the quantized metro shows 2.2.0. If I start the metros at 1.1.0, it sometimes works properly. With any other autostarttime the quantized metro is one beat late.
I got excited when I saw this in the Max 5.0.4 bug fix list:
"timepoint: fixed potential missed triggers when using named transports, tempo changes, and/or autostart metros"
But alas, I am still seeing the behavior I reported in this thread.
Was that timepoint fix supposed to fix this problem? I looked into it a little more and it seems that metros using autostart/autostarttime/quantize will start at the autostarttime + the quantize time. In other words [metro 4n @autostart 1 @autostarttime 2.1.0 @quantize 64n] will start at 2.1.30 and then continue to bang at .30 ticks after the beat. If I specify the autostarttime it should start at that time, right?
I got in the habit of not using quantize for this sort of thing, so I can live with this behavior. But it's very counter-intuitive and bound to confuse other Max users. I'm also bothered by the fact that not everyone seems to experience this behavior (see Chris Muir's reply above), so I don't feel confident patches made on one computer will work the same way on another computer.