From: Scott Theisen <scott.the.elm@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: [FFmpeg-devel] [PATCH] libavcodec/cuviddec.c: increase CUVID_DEFAULT_NUM_SURFACES Date: Thu, 20 Feb 2025 15:37:24 -0500 Message-ID: <20250220203733.165702-1-scott.the.elm@gmail.com> (raw) The default value of CuvidContext::nb_surfaces was reduced from 25 to 5 (as (CUVID_MAX_DISPLAY_DELAY + 1)) in 402d98c9d467dff6931d906ebb732b9a00334e0b. In cuvid_is_buffer_full() delay can be 2 * CUVID_MAX_DISPLAY_DELAY with double rate deinterlacing. ctx->nb_surfaces is CUVID_DEFAULT_NUM_SURFACES = (CUVID_MAX_DISPLAY_DELAY + 1) by default, in which case cuvid_is_buffer_full() will always return true and cuvid_output_frame() will never read any data since it will not call ff_decode_get_packet(). --- I think part of the problem might be that cuvid_is_buffer_full() does not know how many frames are actually in the driver's queue and assumes it is the maximum, even if none have yet been added. This was preventing any frames from being decoded using NVDEC with MythTV for some streams. See https://github.com/MythTV/mythtv/issues/1039 --- libavcodec/cuviddec.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavcodec/cuviddec.c b/libavcodec/cuviddec.c index 67076a1752..05dcafab6e 100644 --- a/libavcodec/cuviddec.c +++ b/libavcodec/cuviddec.c @@ -120,7 +120,7 @@ typedef struct CuvidParsedFrame #define CUVID_MAX_DISPLAY_DELAY (4) // Actual pool size will be determined by parser. -#define CUVID_DEFAULT_NUM_SURFACES (CUVID_MAX_DISPLAY_DELAY + 1) +#define CUVID_DEFAULT_NUM_SURFACES ((2 * CUVID_MAX_DISPLAY_DELAY) + 1) static int CUDAAPI cuvid_handle_video_sequence(void *opaque, CUVIDEOFORMAT* format) { -- 2.43.0 _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next reply other threads:[~2025-02-20 20:37 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-02-20 20:37 Scott Theisen [this message] 2025-02-21 13:26 ` Timo Rothenpieler 2025-02-22 2:52 ` Scott Theisen 2025-02-22 13:16 ` Timo Rothenpieler
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20250220203733.165702-1-scott.the.elm@gmail.com \ --to=scott.the.elm@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git