ShelLuser

See the test patch below, its a Max midi effect.

Just dump the patch in & save it, you'll have just enough space to manually press the live.button yourself even when not using presentation mode. Now open the Max runtime window (right click on patch titlebar & chose 'open max window').

You will see an entry "grabbed_output" which tells you the current song time.

You'll see the bang being triggered by the if command, this reaches the exact same routine as the one triggered by the live.button only this time the output of live.object isn't grabbed any longer.

Am I overlooking something obvious or did I hit a bug here?

inconsistency-with-grab-and-live-object

It has something to do with the message priorities within max. A midi message like any other timing critical message run on a higher priority as the user interface initiated messages (e.g. button). So with a deferred midi bang before grab it works "as expected". right ?

I confirm this behavior.
It has something to do with the message priorities within max. A midi message like any other timing critical message run on a higher priority as the user interface initiated messages (e.g. button). So with a deferred midi bang before grab it works "as expected". right ?


Inconsistency with grab and live.object ?