Re: [mpeg2-dev] why de-interlace so slow(sawtooth obvious)?

[Keith W. <ke...@MI...>]

Allison,

On Wed, 9 May 2007, hdzhne wrote:

> Is "info->display_fbuf->buf" one field or one frame data (my mpeg2=20
> source is interlaced)?

I think it's always a frame. (Not 100% sure in the case of field pictures,=
=20
but nobody seems to use those. I think it's still a frame even when field=
=20
pictures are used, in any event.)

> If I want to do de-interlace before display , may I process=20
> info->display_fbuf->buf directly?

Sure. Keep in mind that buf[] is an array of three framebuffers -- Y, Cb,=
=20
and Cr -- and those will be different sizes. E.g. Y could be 1280x720 and=
=20
Cb and Cr will be 640x360.

Cheers,
Keith

> Best,
>
> allison
>
>
>
> =3D=3D=3D=3D=3D=3D=3D 2007-05-08 13:09:18 =A3=BA=3D=3D=3D=3D=3D=3D=3D
>
>> Allison,
>>
>> I don't understand exactly what you mean by "SD DV mpeg2 data". DV (aka,
>> MiniDV) is a different format that does not use MPEG-2.
>>
>> Assuming you're just referring to interlaced content, there is no perfec=
t
>> way to display interlaced material on a progressive display like a
>> computer monitor.
>>
>> Some deinterlacing techniques include "bobbing" (meaning doubling each
>> line in a field) and "weaving" (meaning displaying each frame as a unit,
>> with separate fields woven together).
>>
>> libmpeg2 does not implement any deinterlacing techniques. It _only_
>> performs the MPEG-2 decoding process. The display process is up to the
>> application that harnesses libmpeg2.
>>
>> Some of the applications that can use libmpeg2, and do implement various
>> deinterlacing methods, include mplayer, xine, and vlc. If you want
>> good-looking results, you should either implement deinterlacing or use o=
ne
>> of those applications. libmpeg2 does not do this.
>>
>> Best regards,
>> Keith
>>
>> On Tue, 8 May 2007, hdzhne wrote:
>>
>>> hi,
>>>
>>>    When I use mpeg2lib to decoder SD DV data, I can see sawtooth clear
>>> when there is quick moving in picture.
>>>
>>> I think it because just deinterlacing is too slow or meet some wrong. P=
C
>>> I used is high performance PC, and can decoder SD DV mpeg2 data about
>>> more than 30fps.
>>>
>>>
>>>
>>> =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1hdzhne
>>> =A1=...@12...
>>> =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A12007-05-08
>>>
>>>
>
> =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D
>
>
> =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=D6=C2
> =C0=F1=A3=A1
>
>
> =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1hdzhne
> =A1=...@12...
> =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A12007-05-09
>
>