(Running the latest Max 8.2.0) Seems I may have found a bug in mtr- unless someone can explain that it's not a bug... and why the behaviour might be useful.

using the addevent message into mtr: I believe the normal behaviour intension is to always addevent without note output out the respective track outlet, but I've found that for the first addevent message since clear, if the message is sent after the absolute time (I'm using ticks, haven't tested with ms) being set in the addevent message, the note will be pushed out the track outlet. Subsequent addevent messages do not sound till clear.

hopefully that's clear enough, if not let me know

using the addevent message into mtr: I believe the normal behaviour intension is to always addevent without note output out the respective track outlet, but I've found that for the first addevent message since clear, if the message is sent after the absolute time (I'm using ticks, haven't tested with ms) being set in the addevent message, the note will be pushed out the track outlet.  Subsequent addevent messages do not sound till clear.

(Running the latest Max 8.2.0) Seems I may have found a bug in mtr- unless someone can explain that it's not a bug... and why the behaviour 

Potential mtr bug?