From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH 3/2] cbs_av1: Remove constraint on MDCV luminance values Date: Wed, 18 Jan 2023 17:38:28 -0300 Message-ID: <e2f0a60e-aaab-b6a7-7f08-92499ee9519b@gmail.com> (raw) In-Reply-To: <f54abbae-e832-6030-7ba4-5abcddf357e7@jkqxz.net> On 1/18/2023 5:35 PM, Mark Thompson wrote: > While desiring min to be less than max feels entirely sensible, > unfortunately the standard does not actually have this requirement. Huh, it really doesn't. > --- > Some of the Argon coverage streams test this. > > libavcodec/cbs_av1_syntax_template.c | 7 ++----- > 1 file changed, 2 insertions(+), 5 deletions(-) > > diff --git a/libavcodec/cbs_av1_syntax_template.c > b/libavcodec/cbs_av1_syntax_template.c > index 3cab02bdd9..dc6724cb59 100644 > --- a/libavcodec/cbs_av1_syntax_template.c > +++ b/libavcodec/cbs_av1_syntax_template.c > @@ -1866,11 +1866,8 @@ static int > FUNC(metadata_hdr_mdcv)(CodedBitstreamContext *ctx, RWContext *rw, > fb(16, white_point_chromaticity_x); > fb(16, white_point_chromaticity_y); > > - fc(32, luminance_max, 1, MAX_UINT_BITS(32)); > - // luminance_min must be lower than luminance_max. Convert > luminance_max from > - // 24.8 fixed point to 18.14 fixed point in order to compare them. > - fc(32, luminance_min, 0, FFMIN(((uint64_t)current->luminance_max << > 6) - 1, > - MAX_UINT_BITS(32))); > + fb(32, luminance_max); > + fb(32, luminance_min); > > return 0; > } LGTM. _______________________________________________ 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-01-18 20:38 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-17 22:21 [FFmpeg-devel] [PATCH 1/2] cbs_av1: Add tracing headers for metadata types Mark Thompson 2023-01-17 22:23 ` [FFmpeg-devel] [PATCH 2/2] cbs_av1: Don't reject unknown metadata Mark Thompson 2023-01-18 20:35 ` [FFmpeg-devel] [PATCH 3/2] cbs_av1: Remove constraint on MDCV luminance values Mark Thompson 2023-01-18 20:38 ` James Almer [this message] 2023-01-24 22:29 ` Mark Thompson
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=e2f0a60e-aaab-b6a7-7f08-92499ee9519b@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