There must be something incredibly stupid I'm doing but...I have a strange bug (or is it a bug?):
I have "key" object inside my M4L device I'm using to trigger various Live.objects. It was working, (I'm not using the KEY MAP Assign in LIVE). Then it stopped working, only to be discovered by chance that I had to CLICK on the Device window (any device window of any track, M4L MIDI or Audio device) in order to get the Max "key" objects to function! If the mouse is clicked on any other region, it will not work.
I can remember to click on the device window before I start performing (interactively, I have to be hands off once the pieces start), but is there a way to avoid this from happening? If not I guess I would have to figure out using the mousestate object to go around it...?
Any pointer appreciated....here is a test sample to put in any track named simpletriggerMK.amxd - '1'= 1 's' = 0. It works as long as you click on this device window....