From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH 6/6] avcodec/h264dec: Support skipping frames that used gray gap frames Date: Tue, 21 Nov 2023 09:28:25 -0300 Message-ID: <b1dae01f-868f-4213-ae20-1f8752ff2e41@gmail.com> (raw) In-Reply-To: <20231114172051.13872-6-michael@niedermayer.cc> On 11/14/2023 2:20 PM, Michael Niedermayer wrote: > Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> > --- > libavcodec/h264dec.c | 7 +++++++ > libavcodec/h264dec.h | 1 + > 2 files changed, 8 insertions(+) > > diff --git a/libavcodec/h264dec.c b/libavcodec/h264dec.c > index b48821db244..aa0022a3aba 100644 > --- a/libavcodec/h264dec.c > +++ b/libavcodec/h264dec.c > @@ -939,6 +939,12 @@ static int finalize_frame(H264Context *h, AVFrame *dst, H264Picture *out, int *g > (h->avctx->flags2 & AV_CODEC_FLAG2_SHOW_ALL) || > out->recovered)) { > > + if (h->skip_gray > 0 && > + h->non_gray && out->gray && > + !(h->avctx->flags2 & AV_CODEC_FLAG2_SHOW_ALL) > + ) > + return 0; > + > if (!h->avctx->hwaccel && > (out->field_poc[0] == INT_MAX || > out->field_poc[1] == INT_MAX) > @@ -1091,6 +1097,7 @@ static const AVOption h264_options[] = { > { "nal_length_size", "nal_length_size", OFFSET(nal_length_size), AV_OPT_TYPE_INT, {.i64 = 0}, 0, 4, VDX }, > { "enable_er", "Enable error resilience on damaged frames (unsafe)", OFFSET(enable_er), AV_OPT_TYPE_BOOL, { .i64 = -1 }, -1, 1, VD }, > { "x264_build", "Assume this x264 version if no x264 version found in any SEI", OFFSET(x264_build), AV_OPT_TYPE_INT, {.i64 = -1}, -1, INT_MAX, VD }, > + { "skip_gray", "Do not return gray gap frames", OFFSET(skip_gray), AV_OPT_TYPE_INT, {.i64 = -1}, -1, 1, VD }, Same here. > { "noref_gray", "Avoid using gray gap frames as references", OFFSET(noref_gray), AV_OPT_TYPE_INT, {.i64 = 1}, -1, 1, VD }, > { NULL }, > }; > diff --git a/libavcodec/h264dec.h b/libavcodec/h264dec.h > index 591769ab258..447c2499d97 100644 > --- a/libavcodec/h264dec.h > +++ b/libavcodec/h264dec.h > @@ -572,6 +572,7 @@ typedef struct H264Context { > > int non_gray; ///< Did we encounter a intra frame after a gray gap frame > int noref_gray; > + int skip_gray; > } H264Context; > > extern const uint16_t ff_h264_mb_sizes[4]; _______________________________________________ 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".
prev parent reply other threads:[~2023-11-21 12:28 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-14 17:20 [FFmpeg-devel] [PATCH 1/6] avcodec/h264: Seperate SEI and IDR recovery handling Michael Niedermayer 2023-11-14 17:20 ` [FFmpeg-devel] [PATCH 2/6] avcodec/h264: Use FRAME_RECOVERED_HEURISTIC instead of IDR/SEI Michael Niedermayer 2023-11-14 17:20 ` [FFmpeg-devel] [PATCH 3/6] avcodec/h264dec: More elaborate documentation for frame_recovered Michael Niedermayer 2023-11-14 17:20 ` [FFmpeg-devel] [PATCH 4/6] avcodec/h264: keep track of which frames used gray references Michael Niedermayer 2023-11-14 17:32 ` Hendrik Leppkes 2023-11-14 18:46 ` Michael Niedermayer 2023-11-20 0:11 ` Michael Niedermayer 2023-11-20 3:01 ` Vittorio Giovara 2023-11-20 23:53 ` Michael Niedermayer 2023-11-14 17:20 ` [FFmpeg-devel] [PATCH 5/6] avcodec/h264: Avoid using gray gap frames as references Michael Niedermayer 2023-11-21 12:27 ` James Almer 2023-11-22 0:09 ` Michael Niedermayer 2023-11-14 17:20 ` [FFmpeg-devel] [PATCH 6/6] avcodec/h264dec: Support skipping frames that used gray gap frames Michael Niedermayer 2023-11-21 12:28 ` James Almer [this message]
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=b1dae01f-868f-4213-ae20-1f8752ff2e41@gmail.com \ --to=jamrial@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