On 2017/8/4 5:32, Maxym Dmytrychenko wrote:
ok, it seems that ./configure related deps change are missing.
as you did for overlay:
_filter_deps=
_filter_select=
yes, this is a very serious bug. Thank you. I will fix this and send out
the V2.
On Tue, Aug 1, 2017 at 7:58 AM, Huang, Zhengxu
<[email protected] <mailto:[email protected]>> wrote:
On 2017/8/1 3:22, Maxym Dmytrychenko wrote:
LGTM, seems to be working just fine
Performance will be significantly reduced
if there are performance numbers showing this statement - would be good to
share it.
The performance comparison between the cascade mode and union mode
is blew:
As the Libav now only has scale_qsv /interlace_qsv two qsv filters
and the deinterlace module still has some bug.
So we use our common filter module to simulate. Though the code is
different but the result is nearly the same(once we
make the validation on our patches that
framerate/denoise/deinterlace/detail/scale filter module are
independent).
There are only three filters in the test case but the performance
has significantly reduced. The more filters in the cascade system
the more drop on the performance compared with the union mode.
On Mon, Jul 31, 2017 at 1:43 PM, Luca Barbato<[email protected]>
<mailto:[email protected]> wrote:
On 31/07/2017 03:27, Huang, Zhengxu wrote:
Looks good after a first read, I still need to try it.
Thank you a lot :)
lu
_______________________________________________
libav-devel mailing list
[email protected] <mailto:[email protected]>
https://lists.libav.org/mailman/listinfo/libav-devel
<https://lists.libav.org/mailman/listinfo/libav-devel>
_______________________________________________
libav-devel mailing list
[email protected] <mailto:[email protected]>
https://lists.libav.org/mailman/listinfo/libav-devel
<https://lists.libav.org/mailman/listinfo/libav-devel>
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
