Have you checked the fans on the control panel? There is a fan mounted on the bottom of the control proc board. If you stick a little piece of paper up under the board, if it gets sucked in, fan works, if not you may have a problem. Another possible issue is network traffic. v15 has a hard time on a busy network. The switcher needs to be isolated from any computers or other network traffic. It can even help to put a network switch between the frame and the control panel. Hope this helps!

Even if that was the case, it wouldn't be lighting up 2 different crosspoints on one buss simultaneously. If it was an additional tally calculation, it would have just tallied everything on that output no matter what, which I would have noticed as a pattern. This didn't have a pattern. The lights would just not follow my button presses and then catch up several seconds later, or in this case long enough for me to get a little angry, mention a few choice words under my breath followed by a loud "Nothing" when someone asked "What?," wrestle my backpack out from under the bench with one hand while looking up, open it up, dig out my camera, put back all the stuff the leash dragged out, remove the leather pouch, turn it on, put it on the right program, select 3200k indoor light for white balance, increase ISO to maximum and take the picture with a couple of replays peppered in there. In other words, too long. Sometimes I had to pound the BKD only button to make sure my next dissolve was clean because the BKD+KEY lights wouldn't turn off. The worst was not being able to daydream about how slow the clock was moving because I had to follow all my button presses mentally.

Hey Oleg: May not be a "bug". Check the Tally settings. I walked into a truck where ME1 was set to tally all the time due to a previous split feed. Normalizing the tallies corrected the "problem". Ross