Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Jan Ekström" <jeebjp@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v2 0/3] avcodec: move HDR10 (MDCV/CLL) SEI handling to h2645_sei
Date: Thu, 27 Jul 2023 00:37:20 +0300
Message-ID: <CAEu79SZgW8C0sQVTznHNwViJgqCpMKdv-Zg=+yDmmT1Hy=uJJg@mail.gmail.com> (raw)
In-Reply-To: <20230725192918.199526-1-jeebjp@gmail.com>

On Tue, Jul 25, 2023 at 10:29 PM Jan Ekström <jeebjp@gmail.com> wrote:
>
> This allows parsing code to be re-utilized from H.264, as well as probably
> from VVC in the future.
>
> This additionally eases verification of the AVCodecContext side data patch
> set, which includes libx264 integration for HDR10 side data.
>
> Changes from v1:
> * Reordered the new h2645_sei include to correct location as per alphabetical
>   order. Thanks for Leo Izen for noticing this.
> * Cleaned up the mastering_display_metadata.h include in hevcdec, as that file
>   no longer directly handles AVContentLightMetadata or
>   AVMasteringDisplayMetadata.
>
> Notes:
> * In addition to testing with FATE, looking at the show_frames ffprobe output
>   for a UHD BD sample with each IRAP containing these SEI entries, the
>   behavior is the same as before with regards to each frame having the side
>   data persist.
>
>   There is also no change with tests I've done with a UHD BD mp4 remux as well
>   as an iphone 12 sample I had around, So I think I have not modified the HEVC
>   behavior in any great manner.
> * As for H.264, it now automatically gains support for these SEI messages. It
>   seems like its definition of CVS (coded video sequence) is from one IDR to
>   another (essentially a GOP). That said, currently the decoder resets the SEI
>   setup in decode_nal_units, which means that the side data only persist for
>   a single frame.
>

Unless there are objections, I will apply this tomorrow evening as
this is a strict improvement over the current situation where the
parsing is limited to HEVC and at least checking with ffprobe does not
show regressions for HEVC.

Jan
_______________________________________________
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".

  parent reply	other threads:[~2023-07-26 21:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 19:29 Jan Ekström
2023-07-25 19:29 ` [FFmpeg-devel] [PATCH v2 1/3] avcodec: move mastering display colour volume " Jan Ekström
2023-07-25 19:29 ` [FFmpeg-devel] [PATCH v2 2/3] avcodec: move content light level " Jan Ekström
2023-07-25 19:29 ` [FFmpeg-devel] [PATCH v2 3/3] avcodec/hevcdec: simplify decrementing of MDCV/CLL flags Jan Ekström
2023-07-26 21:37 ` Jan Ekström [this message]
2023-07-27 19:22   ` [FFmpeg-devel] [PATCH v2 0/3] avcodec: move HDR10 (MDCV/CLL) SEI handling to h2645_sei Jan Ekström

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='CAEu79SZgW8C0sQVTznHNwViJgqCpMKdv-Zg=+yDmmT1Hy=uJJg@mail.gmail.com' \
    --to=jeebjp@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