Related to the problem reported by dg3nec about the VU-meters, i have found a way to reproduce easily (at least on my laptop, in both xp and w7).
Load a song on any deck, start playing it, and then just modify any EQ channel (any tiny amount) put the VU-meter of the deck and the global one on the reds for a second -weird because the green bar/sound volume is nowhere near- , and then they are "locked" (are not updated any more, keep the last value). So you can "lock" one vu-meter and the global one, and keep using the other... until you equalize it, that is
Gain or FX seems to work fine and don't trigger the bug.
May i fill a standard bug report on launchpad?
Update: Related to the EQ's, the kill buttons also triggers this bug, just using a controller directly triggers the bug -because it has to restore the controller position by script at init, don't know-), and the only part that is "locked" is the green bar, because i've seen that the reds continue to work as usual
. As a side note, i have an script for the nanoKontrol2, that use the lights as vumeter, and it fails exactly the same as the screen.
BTW, the EQ part has been touched? It seems that they are messed up... highs are lows, meds are highs and low does nothing...