- 26 Sep, 2019 1 commit
-
-
Ting Fu authored
Signed-off-by:
Ting Fu <ting.fu@intel.com> Signed-off-by:
Ruiling Song <ruiling.song@intel.com>
-
- 20 Sep, 2019 1 commit
-
-
Guo, Yejun authored
Signed-off-by:
Guo, Yejun <yejun.guo@intel.com> Signed-off-by:
Pedro Arthur <bygrandao@gmail.com>
-
- 19 Sep, 2019 2 commits
-
-
Guo, Yejun authored
'make fate-dnn-layer-depth2space' to run the test Signed-off-by:
Guo, Yejun <yejun.guo@intel.com> Signed-off-by:
Pedro Arthur <bygrandao@gmail.com>
-
Guo, Yejun authored
'make fate-dnn-layer-conv2d' to run the test Signed-off-by:
Guo, Yejun <yejun.guo@intel.com> Signed-off-by:
Pedro Arthur <bygrandao@gmail.com>
-
- 11 Sep, 2019 1 commit
-
-
Lynne authored
-
- 08 Sep, 2019 1 commit
-
-
Calvin Walton authored
Right now, the concat filter does not set the frame_rate value on any of the out links. As a result, the default ffmpeg behaviour kicks in - to copy the framerate from the first input to the outputs. If a later input is higher framerate, this results in dropped frames; if a later input is lower framerate it might cause judder. This patch checks if all of the video inputs have the same framerate, and if not it sets the out link to use '1/0' as the frame rate, the value meaning "unknown/vfr". A test is added to verify the VFR behaviour. The existing test for CFR behaviour passes unchanged.
-
- 05 Sep, 2019 1 commit
-
-
Gyan Doshi authored
Checks that seek to start indeed seeks to start.
-
- 24 Aug, 2019 1 commit
-
-
Thilo Borgmann authored
-
- 17 Aug, 2019 1 commit
-
-
Limin Wang authored
This fixes make fate issue for frame thread scale in my local testing Signed-off-by:
Limin Wang <lance.lmwang@gmail.com> Signed-off-by:
Marton Balint <cus@passwd.hu>
-
- 13 Aug, 2019 1 commit
-
-
Zhong Li authored
Reviewed-by:
Michael Niedermayer <michael@niedermayer.cc> Reviewed-by:
Thilo Borgmann <thilo.borgmann@mail.de> Signed-off-by:
Zhong Li <zhong.li@intel.com>
-
- 01 Aug, 2019 1 commit
-
-
Steven Liu authored
Signed-off-by:
Steven Liu <lq@chinaffmpeg.org>
-
- 29 Jul, 2019 1 commit
-
-
Guo, Yejun authored
'make fate-dnn-layer-pad' to run the test Signed-off-by:
Guo, Yejun <yejun.guo@intel.com> Signed-off-by:
Pedro Arthur <bygrandao@gmail.com>
-
- 22 Jul, 2019 1 commit
-
-
Limin Wang authored
why change .4 to .25, it's for: one scenecut(pkt_pts=20040) isn't detected by 0.4 threshold why not change to 0.3 instead of 0.25: it will miss the scenecut(pkt_pts=20040) after applying the next patch which enables yuvj420 for fate testing, it's better to catch all scenecut scenes. Reviewed-by:
Marton Balint <cus@passwd.hu> Signed-off-by:
Limin Wang <lance.lmwang@gmail.com>
-
- 15 Jul, 2019 1 commit
-
-
Steven Liu authored
Tested-by:
Michael Niedermayer <michael@niedermayer.cc> Signed-off-by:
Steven Liu <lq@chinaffmpeg.org>
-
- 11 Jul, 2019 2 commits
-
-
Steven Liu authored
Signed-off-by:
Steven Liu <lq@chinaffmpeg.org>
-
Steven Liu authored
Signed-off-by:
Steven Liu <lq@chinaffmpeg.org>
-
- 07 Jul, 2019 1 commit
-
-
Mark Thompson authored
Operates in the same way as the h264-levels test.
-
- 12 Jun, 2019 3 commits
-
-
Peter Ross authored
-
Michael Niedermayer authored
The tests previously rounded the timestamps. Its better in a fate test to preserve the data from the demuxer and decoder. Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
Ruiling Song authored
Signed-off-by:
Ruiling Song <ruiling.song@intel.com>
-
- 09 Jun, 2019 1 commit
-
-
Peter Ross authored
-
- 08 May, 2019 3 commits
-
-
Andreas Rheinhardt authored
Up until now, the length field of most level 1 elements has been written using eight bytes, although it is known in advance how much space the content of said elements will take up so that it would be possible to determine the minimal amount of bytes for the length field. This commit changes this. Signed-off-by:
Andreas Rheinhardt <andreas.rheinhardt@gmail.com> Signed-off-by:
James Almer <jamrial@gmail.com>
-
Andreas Rheinhardt authored
Given that in both the seekable as well as the non-seekable mode dynamic buffers are used to write level 1 elements and that now no seeks are used in the seekable case any more, the two modes can be combined; as a consequence, the non-seekable mode automatically inherits the ability to write CRC-32 elements. There are no differences in case the output is seekable; when it is not and writing CRC-32 elements is disabled, there can still be minor differences because before this commit, the EBML ID and length field were counted towards the cluster size limit; now they no longer are. Signed-off-by:
Andreas Rheinhardt <andreas.rheinhardt@gmail.com> Signed-off-by:
James Almer <jamrial@gmail.com>
-
Andreas Rheinhardt authored
Up until now the EBML Header length field has been written with eight bytes, although the EBML Header is always so small that only one byte is needed for it. This patch saves seven bytes for every Matroska/Webm file. Signed-off-by:
Andreas Rheinhardt <andreas.rheinhardt@gmail.com> Signed-off-by:
James Almer <jamrial@gmail.com>
-
- 03 May, 2019 1 commit
-
-
James Almer authored
Signed-off-by:
James Almer <jamrial@gmail.com>
-
- 19 Apr, 2019 1 commit
-
-
Hendrik Leppkes authored
The transcode() helper function will already prepend the TARGET_PATH to the sample path, if its a relative path. This avoids an issue on Windows, where the relative path check could fail.
-
- 18 Apr, 2019 2 commits
-
-
Carl Eugen Hoyos authored
Fixes fate in Windows subsystem for Linux.
-
Steven Liu authored
-
- 17 Apr, 2019 1 commit
-
-
Steven Liu authored
Signed-off-by:
Steven Liu <lq@chinaffmpeg.org>
-
- 05 Apr, 2019 1 commit
-
-
Derek Buitenhuis authored
This makes sure we don't regress on 70c8c8a8. Signed-off-by:
Derek Buitenhuis <derek.buitenhuis@gmail.com>
-
- 03 Apr, 2019 1 commit
-
-
Gyan Doshi authored
write_tmcd allows tmcd track to be created with any mode but in mov_write_header, index for first tmcd track is only set for modes MP4 or MOV, causing a crash if tmcd creation is attempted with other modes.
-
- 15 Mar, 2019 1 commit
-
-
Carl Eugen Hoyos authored
The file has to be created first, fixes fate without zlib.
-
- 14 Mar, 2019 2 commits
-
-
James Almer authored
Should fix fate failures on big endian targets. Signed-off-by:
James Almer <jamrial@gmail.com>
-
James Almer authored
-
- 13 Mar, 2019 1 commit
-
-
Mark Reid authored
Reviewed-by:
Tomas Härdin <tjoppen@acc.umu.se> Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 04 Mar, 2019 1 commit
-
-
Martin Vignali authored
-
- 27 Feb, 2019 1 commit
-
-
Martin Vignali authored
-
- 16 Feb, 2019 3 commits
-
-
Diego Biurrun authored
Rename a test in the process for consistency and simplicity and remove the remnants of the now-unused lavf regression test scripts.
-
Diego Biurrun authored
Rename some tests in the process for consistency and simplicity.
-
Diego Biurrun authored
Also split monolithic lavf-pixfmt test into individual tests.
-