Carl Eugen Hoyos
I added logs and explanation in tichet #7565.
Thank you in advance.
ponpon
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>Please avoid top-posting here,
Thannk you for your advice. I'll take care.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
2018-11-28 7:52 GMT+01:00, pon pon :
> I have attached logs in tichet #7565.
No...
Please avoid top-posting here, Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
I have attached logs in tichet #7565.
idet before patch (72.6x) is far faster than after (62.2x).
I think it means processes terminate by double counts than expeccted.
How do you thinnk about it?
ponpon
2018年11月28日(水) 11:24 Carl Eugen Hoyos :
> 2018-11-28 3:01 GMT+01:00, pon pon :
>
> > I think
2018-11-28 3:01 GMT+01:00, pon pon :
> I think idet duplicately counts and offsets accuracy of progressive
> frames, as repoert in ticket #7565.
Unfortunately, this ticket is missing all necessary information including
the command line, the complete, uncut console output and a sample file.
For
Hello,
I think idet duplicately counts and offsets accuracy of progressive frames,
as repoert in ticket #7565.
If this is corret, the below patch can fix it.
ponpon
diff --git a/libavfilter/vf_idet.c b/libavfilter/vf_idet.c
index 02ae2edcb9..8c355ee2f9 100644
--- a/libavfilter/vf_idet.c
+++
