key and keyup bug in Max5

Mar 9, 2009 at 8:13pm

key and keyup bug in Max5

Hi guys,

I’ve found a bug with the key and keyup objects in Max5 – when simultaneously clicking and dragging the mouse. It’s currently effecting the performance of my glNavigator abstractions when used in Max5, so I thought I would post a simple example patch. See below.

Open it in Max4 and Max5 – notice the problem only occurs in Max5 (at least, on my machine).

Can anyone confirm?


#P window setfont “Sans Serif” 12.;
#P window linecount 1;
#P comment 8 29 368 196620 Everything works fine in Max4.6.x. The problem is Max5.0.6;
#P button 61 208 15 0;
#P button 18 208 15 0;
#P comment 16 249 463 196620 when you release a key , these should always be the same , but they’re not.;
#P number 61 180 35 12 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 61 150 45 196620 keyup;
#P number 18 180 35 12 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 18 150 40 196620 key;
#P window linecount 3;
#P comment 125 178 353 196620 In fact , you don’t even need a jitter window for this. Just click and drag around the patch while pressing different keys. You’ll notice the same behavior sometimes.;
#P comment 125 115 384 196620 Click and drag the mouse around the jitter window , and simultaneously press differnt keys. You’ll see that sometimes the key doesn’t report , other times the keyup doesn’t report.;
#P window linecount 1;
#P newex 14 109 99 196620 jit.window drag;
#P window linecount 2;
#P comment 125 69 279 196620 In Max5 , key and keyup perform as expected if you don’t click and drag the mouse;
#P connect 4 0 5 0;
#P connect 5 0 9 0;
#P connect 6 0 7 0;
#P connect 7 0 10 0;
#P window clipboard copycount 12;

Mar 10, 2009 at 1:08am

It is a Mac only bug, and we are aware of it. Unfortunately, this is the way things are at the moment, and i’m not sure when it will be fixed, as it appears to to be something to do with the Mac OS key event implementation.


Mar 10, 2009 at 3:09am

Ok, thanks for letting me know Ben. That’s quite an annoying bug, don’t know how I’m going to get around it, but I’ll trust that you’ll fix it when you can.

Hmmm… You say it appears to be an issue with the OS key event implementation, but if that were so, shouldn’t the bug also occur in Max 4.6.x on the same system? It doesn’t, everything’s fine in 4.6.x. That’w why I assumed it was a software bug in the first place.


Mar 10, 2009 at 4:28pm


From what I understand, this problem is due to fully supporting unicode in Max 5, which is a priority for us. It appears that this is something that Apple is going to have to fix.

You might have more luck with the hi object, though i understand how that could be dicey if you plan on supporting random computer setups.

apologies for the inconvenience.


Oct 23, 2009 at 10:16am

Hi Ben,

Are you aware of any progress made on this issue with Apple? Thanks.


Oct 23, 2009 at 5:57pm

I don’t have any news regarding this. It appears to still be an issue in 10.6.1. Note that this isn’t a problem on XP/Vista.

Again, apologies for the inconvenience, it appears that there is not a whole lot we can do about this right now.


May 3, 2011 at 11:02pm

A year later, I am having the same problem in Max 5 on my macbook pro with OS 10.6.7 . has there been any development solving this issue? Any good workarounds?


You must be logged in to reply to this topic.