[mythtv] [mythtv-commits] Ticket #2429: Autodetect video scan is confused by 1080i recordings

Jack Perveiler perveilerj at yahoo.com
Wed Sep 20 21:24:16 UTC 2006

> > It's not wrong.  It's reporting based off of what's in the video headers.
> I see. And 0.19 did not look into the video headers?
> So, it's the fault of the channels or the provider.
> In that case, it would be extremely helpful to have a setting to force 
> this always to "interlaced" (for 0.20 fixes branch).
> BTW, what's the negative effect, if I set a progressive recording to 
> video scan "interlaced"?
> I can see no negative effect here, so maybe this means all my recordings 
> really are interlaced, but some are wrongly marked in the video headers?

Deinterlacing, at least with bob, can have some very undesirable side effects
when used with progressive content.  In my case I see two copies of every
image: one squished into the top half of the screen, the other squished into
the bottom half.  I don't know if that's what happens for everyone, but that's
what happend for me.

Which is why I thought the ability to change the default away from "detect" on
a  per-channel basis sounded interesting.  Isaac, any comment on that?  If I
coded it up, is the idea something that could be committed?  It sounds like it
won't fix everything for everybody, but could help some (myself, anyways) and
could still be overridable by the OSD selection.  I don't want to waste my time
on something non-commitable, though.


Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 

More information about the mythtv-dev mailing list