[mythtv-users] interlace issue on TV?

[Tom Dexter]

On Fri, May 1, 2009 at 10:14 AM, Paul Gardiner <lists at glidos.net> wrote:
> Udo van den Heuvel wrote:
>>
>> Tom Dexter wrote:
>>>>>>>>
>>>>>>>> At the start of this topic I explained how the VIA XvMC setup at is
>>>>>>>> this point.
>>>>>>>
>>>>>>> Select "Interlaced(x2)" as your deinterlacer.
>>>>
>>>> As primary or backup?
>>>> I can't find this deinterlacer in the list.
>>>>
>>> I did notice when I set mine up that the new deinterlacer didn't show
>>> up when XvMC is set as the decoder.  I use either ffmeg or libmpeg2 so
>>> it made no difference to me.  I don't know if that's by design or not.
>>>  Paul may be able to answer that.
>>
>> Thanks, interesting observation as I do use XvMC, as posted earlier.
>> Paul? Can I fix this?
>> Or is it teh patch?
>
> Oh might be the patch. I use ffmpeg too, so I hadn't noticed
> Interlacedx2 not appearing with XvMC.
>
> P.


I think (??) it may need to be added to this block of code in
libs/libmythtv/videodisplayprofile.cpp around line 1490:

    QStringList::const_iterator it2;
    for (it2 = tmp.begin(); it2 != tmp.end(); ++it2)
    {
        safe_deint[*it2] += "bobdeint";
        safe_deint[*it2] += "onefield";
        safe_deint[*it2] += "none";
        safe_osd[*it2]   += "chromakey";
    }

That is, a new line something like:

safe_deint[*it2] += "fieldorderdoubleprocessdeint";

...added into that block.  Now whether or not it actually works is
another story.

I'll see if I can find time to test that on my end.  However, I know
nothing about Via XvMC (xvmc-vld), and I'm not sure how that relates
to that code at all.  Obviously I can't test that with an nVidia card.

Tom