lawnghost

I'm trying to make a patch that takes actions based on midi note on/off events. I'm using the notein & borax objects to parse incoming midi messages. The problem I'm running into is when an ON & OFF message occur simultaneously. My patch will start running for one of the messages, but it gets interrupted in the middle of processing by the second message. I know I can use speedlim to throttle the speed of incoming messages, but I don't want to introduce unnecessary latency. Is there some way to mark a patch "high priority" or otherwise allow it to finish evaluation before processing subsequent midi messages?

I'm trying to make a patch that takes actions based on midi note on/off events.  I'm using the notein & borax objects to parse incoming midi messages.  The problem I'm running into is when an ON & OFF message occur simultaneously.  My patch will start running for one of the messages, but it gets interrupted in the middle of processing by the second message.  I know I can use speedlim to throttle the speed of incoming messages, but I don't want to introduce unnecessary latency.  Is there some way to mark a patch "high priority" or otherwise allow it to finish evaluation before processing subsequent midi messages?


midi-note-event-priority

https://cycling74.com/articles/event-priority-in-max-scheduler-vs-queue/

yes! thank you! deferlow is what i was looking for.

I'm embarrassed to say I came across the article before, but dismissed it too quickly, thinking it was only about "overdrive".

yes! thank you! deferlow is what i was looking for.
I'm embarrassed to say I came across the article before, but dismissed it too quickly, thinking it was only about "overdrive".

midi note event priority?