The event priority in Max is something one might not be aware of all the time, but having an idea about it helps a lot. To put it simply, there is a high priority thread (often called the scheduler) and a low priority thread (often called the queue) for Max messages if we turn on Overdrive. Otherwise, these are executed in one thread, with the same priority. Max just has two lists of things to do and does the things on both lists, but it can interrupt things being done on the low-priority list, to first finish the high-priority thread. What events are in which thread? Things such as GUI interaction get in the low-priority thread while MIDI input, for example, is in the high priority one. We can use the [deferlow] object to place an event at the end of the low-priority queue, or [defer], to put it at the top of the low-priority list. The [defer] object, therefore, might mess up the order of events since there most likely are things on the low-priority list to be done and...