From: Jerome Martinez <jerome@mediaarea.net> To: 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 19:11:45 +0200 Message-ID: <71eaedd7-d771-50a7-ed13-3733b8c2187f@mediaarea.net> (raw) In-Reply-To: <20230401154301.GF1164690@pb2> [-- Attachment #1: Type: text/plain, Size: 2739 bytes --] On 01/04/2023 17:43, Michael Niedermayer wrote: > 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 I hardcoded version 5 in the encoder based on version 4 (so with extra metadata), and I have: [mxf @ 0x7fffd52f3100] could not get ffv1 version My understanding is that you hardcoded version 5 in the encoder based on version 0 or 1 (so without extra metadata), in that case I have the assert, and it was on purpose on my side because I understand from ffv1 encoder code that any version > 2 should have extra metadata, and if it changes in the future this line in MXF muxer should be changed at the same time as FFV1 encoder code But I didn't test and didn't realize that the FFV1 parsing is not done with -c:v copy, and if that case I get the assert with an (fake) input with version 5 and no extra metadata. What about the attached patch? I reused the ffv1 decoder error messages + "ffv1 " tip. Note: I moved, so less coherency in the code, the error message in mxf_parse_ffv1_frame for more precise message depending on the presence or not of extra metadata, it could stay as is if we don't care about the precision. [-- Attachment #2: 0001-avformat-mxfenc-replace-ffv1-version-related-assert-.patch --] [-- Type: text/plain, Size: 1870 bytes --] From 65f6fba9434fa9ab4b5d2b91c3f930c1e3cb4bef Mon Sep 17 00:00:00 2001 From: Jerome Martinez <jerome@mediaarea.net> Date: Sat, 1 Apr 2023 19:04:25 +0200 Subject: [PATCH] avformat/mxfenc: replace ffv1 version related assert by error message --- libavformat/mxfenc.c | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/libavformat/mxfenc.c b/libavformat/mxfenc.c index 9eba208ffb..0a1ae5353c 100644 --- a/libavformat/mxfenc.c +++ b/libavformat/mxfenc.c @@ -2489,8 +2489,8 @@ static int mxf_parse_ffv1_frame(AVFormatContext *s, AVStream *st, AVPacket *pkt) 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) { + if (v < 2) { + av_log(s, AV_LOG_ERROR, "Invalid version in ffv1 global header\n"); return 0; } sc->micro_version = get_ffv1_unsigned_symbol(&c, state); @@ -2500,7 +2500,10 @@ static int mxf_parse_ffv1_frame(AVFormatContext *s, AVStream *st, AVPacket *pkt) 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); + if (v >= 2) { + av_log(s, AV_LOG_ERROR, "invalid version %d in ffv1 ver01 header\n", v); + return 0; + } } sc->codec_ul = &mxf_ffv1_codec_uls[v]; @@ -3129,7 +3132,6 @@ static int mxf_write_packet(AVFormatContext *s, AVPacket *pkt) } } else if (st->codecpar->codec_id == AV_CODEC_ID_FFV1) { if (!mxf_parse_ffv1_frame(s, st, pkt)) { - av_log(s, AV_LOG_ERROR, "could not get ffv1 version\n"); return -1; } } -- 2.13.3.windows.1 [-- Attachment #3: 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 17:11 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 2023-04-01 17:11 ` Jerome Martinez [this message] 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=71eaedd7-d771-50a7-ed13-3733b8c2187f@mediaarea.net \ --to=jerome@mediaarea.net \ --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