When I look at the first two pictures of Rich's it seems like the text is fine when the cursor is in the editing box (i.e. when the box appears around the block of text). So in pic 1, he's editing the metadata at the bottom of the screen, and the lyric text looks bad. In pic 2, he's editing the lyrics, and it looks good. But I would presume when he's done editing and clicks outside of the text box, the text reverts to that "choppy" kind of look.
In pics 3 and 4 the effect is much less obvious - maybe that's because of the Arial font (it looks like Arial, anyway)?
That's what's happening for me. When the cursor is in a text box and I'm making edits - whether to lyrics, or metadata - or whatever (I believe it's happening across cue types, but I'll verify that), it looks like it should. But once done editing, in both the control display and on the main display, the text looks like it's got really bad anti-aliasing, just like in pic 1 of Rich's, above.
If I have time tomorrow I'll upload some screenshots.
Re: resolution, our control monitor use 1280x1024, which is the native resolution of the control LCD monitor. Our main display is 1024x768, which is the native resolution of our projector. We're not using stage display on our backup, since the video card can't handle it and we can't put our newer video card into that computer. But in our new build we'll go back to using stage display on an HD TV. We've run that at both 1280x820 and 1920x1080 (which is the TV's native resolution).
The thought just struck me now that I see Rich's aspect ratio is 4:3, as is ours on the main display. I've had other issues in v6 testing with the 4:3 ratio, which I've conversed a bit about with support. Could it be related to that somehow? I'm wondering if support for 4:3 is lacking since most are likely running 16:9 main displays now?
Again, once I get our new build done, maybe I'll test it using our TV as the main display, just to see what happens.
Thanks again for your prompt responses.