I don't know if the sticking button condition could be related to the IR. As I understand the way IR signals work, a runaway condition couldn't happen because of them. IR signals don't send button down and up codes as two separate things. If they did, you'd induce runaway conditions all the time simply by moving the remote before releasing the button. The way that IR signals get a button to repeat is that there is a "repeat last command" code in the IR commandset. If you hold down a button, it sends the code for that button followed by stream of "repeat" codes.

Now, your contention is that the runaway condition isn't caused by IR commands, but that the system might be getting confused when it receives a random IR signal combined with a button press. This is a good guess, but if that were the case, wouldn't we be getting spurious random commands activating the unit even when we weren't pressing the buttons? For example, the unit is designed to wake up from sleep mode at any button/IR signal. I've never seen it wake up without my explicit instructions, have you?

Besides, I spent a lot of time trying to induce the bug by deliberately combining IR commands and button presses. The frequency of the ocurrence of the bug was no greater than with button presses alone.

Tony Fabris
Empeg #144