From: Jun Zhao <mypopy@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Cc: Jun Zhao <barryjzhao@tencent.com>, Jun Zhao <mypopydev@gmail.com>
Subject: [FFmpeg-devel] [PATCH 1/4] lavc/vvc_parser: Remove max_b_frames setting
Date: Fri, 19 Apr 2024 21:47:08 +0800
Message-ID: <20240419134711.3824735-1-mypopy@gmail.com> (raw)
From: Jun Zhao <mypopydev@gmail.com>
We don't used the max_b_frames field in decoder normally
Signed-off-by: Jun Zhao <barryjzhao@tencent.com>
---
libavcodec/vvc_parser.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/libavcodec/vvc_parser.c b/libavcodec/vvc_parser.c
index e3501fa139..a0e10e1a7c 100644
--- a/libavcodec/vvc_parser.c
+++ b/libavcodec/vvc_parser.c
@@ -187,7 +187,6 @@ static void set_parser_ctx(AVCodecParserContext *s, AVCodecContext *avctx,
avctx->has_b_frames = (sps->sps_max_sublayers_minus1 + 1) > 2 ? 2 :
sps->sps_max_sublayers_minus1;
- avctx->max_b_frames = sps->sps_max_sublayers_minus1;
if (sps->sps_ptl_dpb_hrd_params_present_flag &&
sps->sps_timing_hrd_params_present_flag) {
--
2.25.1
_______________________________________________
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:[~2024-04-19 13:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 13:47 Jun Zhao [this message]
2024-04-19 13:47 ` [FFmpeg-devel] [PATCH 2/4] lavc/libxevd: Fixed the has_b_frames setting Jun Zhao
2024-04-19 13:47 ` [FFmpeg-devel] [PATCH 3/4] lavc/vvc_parser: " Jun Zhao
2024-04-20 3:49 ` Nuo Mi
2024-04-21 2:51 ` mypopy
2024-04-21 13:12 ` Nuo Mi
2024-04-19 13:47 ` [FFmpeg-devel] [PATCH 4/4] lavc/vvc/refs: Use dpb_max_num_reorder_pics to control output Jun Zhao
2024-04-20 3:48 ` Nuo Mi
2024-04-21 2:33 ` mypopy
2024-04-21 13:14 ` Nuo Mi
2024-04-20 3:51 ` [FFmpeg-devel] [PATCH 1/4] lavc/vvc_parser: Remove max_b_frames setting Nuo Mi
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=20240419134711.3824735-1-mypopy@gmail.com \
--to=mypopy@gmail.com \
--cc=barryjzhao@tencent.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=mypopydev@gmail.com \
/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