aldymachine

I'm using the keys on my laptop to control my max patch. The problem I'm having is that when things get going, even though "overdrive" is on in my DSP settings (and my midi controller is working without incident) the "key" and "keyup" objects seem to be set to low priority and my keyboard input ceases to operate smoothly and on time. I used the "defer" object to bump "key" and "keyup" to the top of the low priority ladder, which helped a but, but its still good enough.

Is there any way to specify an object as being "high priority" – like on the level of a midi trigger or metro event?

Max 6.1.9
OS X 10.10.2
MacBook Pro (Retina, 15-inch, Mid 2014)
2.8 GHz Intel Core i7
16 GB 1600 MHz DDR3


setting-key-and-keyup-as-high-priority-processing-thread

you can never have anything coming from outside acting like the sheduler.

this does not make the input faster ... but at least this way you can implement safe threading now, for example when your key input has to control more than one thing:

1.
you can never have anything coming from outside acting like the sheduler.

2.
but you can move things to the hp thread after they came in by using a delay:

awesome, I'm going to try this! Thank you

setting "key" and "keyup" as high priority processing thread