#11514: Cuvid decoder problem with deinterlacing
---------------------------------+--------------------------------------
             Reporter:  ua0lnj   |                     Type:  defect
               Status:  new      |                 Priority:  normal
            Component:  avcodec  |                  Version:  git-master
             Keywords:  cuvid    |               Blocked By:
             Blocking:           |  Reproduced by developer:  0
Analyzed by developer:  0        |
---------------------------------+--------------------------------------
 Summary of the bug:
 After commit 99e2af4
 
https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/99e2af4e7837ca09b97d93a562dc12947179fc48
 I have frame jerking with vdr-plugin-softhddevice and vdr-plugin-
 softhdcuvid.(https://github.com/ua0lnj/vdr-plugin-softhddevice,
 https://github.com/jojo61/vdr-plugin-softhdcuvid), with interlaced video
 and cuvid deinterlace bob or adaptive. No errors in libavcodec debug log.
 But ffplay works without problems: DISPLAY=:0 ffplay -x 1920 -y 1080
 -vcodec h264_cuvid -deint 2 -drop_second_field 0 -v debug ./00001.ts

 The only difference i found in the logs:
 ffplay:
 [h264_cuvid @ 0x7139edffb2c0] Format nv12 chosen by get_format().
 [h264_cuvid @ 0x7139edffb2c0] Formats: Original: nv12 | HW: nv12 | SW:
 nv12

 softhddevice:
 [h264_cuvid @ 0x7a36343b0900] Format cuda chosen by get_format().
 [h264_cuvid @ 0x7a36343b0900] Formats: Original: nv12 | HW: cuda | SW:
 nv12

 How to reproduce:
 ffmpeg version latest from git, Nvidia driver 570, Ubuntu 24.04.
 vdr with vdr-plugin-softhddevice, -v cuvid.

 I know about nvdec and softhddevice supports it too, here we are talking
 about cuvid.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/11514>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Reply via email to