aboutsummaryrefslogtreecommitdiffstats
path: root/libavcodec/ra288.c
diff options
context:
space:
mode:
authorSergey Svechnikov <svechnikov66@gmail.com>2019-04-22 22:26:24 +0500
committerTimo Rothenpieler <timo@rothenpieler.org>2019-04-23 12:59:44 +0200
commitfc630d7b437b754cc9d4a848d2b32b0ff8c1a7d7 (patch)
tree5545d058f1d937829059faabc37278d7252fc2b4 /libavcodec/ra288.c
parentee66e04bc9dbbcf95114a103f174ed54b2260758 (diff)
downloadffmpeg-fc630d7b437b754cc9d4a848d2b32b0ff8c1a7d7.tar.gz
avcodec/cuviddec: improve progressive frame detection
There are 2 types of problems when using adaptive deinterlace with cuvid: 1. Sometimes, in the middle of transcoding, cuvid outputs frames with visible horizontal lines (as though weave deinterlace method was chosen); 2. Occasionally, on scene changes, cuvid outputs a wrong frame, which should have been shown several seconds before (as if the frame was assigned some wrong PTS value). The reason is that sometimes CUVIDPARSERDISPINFO has property progressive_frame equal to 1 with interlaced videos. In order to fix the problem we should check if the video is interlaced or progressive in the beginning of a video sequence (cuvid_handle_video_sequence). And then we just use this information instead of the property progressive_frame in CUVIDPARSERDISPINFO (which is unreliable). Signed-off-by: Timo Rothenpieler <timo@rothenpieler.org>
Diffstat (limited to 'libavcodec/ra288.c')
0 files changed, 0 insertions, 0 deletions