24.08.2021, 19:31
(24.08.2021, 16:58)Selur Wrote: You could test:
1. Will the output differ if I use:
or-c:v h264_cuvid -crop 16,16,16,16 -resize 1280x720
and what resolution does the output have for these.-c:v h264_cuvid -resize 1280x720 -crop 16,16,16,16
2. Does crop properly work on interlaced content that isn't deinterlaced but again encoded to interlaced output?
3. Does crop need mod4 bottom and top crop values on YUV420 content if the input is interlaced and not deinterlacing is used?
4. Does crop need mod4 bottom and top crop values on YUV420 content if the input is interlaced and deinterlacing is used?
5. Does crop need mod2 crop values if the input is yuv420?
6. Will I get different output if '-resize', '-crop' ´, '-deint' are all used but their order differs? (related to the first question)
7. Does cuvid properly work when used with nvenc based encoders?
Can be done, but will take time.
The video of how the bug is triggered: https://drive.google.com/file/d/1tWwvd7m...J__sF/view
- Import an mpeg2 video, select CUVID as deinterlacer, save the configuration.
- Import an avc video, restore saved configuration.
- Decoder should be mpeg2_cuvid.