Well screen burn can happen with anything else, from using the Track Info screen to the menus... If it was really a big deal, it could certainly be offset by randomly choosing a position for the timecode one-pixel in each direction... Wouldn't really be noticable to the user, but it'd save those same pixels from being used. It could move when tracks change, or on reboots, or whatever. Alternately, just use a lower-intensity shade for the timecode... How prevalent is burn-in on the MkII display?

(Doh I just realized my typo in the thread title...)

-Tony
MkII #554