Yes, that's what I'm saying.rainwarrior wrote:Or... are you talking about a TV that does output a picture that changes at 60fps by alternatingly updating the even and odd lines? (I don't believe I've ever encountered that in an LCD TV.)
You won't be able to tell the difference with a 30fps flicker:tokumaru wrote:If a sprite flickers, I get alternating scanlines with and without the sprite, with no visible changes from one target frame to the next.
Fields: A b C d E f (lowercase meaning the not-drawn flicker state)
30fps deinterlace: Ab Cd Ef
60fps deinterlace: Ab Cb Cd Ed Ef
In both cases you'll see an almost-identical comb-y result.
With a 1/3rd duty flicker (20Hz) the difference will be obvious:
Fields: A b c D e f G
30fps deinterlace: Ab cD ef - it will now appear to flicker at 10Hz
60fps deinterlace: Ab cb cD eD ef Gf - this will still flicker at 20Hz
I don't know how starting with a 60i source changes the motion prediction in a 120Hz TV. Certainly I can see that they'd interrelated, such as with mplayer's "mcdeint" deinterlacer which uses motion compensation to produce plausible lies for the missing scanlines, and the same motion compensation data would also be used to generate the entire missing frame for 120Hz rendering.rainwarrior wrote:What about 120hz TVs?