summaryrefslogtreecommitdiffstats
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* aarch64: Add cpu flags for the dotprod and i8mm extensionsMartin Storsjö2023-06-061-0/+2
| | | | | | | Set these available if they are available unconditionally for the compiler. Signed-off-by: Martin Storsjö <[email protected]>
* fftools/ffmpeg_enc: avoid breaking exactly integer timestamps in vsync codeAnton Khirnov2023-06-054-4/+4
| | | | | | | | The code will currently add a small offset to avoid exact midpoints, but this can cause inexact results when a float timestamp is exactly representable as an integer. Fixes off-by-one in the first frame duration in multiple FATE tests.
* tests/fate/ffmpeg: add tests for -max_error_rateAnton Khirnov2023-06-053-0/+6
|
* av1dec: add Vulkan hwaccelLynne2023-05-291-0/+2
|
* fate-source: exclude Apache-2 licensed filesLynne2023-05-291-0/+1
|
* lsws: add in/out support for the new 12-bit 2-plane 422 and 444 pixfmtsLynne2023-05-2916-0/+70
|
* lavu: add 12-bit 2-plane 422 and 444 pixel formatsLynne2023-05-291-0/+4
|
* avfilter/af_silenceremove: add real peak detectorPaul B Mahol2023-05-261-1/+1
| | | | Rename old peak detector to more correct name one.
* avformat/gifdec: switch to using gif parserPaul B Mahol2023-05-251-1/+1
| | | | Update fate test, more correct as last packet is not truncated.
* fate/tests/ffmpeg: use -idct simple for fate-ffmpeg-input-rAnton Khirnov2023-05-231-1/+1
| | | | Makes the test bitexact on non-x86_64.
* tests/fate/ffmpeg: add a test for input -r optionAnton Khirnov2023-05-222-0/+16
|
* tests/fate/ffmpeg: move a misplaced lineAnton Khirnov2023-05-221-2/+1
|
* fate/checkasm: add h264chroma testJames Almer2023-05-201-0/+1
| | | | Signed-off-by: James Almer <[email protected]>
* checkasm: add h264chroma testsLynne2023-05-204-0/+90
| | | | Checks all variants of put_h264_chroma and avg_h264_chroma.
* fate/demux: fix fate-cavs-demuxJames Almer2023-05-202-2/+2
| | | | Signed-off-by: James Almer <[email protected]>
* avcodec/cavs_parser: fix finding the end of a frameZhao Zhili2023-05-202-0/+65
| | | | | | | | | | Use the next I/P/B or start code as the end of current frame. Before the patch, extension start code, user data start code, sequence end code and so on are treated as the start of next frame. Signed-off-by: Zhao Zhili <[email protected]>
* fate/jpg: add RGB mjpeg fate testsLeo Izen2023-05-176-0/+41
| | | | | Adds FATE tests for RGB jpegs to test commit 0b352e350e773673f11ea380f3507923c70e1175.
* tests/fate: add a simple test for libx264Anton Khirnov2023-05-154-0/+108
| | | | | | | | Since this is an external encoder not under our control, we cannot test the encoded output exactly as is done for internal encoders. We can still test however that the output is decodable and produces the expected number of frames with expected dimensions, pixel formats, and timestamps.
* avformat/tests/imf: add invalid resource testPierre-Anthony Lemieux2023-05-111-0/+2
|
* fftools/ffprobe: print exported stream AVOptionsJames Almer2023-05-084-7/+7
| | | | | | | Similar to the decoder AVOptions, this is useful to show values from options exported by the demuxer. Signed-off-by: James Almer <[email protected]>
* fftools/ffmpeg: always use the same path for setting InputStream.[next_]dtsAnton Khirnov2023-05-022-28/+28
| | | | | | | | | | | | | | | | | | | | | Currently those are set in different ways depending on whether the stream is decoded or not, using some values from the decoder if it is. This is wrong, because there may be arbitrary amount of delay between input packets and output frames (depending e.g. on the thread count when frame threading is used). Always use the path that was previously used only for streamcopy. This should not cause any issues, because these values are now used only for streamcopy and discontinuity handling. This change will allow to decouple discontinuity processing from decoding and move it to ffmpeg_demux. It also makes the code simpler. Changes output in fate-cover-art-aiff-id3v2-remux and fate-cover-art-mp3-id3v2-remux, where attached pictures are now written in the correct order. This happens because InputStream.dts is no longer reset to AV_NOPTS_VALUE after decoding, so streamcopy actually sees valid dts values.
* fftools/ffmpeg: rework audio-decode timestamp handlingAnton Khirnov2023-05-023-334/+334
| | | | | | | | | | | | | | | | | | | | | Stop using InputStream.dts for generating missing timestamps for decoded frames, because it contains pre-decoding timestamps and there may be arbitrary amount of delay between input packets and output frames (e.g. dependent on the thread count when frame threading is used). It is also in AV_TIME_BASE (i.e. microseconds), which may introduce unnecessary rounding issues. New code maintains a timebase that is the inverse of the LCM of all the samplerates seen so far, and thus can accurately represent every audio sample. This timebase is used to generate missing timestamps after decoding. Changes the result of the following FATE tests * pcm_dvd-16-5.1-96000 * lavf-smjpeg * adpcm-ima-smjpeg In all of these the timestamps now better correspond to actual frame durations.
* lavf/dv: use a more granular timebase for audioAnton Khirnov2023-05-021-8/+8
| | | | | | | | | | | | | One that is fine enough to represent all DV audio sample rates. Audio packet durations are now sample-accurate. This largely undoes commit 76fbb0052df471075858c1cb82b04c8be7adba8d. To avoid breaking the issue fixed by that commit, resync audio timestamps against video if they get more than one frame apart. The sample from issue #8762 still works correctly after this commit. Slightly changes the results of the lavf-dv seektest, due to the audio timebase being more granular.
* lavf/dv: do not set video timebase more than onceAnton Khirnov2023-05-024-44/+44
| | | | | | | | | | | | | Current code will call avpriv_set_pts_info() for each video frame, possibly setting a different timebase if the stream framerate changes. This violates API conventions, as the timebase is supposed to stay constant after stream creation. Change the demuxer to set a single timebase that is fine enough to handle all supported DV framerates. The seek tests change slightly because the new timebase is more granular.
* lavf/dauddec: set timebase to 1/samplerateAnton Khirnov2023-04-282-18/+18
| | | | | Prevents lavf from generating inexact timestamps with the default timebase of 1/90000.
* lavfi/dnn: Remove DNN native backendTing Fu2023-04-282-46/+0
| | | | | | | | | | According to discussion in https://etherpad.mit.edu/p/FF_dev_meeting_20221202 and the proposal in http://ffmpeg.org/pipermail/ffmpeg-devel/2022-December/304534.html, the DNN native backend should be removed at first step. All the DNN native backend related codes are deleted. Signed-off-by: Ting Fu <[email protected]>
* tests: do not override movflags defaultsMarton Balint2023-04-242-2/+2
| | | | | | It does not matter if the default is 0, but still it is cleaner that way. Signed-off-by: Marton Balint <[email protected]>
* fftools/ffmpeg_enc: always use video frame durations when availableAnton Khirnov2023-04-244-71/+71
| | | | | | | | | Previously they would only be used with trivial filtergraphs, because filters did not handle frame durations. That is no longer true - most filters process frame durations properly (there may still be some that don't - this change will help finding and fixing them). Improves output video frame durations in a number of FATE tests.
* fate/jpeg2000: add missing dependecy checksJames Almer2023-04-231-3/+5
| | | | Signed-off-by: James Almer <[email protected]>
* fate/jpeg2000: add JPEG 2000 tests using ITU/ISO conformance materialsPierre-Anthony Lemieux2023-04-2216-0/+149
| | | | | | | | | Adds JPEG 2000 decoder tests using materials from the conformance suite specified in Rec. ITU-T T.803 | ISO/IEC 15444-4. The test materials are available at https://gitlab.com/wg1/htj2k-codestreams Signed-off-by: Pierre-Anthony Lemieux <[email protected]>
* fate/h264: test disabling croppingJames Almer2023-04-222-1/+291
| | | | Signed-off-by: James Almer <[email protected]>
* fate: add tests for RGB jpegsLeo Izen2023-04-214-0/+27
| | | | | Added framecrc tests for RGB JPEGs to verify future changes to the decoder.
* fate/png-icc-parse: update ref dataSteven Liu2023-04-211-12/+5
| | | | | | | | | | When enable lcms2, the fate-png-icc-parse will get error bellow. TEST png-icc-parse This because updated how PNG handles colors (no longer using mastering display metadata for that). Reviewed-by: Leo Izen <[email protected]> Signed-off-by: Steven Liu <[email protected]>
* fftools/ffmpeg: propagate frame durations to packets when encodingAnton Khirnov2023-04-1919-133/+133
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove now-obsolete code setting packet durations pre-muxing for CFR encoded video. Changes output in the following FATE tests: * numerous adpcm tests * ffmpeg-filter_complex_audio * lavf-asf * lavf-mkv * lavf-mkv_attachment * matroska-encoding-delay All of these change due to the fact that the output duration is now the actual input data duration and does not include padding added by the encoder. * apng-osample: less wrong packet durations are now passed to the muxer. They are not entirely correct, because the first frame duration should be 3 rather than 2. This is caused by the vsync code and should be addressed later, but this change is a step in the right direction. * tscc2-mov: last output frame has a duration of 11 rather than 1 - this corresponds to the duration actually returned by the demuxer. * film-cvid: video frame durations are now 2 rather than 1 - this corresponds to durations actually returned by the demuxer and matches the timestamps. * mpeg2-ticket6677: durations of some video frames are now 2 rather than 1 - this matches the timestamps.
* fftools/ffmpeg: stop using fake dts for generating timestampsAnton Khirnov2023-04-1353-3474/+3474
| | | | | | | | | | | | | When no packet dts values are available from the container, video decoding code will currently use its own guessed values, which will then be propagated to pkt_dts on decoded frames and used as pts in certain cases. This is inaccurate, fragile, and unnecessarily convoluted. Simply removing this allows the extrapolation code introduced in the previous commit to do a better job. Changes the results of numerous h264 and hevc FATE tests, where no spurious timestamp gaps are generated anymore. Several tests no longer need -vsync passthrough.
* fftools/ffmpeg: change video decoding timestamp generationAnton Khirnov2023-04-134-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | When no timestamps are available from the container, the video decoding code will currently use fake dts values - generated in process_input_packet() based on a combination of information from the decoder and the parser (obtained via the demuxer) - to generate timestamps during decoder flushing. This is fragile, hard to follow, and unnecessarily convoluted, since more reliable information can be obtained directly from post-decoding values. The new code keeps track of the last decoded frame pts and estimates its duration based on a number of heuristics. Timestamps generated when both pts and pkt_dts are missing are then simple pts+duration of the last frame. The heuristics are somewhat complicated by the fact that lavf insists on making up packet timestamps based on its highly incomplete information. That should be removed in the future, allowing to further simplify this code. The results of the following tests change: * h264-3386 now requires -fps_mode passthrough to avoid dropping frames at the end; this is a pathology of the interaction of the new and old code, and the fact that the sample switches from field to frame coding in the last packet, and will be fixed in following commits * hevc-conformance-DELTAQP_A_BRCM_4 stops inventing an arbitrary timestamp gap at the end * hevc-small422chroma - the single frame output by this test now has a timestamp of 0, rather than an arbitrary 7
* lavf/rawdec: mark raw demuxers as having no timestampsAnton Khirnov2023-04-131-1/+1
| | | | | | Changes the result of the h264_redundant_pps-mov test, where the output timebase is now 1001/24000 instead of 1/24. This is more correct, as the source file actually is 23.98fps.
* lavf/rawdec: set avg_frame_rateAnton Khirnov2023-04-137-33/+33
| | | | | | | | | | | | Timestamps in two FATE H.264 conformance tests now start at 1 instead of 0, which also happens in some other H.264 tests before this commit and so is not a big issue. Conversely, timestamps in some HEVC conformance tests start from a smaller value now. Ideally this should be addressed later in a more general way. h264-conformance-frext-frext2_panasonic_b no longer requires -vsync passthrough.
* checkasm: pass context as pointerxufuji4562023-04-136-39/+39
| | | | | Signed-off-by: xufuji456 <[email protected]> Signed-off-by: Martin Storsjö <[email protected]>
* checkasm/hevc: add transform_luma testxufuji4562023-04-131-0/+29
| | | | | Signed-off-by: xufuji456 <[email protected]> Signed-off-by: Martin Storsjö <[email protected]>
* fftools/sync_queue: make sure audio duration matches sample countAnton Khirnov2023-04-091-1/+0
| | | | | | | | | For audio AVFrames, nb_samples is typically more trustworthy than duration. Since sync queues look at durations, make sure they match the sample count. The last audio frame in the fate-shortest test is now gone. This is more correct, since it outlasts the last video frame.
* fate/matroska: add HDR10+ muxing testsJames Almer2023-04-083-0/+134
| | | | Signed-off-by: James Almer <[email protected]>
* avformat/matroskaenc: support writing Dynamic HDR10+ packet side dataJames Almer2023-04-0827-85/+85
| | | | Signed-off-by: James Almer <[email protected]>
* checkasm: add hevc_deblock chroma testJ. Dekker2023-04-065-1/+105
| | | | Signed-off-by: J. Dekker <[email protected]>
* tests/fate/vcodec.mak: drop strict experimental from j2k testsMichael Niedermayer2023-04-061-4/+4
| | | | Signed-off-by: Michael Niedermayer <[email protected]>
* fate: split mxf test dependencies to DV and MPEG2Marton Balint2023-04-061-1/+2
| | | | Signed-off-by: Marton Balint <[email protected]>
* avformat/matroskaenc: write a MaxBlockAdditionID elementJames Almer2023-04-0527-85/+85
| | | | | | A non zero value is mandatory for Matroska if the track has blocks with BlockAdditions. Signed-off-by: James Almer <[email protected]>
* tests: Add more j2k tests to cover a wider range of casesMichael Niedermayer2023-04-029-1/+35
| | | | Signed-off-by: Michael Niedermayer <[email protected]>
* avcodec/j2kenc: Fix funky bpno errors on decodingMichael Niedermayer2023-04-027-14/+14
| | | | Signed-off-by: Michael Niedermayer <[email protected]>
* fate/lavf-container: add missing swscale deps to mxf_dvcpro100 and mxf_ffv1James Almer2023-03-281-2/+2
| | | | Signed-off-by: James Almer <[email protected]>
generated by cgit v1.2.3 (git 2.25.1) at 2025-09-23 10:19:28 +0000