From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] avformat/mxfenc: SMPTE RDD 48:2018 Amd 1:2022 (FFV1 in MXF) support
Date: Sat, 1 Apr 2023 17:43:01 +0200
Message-ID: <20230401154301.GF1164690@pb2> (raw)
In-Reply-To: <85c1e58e-cc90-5814-cba5-d91201dec993@mediaarea.net>
[-- Attachment #1.1: Type: text/plain, Size: 1865 bytes --]
On Sat, Apr 01, 2023 at 05:20:50PM +0200, Jerome Martinez wrote:
> On 01/04/2023 16:37, Michael Niedermayer wrote:
> > On Tue, Mar 14, 2023 at 10:52:15AM +0100, Jerome Martinez wrote:
> > [...]
> > > +
> > > + memset(state, 128, sizeof(state));
> > > + if (st->codecpar->extradata) {
> > > + ff_init_range_decoder(&c, st->codecpar->extradata, st->codecpar->extradata_size);
> > > + ff_build_rac_states(&c, 0.05 * (1LL << 32), 256 - 8);
> > > + v = get_ffv1_unsigned_symbol(&c, state);
> > > + av_assert0(v >= 2);
> > > + if (v > 4) {
> > > + return 0;
> > > + }
> > > + sc->micro_version = get_ffv1_unsigned_symbol(&c, state);
> > > + } else {
> > > + uint8_t keystate = 128;
> > > + ff_init_range_decoder(&c, pkt->data, pkt->size);
> > > + ff_build_rac_states(&c, 0.05 * (1LL << 32), 256 - 8);
> > > + get_rac(&c, &keystate); // keyframe
> > > + v = get_ffv1_unsigned_symbol(&c, state);
> > > + av_assert0(v < 2);
> > Are these asserts testing muxer input ?
> > if so what ensures that the values are within the asserted range ?
>
>
> My understanding of the code and workflow is that the input is currently
> rejected (AV_LOG_ERROR, "invalid version %d in ver01 header\n" and
> AV_LOG_ERROR, "Invalid version in global header\n") in ffv1dec.c during the
> analysis of this input so before this piece of code is reached.
> Could be an AV_LOG_ERROR if preferred.
if the encoder writes 5 teh muxer crashes here
V 5me= 0 fps=0.0 q=-0.0 size= 0kB time=00:00:00.00 bitrate=N/A speed= 0x
Assertion v < 2 failed at libavformat/mxfenc.c:2505
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Never trust a computer, one day, it may think you are the virus. -- Compn
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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 prev parent reply other threads:[~2023-04-01 15:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 15:45 Jerome Martinez
2023-01-16 14:00 ` Tomas Härdin
2023-01-16 14:17 ` Jerome Martinez
2023-01-18 10:12 ` Tomas Härdin
2023-01-18 14:25 ` Jerome Martinez
2023-01-18 13:40 ` Tomas Härdin
2023-01-18 14:15 ` Jerome Martinez
2023-01-20 15:17 ` Tomas Härdin
2023-01-29 16:36 ` Dave Rice
2023-01-31 14:53 ` Tomas Härdin
2023-03-14 9:52 ` Jerome Martinez
2023-03-15 14:00 ` Tomas Härdin
2023-03-24 13:59 ` Dave Rice
2023-03-25 18:29 ` Tomas Härdin
2023-04-01 14:37 ` Michael Niedermayer
2023-04-01 15:20 ` Jerome Martinez
2023-04-01 15:43 ` Michael Niedermayer [this message]
2023-04-01 17:11 ` Jerome Martinez
2023-04-02 20:07 ` Michael Niedermayer
2023-04-02 22:07 ` Jerome Martinez
2023-04-04 14:43 ` Michael Niedermayer
2023-04-04 14:57 ` Jerome Martinez
2023-04-04 17:32 ` Michael Niedermayer
2023-04-04 21:37 ` Jerome Martinez
2023-04-05 12:31 ` Michael Niedermayer
2023-04-05 12:42 ` Michael Niedermayer
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=20230401154301.GF1164690@pb2 \
--to=michael@niedermayer.cc \
--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