From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/hevc_sei: Fix check for SEI end
Date: Fri, 24 Jun 2022 11:53:44 +0200
Message-ID: <DB6PR0101MB22144410914491047C3595B38FB49@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <DB6PR0101MB2214AB938D29E67A59B9D1258FB29@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com>
Andreas Rheinhardt:
> The intention behind the current check seems to be to check for
> the rbsp_trailing_bits() syntax structure which is always 0x80
> for valid SEI messages. Yet this is wrong: These trailing bits
> are not part of the GetBitContext -- they have already been
> stripped in ff_h2645_packet_split(). And it is harmful, as
> 0x80 is a legal SEI message payload type (namely for
> Structure of pictures information SEI messages). We ignore this
> type of SEI, but because of this bug we also ignored every
> SEI message in the same NALU following it.
>
> Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
> ---
> libavcodec/hevc_sei.c | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/libavcodec/hevc_sei.c b/libavcodec/hevc_sei.c
> index a5c7df34b0..953633f4bd 100644
> --- a/libavcodec/hevc_sei.c
> +++ b/libavcodec/hevc_sei.c
> @@ -549,12 +549,6 @@ static int decode_nal_sei_message(GetByteContext *gb, void *logctx, HEVCSEI *s,
> }
> }
>
> -static int more_rbsp_data(GetByteContext *gb)
> -{
> - return bytestream2_get_bytes_left(gb) > 0 &&
> - bytestream2_peek_byteu(gb) != 0x80;
> -}
> -
> int ff_hevc_decode_nal_sei(GetBitContext *gb, void *logctx, HEVCSEI *s,
> const HEVCParamSets *ps, int type)
> {
> @@ -569,7 +563,7 @@ int ff_hevc_decode_nal_sei(GetBitContext *gb, void *logctx, HEVCSEI *s,
> ret = decode_nal_sei_message(&gbyte, logctx, s, ps, type);
> if (ret < 0)
> return ret;
> - } while (more_rbsp_data(&gbyte));
> + } while (bytestream2_get_bytes_left(&gbyte) > 0);
> return 1;
> }
>
Will apply this tonight unless there are objections.
- Andreas
_______________________________________________
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:[~2022-06-24 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 11:26 Andreas Rheinhardt
2022-06-24 9:53 ` Andreas Rheinhardt [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=DB6PR0101MB22144410914491047C3595B38FB49@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com \
--to=andreas.rheinhardt@outlook.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