It seems there is some strange behavior with timepoint when you try to:
1. Use a timepoint object to "loop" a transport by rewinding the transport to 0 everytime you hit a certain bar.beat.unit.
2. Use a separate timepoint object to try to detect that same bar.beat.unit that the transport is being rewinded on.
For example, you have a timepoint object that is banging at 2.1.0, and you use that bang to reset the transport to 1.1.0. Then, elsewhere in the patch you have another timepoint object that is banging at 2.1.0.
Expected behavior: the "remote" timepoint object should bang each time the transport reaches 2.1.0.
Actual behavior: the "remote" timepoint object actually only bangs every other time the transport reaches 2.1.0, resulting in only half the number of bangs compared to the timepoint object that is rewinding the transport.
See attached max5 patch to clarify.
Can anyone confirm that this is a bug?
I'm using Max 5.0.5, Mac OS X 10.4.11