From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v20 02/10] avcodec/evc_parser: Added parser implementation for EVC format
Date: Wed, 19 Apr 2023 10:12:16 -0300
Message-ID: <3f225c34-f8fb-2a7e-bf29-cc5d0660dc9d@gmail.com> (raw)
In-Reply-To: <20230418103012.714-1-d.kozinski@samsung.com>
On 4/18/2023 7:30 AM, Dawid Kozinski wrote:
> static EVCParserSliceHeader *parse_slice_header(const uint8_t *bs, int bs_size, EVCParserContext *ev)
> {
> GetBitContext gb;
> EVCParserSliceHeader *sh;
> EVCParserPPS *pps;
> EVCParserSPS *sps;
>
> int num_tiles_in_slice = 0;
> int slice_pic_parameter_set_id;
>
> if (init_get_bits8(&gb, bs, bs_size) < 0)
> return NULL;
>
> slice_pic_parameter_set_id = get_ue_golomb(&gb);
>
> if (slice_pic_parameter_set_id < 0 || slice_pic_parameter_set_id >= EVC_MAX_PPS_COUNT)
> return NULL;
>
> sh = &ev->slice_header[slice_pic_parameter_set_id];
> pps = &ev->pps[slice_pic_parameter_set_id];
> sps = &ev->sps[slice_pic_parameter_set_id];
Missing a check to see if either of these two exist/were parsed.
[...]
> +static int evc_parse(AVCodecParserContext *s, AVCodecContext *avctx,
> + const uint8_t **poutbuf, int *poutbuf_size,
> + const uint8_t *buf, int buf_size)
> +{
> + int next;
> + EVCParserContext *ev = s->priv_data;
> + ParseContext *pc = &ev->pc;
> +
> + if (s->flags & PARSER_FLAG_COMPLETE_FRAMES)
> + next = buf_size;
> + else {
> + next = evc_find_frame_end(s, buf, buf_size, avctx);
> + if (ff_combine_frame(pc, next, &buf, &buf_size) < 0) {
> + *poutbuf = NULL;
> + *poutbuf_size = 0;
> + return buf_size;
> + }
> + }
> +
> + parse_nal_units(s, buf, buf_size, avctx);
> +
> + // poutbuf contains just one Access Unit
> + *poutbuf = buf;
> + *poutbuf_size = buf_size;
> +
> + return next;
> +
Does the mp4 encapsulation allow the stripping of parameter sets from
packets? If so, you should parse extradata here too, otherwise no
sps/pps will be handled.
_______________________________________________
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-04-19 13:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230418103024eucas1p1ad475a241d2d758a7d9429a25802273f@eucas1p1.samsung.com>
2023-04-18 10:30 ` Dawid Kozinski
2023-04-19 13:12 ` 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=3f225c34-f8fb-2a7e-bf29-cc5d0660dc9d@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