[FFmpeg-devel] [PATCH 24/24] lavfi/vf_scale: implement slice threading

[Michael Niedermayer]

On Mon, Jul 12, 2021 at 12:34:55PM +0200, Anton Khirnov wrote:
> Quoting Michael Niedermayer (2021-07-03 18:27:36)
> > On Sat, Jul 03, 2021 at 03:27:36PM +0200, Anton Khirnov wrote:
> > > Quoting Michael Niedermayer (2021-06-01 11:35:13)
> > > > On Mon, May 31, 2021 at 09:55:15AM +0200, Anton Khirnov wrote:
> > > > > ---
> > > > >  libavfilter/vf_scale.c | 182 +++++++++++++++++++++++++++++++----------
> > > > >  1 file changed, 141 insertions(+), 41 deletions(-)
> > > > 
> > > > breaks: (lower 50% is bright green)
> > > > ./ffplay -i mm-short.mpg -an   -vf "tinterlace,scale=720:576:interl=1"
> > > 
> > > Fixed locally, but I'm wondering why is interlaced scaling not done by
> > > default for interlaced videos.
> > 
> > IIRC the flags where quite unreliable. If we have reliable knowledge about
> > interlacing it certainly should be used automatically
> 
> You mean there is a significant amount of progressive content that is
> flagged as interlaced?

Yes, thats from my memory though, this may have changed of course.
IIRC one source of this is progressive material intended for interlaced
displays

Most ideally IMHO we should reliably autodetect the material 
progressive/interlaced/telecined set the flags accordingly and then also
automatically optimally do what the flags say without user intervention.

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

If a bugfix only changes things apparently unrelated to the bug with no
further explanation, that is a good sign that the bugfix is wrong.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20210712/51f63689/attachment.sig>