From: Cosmin Stejerean via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: "FFmpeg development discussions and patches" <ffmpeg-devel@ffmpeg.org> Cc: "Cosmin Stejerean" <cosmin@cosmin.at> Subject: Re: [FFmpeg-devel] [PATCH v2] avcodec/dovi - correctly read el_bit_depth_minus8 and ext_mapping_idc Date: Wed, 22 May 2024 15:50:34 +0000 Message-ID: <0101018fa0ff421e-4d7378f3-b75e-4ca0-9776-7e4baf4ac3a6-000000@us-west-2.amazonses.com> (raw) In-Reply-To: <GV1P250MB0737276A0B730B489BB24E7C8FEB2@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM> > On May 21, 2024, at 9:19 PM, Andreas Rheinhardt <andreas.rheinhardt@outlook.com> wrote: > > Cosmin Stejerean via ffmpeg-devel: >> From: Cosmin Stejerean <cosmin@cosmin.at> >> >> These two fields are coded together into a single 16 bit integer with upper 8 >> bits for ext_mapping_idc and lower 8 bits for el_bit_depth_minus8. >> >> Furthermore ext_mapping_idc has two components, upper 3 bits and lower 5 bits. > > How do you know about these fields? You seem to know something that > Niklas doesn't. I can see them in the output of the DoVi verifier. RPU Header ... | Sequence header ... | BL_video_full_range_flag 0 | BL_bit_depth 10 | EL_bit_depth 10 | ext_mapping_idc[4:0] 1 | ext_mapping_idc[7:5] 4 | vdr_bit_depth 12 ... >> --- a/libavutil/dovi_meta.h >> +++ b/libavutil/dovi_meta.h >> @@ -87,6 +87,8 @@ typedef struct AVDOVIRpuDataHeader { >> uint8_t bl_video_full_range_flag; >> uint8_t bl_bit_depth; /* [8, 16] */ >> uint8_t el_bit_depth; /* [8, 16] */ >> + uint8_t ext_mapping_idc_0_4; /* extended base layer inverse mapping indicator */ >> + uint8_t ext_mapping_idc_5_7; /* reserved */ > > This is an ABI break. All new additions need to be put at the end. > Furthermore this needs an entry in APIChanges and a lavu minor version > bump. And it should be in a patch of its own. Ok, sending v3. - Cosmin _______________________________________________ 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:[~2024-05-22 15:50 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20240521183905.76407-1-cosmin@cosmin.at> 2024-05-21 18:39 ` Cosmin Stejerean via ffmpeg-devel 2024-05-22 4:19 ` Andreas Rheinhardt [not found] ` <0933A15D-25B1-4AB6-99D7-1389D3561AE8@cosmin.at> 2024-05-22 15:50 ` Cosmin Stejerean via ffmpeg-devel [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=0101018fa0ff421e-4d7378f3-b75e-4ca0-9776-7e4baf4ac3a6-000000@us-west-2.amazonses.com \ --to=ffmpeg-devel@ffmpeg.org \ --cc=cosmin@cosmin.at \ /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