From: Mohammad Izadi
The dynamic metadata contains data for color volume transform - application 4
of SPMTE 2094-40:2016 standard. The data comes from HEVC in the
SEI_TYPE_USER_DATA_REGISTERED_ITU_T_T35.
I'll add support to HEVC in a follow-up.
---
libavutil/Makefile
On Mon, Feb 24, 2020 at 9:56 AM Vittorio Giovara
wrote:
> On Sat, Feb 22, 2020 at 12:44 PM Mohammad Izadi
> wrote:
>
> > On Fri, Feb 21, 2020, 6:44 PM Vittorio Giovara <
> vittorio.giov...@gmail.com
> > >
> > wrote:
> >
> > > On Fri,
On Tue, Feb 25, 2020, 9:32 PM Vittorio Giovara
wrote:
> On Tue, Feb 25, 2020 at 9:16 PM Mohammad Izadi
> wrote:
>
> > On Mon, Feb 24, 2020 at 9:56 AM Vittorio Giovara <
> > vittorio.giov...@gmail.com>
> > wrote:
> >
> > > On Sat, Feb
From: Mohammad Izadi
Trying to read HDR10+ metadata from HEVC/SEI and pass it to packet side data in
the follow-up CLs.
---
libavutil/hdr_dynamic_metadata.c | 386 +++
libavutil/hdr_dynamic_metadata.h | 51 +++-
libavutil/version.h | 2 +-
3 files
wrote:
> Am Mo., 27. Jan. 2020 um 20:34 Uhr schrieb Mohammad Izadi <
> moh.iz...@gmail.com>:
>
> > /**
> > * Allocate an AVDynamicHDRPlus structure and set its fields to
> > * default values. The resulting struct can be freed using av_freep().
>
James, I am making another CL to comply with API.
I have a question about using GetBitContext and PutBitContext. Is there any
alternative to use in libavutil?
--
Best,
Mohammad
On Mon, Jan 27, 2020 at 11:50 AM James Almer wrote:
> On 1/27/2020 4:08 PM, Mohammad Izadi wrote:
> > From:
Great! Thanks!
On Mon, Feb 3, 2020, 6:37 PM James Almer wrote:
> On 2/3/2020 11:01 PM, Mohammad Izadi wrote:
> > James, I am making another CL to comply with API.
> > I have a question about using GetBitContext and PutBitContext. Is there
> any
> > alternative to use i
From: Mohammad Izadi
Trying to read HDR10+ metadata from HEVC/SEI and pass it to packet side data in
the follow-up CLs.
---
libavutil/hdr_dynamic_metadata.c | 167 ++-
libavutil/hdr_dynamic_metadata.h | 14 ++-
libavutil/version.h | 2 +-
3 files
Please check my responses inline:
On Wed, Feb 5, 2020 at 5:48 AM Moritz Barsnick wrote:
> Hi Mohammad,
>
> On Tue, Feb 04, 2020 at 18:44:00 -0800, Mohammad Izadi wrote:
> > --- a/libavutil/hdr_dynamic_metadata.c
> > +++ b/libavutil/hdr_dynamic_metada
From: Mohammad Izadi
Trying to read HDR10+ metadata from HEVC/SEI and pass it to packet side data in
the follow-up CLs.
---
libavutil/hdr_dynamic_metadata.c | 165 +++
libavutil/hdr_dynamic_metadata.h | 12 ++-
libavutil/version.h | 2 +-
3 files
From: Mohammad Izadi
Trying to read HDR10+ metadata from HEVC/SEI and pass it to packet side data in
the follow-up CLs.
---
libavutil/hdr_dynamic_metadata.c | 165 +++
libavutil/hdr_dynamic_metadata.h | 12 ++-
libavutil/version.h | 2 +-
3 files
On Sun, Feb 9, 2020 at 8:31 AM Mark Thompson wrote:
> On 07/02/2020 17:46, Mohammad Izadi wrote:
> > From: Mohammad Izadi
> >
> > Trying to read HDR10+ metadata from HEVC/SEI and pass it to packet side
> data in the follow-up CLs.
> > ---
> > li
From: Mohammad Izadi
Trying to read HDR10+ metadata from HEVC/SEI and pass it to packet side data in
the follow-up CLs.
---
libavutil/hdr_dynamic_metadata.c | 165 +++
libavutil/hdr_dynamic_metadata.h | 13 ++-
libavutil/version.h | 2 +-
3 files
Hello,
What's the status of the cl review? Is it good to submit?
--
Best,
Mohammad
On Mon, Feb 10, 2020 at 11:44 AM Mohammad Izadi wrote:
> From: Mohammad Izadi
>
> Trying to read HDR10+ metadata from HEVC/SEI and pass it to packet side
> data in the follow-up CLs.
&
The comment was wrong.
--
Best,
Mohammad
On Wed, Feb 19, 2020 at 7:22 AM Derek Buitenhuis
wrote:
> On 10/02/2020 19:44, Mohammad Izadi wrote:
> > /**
> > * The nominal maximum display luminance of the targeted system
> display,
> > - * in units of 0.
On Wed, Feb 19, 2020 at 4:22 PM Mark Thompson wrote:
> On 10/02/2020 19:38, Mohammad Izadi wrote:
> > On Sun, Feb 9, 2020 at 8:31 AM Mark Thompson wrote:
> >
> >> On 07/02/2020 17:46, Mohammad Izadi wrote:
> >>> From: Mohammad Izadi
> >>>
> &
On Thu, Feb 20, 2020 at 12:10 PM Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> On Mon, Feb 10, 2020 at 3:14 PM Mohammad Izadi
> wrote:
>
> > From: Mohammad Izadi
> >
> > Trying to read HDR10+ metadata from HEVC/SEI and pass it to packet s
,
Mohammad
On Fri, Feb 21, 2020 at 2:53 AM Hendrik Leppkes wrote:
> On Fri, Feb 21, 2020 at 5:59 AM Vittorio Giovara
> wrote:
> >
> > On Thu, Feb 20, 2020 at 6:38 PM James Almer wrote:
> >
> > > On 2/20/2020 5:02 PM, Vittorio Giovara wrote:
> > &
PM Mohammad Izadi
> wrote:
> >
> > If you believe lavc is at the top of the hierarchy, I can simply move the
> > file to lavc. Then both lavc and lavf can use it and hierarchy is
> > respected. Can I do that? Doesn't break API? Any objection (with
> solution)?
>
On Fri, Feb 21, 2020, 6:44 PM Vittorio Giovara
wrote:
> On Fri, Feb 21, 2020 at 5:17 PM Mohammad Izadi
> wrote:
>
> > Why does the struct belong to lavu? This struct is super similar to
> structs
> > in libavcodec/hevc_sei.h. We just move it to a new file to share it
&g
HDR10+ metadata is stored in the bit stream for HEVC. The story is different
for VP9 and cannot store the metadata in the bit stream. HDR10+ should be
passed to packet side data an stored in the container (mkv) for VP9.
This CL is taking HDR10+ from AVFrame side data in libvpxenc and is passing
On Fri, Apr 23, 2021 at 11:53 AM James Zern
wrote:
> Hi,
>
> On Fri, Apr 23, 2021 at 8:58 AM Mohammad Izadi
> wrote:
> >
> > HDR10+ metadata is stored in the bit stream for HEVC. The story is
> different for VP9 and cannot store the metadata in the bit stream. H
HDR10+ metadata is stored in the bit stream for HEVC. The story is different
for VP9 and cannot store the metadata in the bit stream. HDR10+ should be
passed to packet side data an stored in the container (mkv) for VP9.
This CL is taking HDR10+ from AVFrame side data in libvpxenc and is passing
Any more comments or looks good to go?
Thanks,
Mohammad
On Mon, Apr 26, 2021 at 6:54 PM Mohammad Izadi wrote:
> HDR10+ metadata is stored in the bit stream for HEVC. The story is
> different for VP9 and cannot store the metadata in the bit stream. HDR10+
> should be passed to packet
HDR10+ metadata is stored in the bit stream for HEVC. The story is different
for VP9 and cannot store the metadata in the bit stream. HDR10+ should be
passed to packet side data an stored in the container (mkv) for VP9.
This CL is taking HDR10+ from AVFrame side data in libvpxenc and is passing
Answered inline:
On Tue, May 25, 2021 at 8:15 AM James Almer wrote:
> On 4/26/2021 10:54 PM, Mohammad Izadi wrote:
> > HDR10+ metadata is stored in the bit stream for HEVC. The story is
> different for VP9 and cannot store the metadata in the bit stream. HDR10+
> should be p
HDR10+ metadata is stored in the bit stream for HEVC. The story is different
for VP9 and cannot store the metadata in the bit stream. HDR10+ should be
passed to packet side data an stored in the container (mkv) for VP9.
This CL is taking HDR10+ from AVFrame side data in libvpxenc and is passing
On Tue, May 25, 2021 at 11:21 PM Moritz Barsnick wrote:
> On Tue, May 25, 2021 at 18:53:11 -0700, Mohammad Izadi wrote:
>
> > Subject: Pass the HDR10+ metadata to the packet side data in VP9 encoder
>
> You should prefix this with "avcodec: ".
>
Done
>
&
HDR10+ metadata is stored in the bit stream for HEVC. The story is different
for VP9 and cannot store the metadata in the bit stream. HDR10+ should be
passed to packet side data an stored in the container (mkv) for VP9.
This CL is taking HDR10+ from AVFrame side data in libvpxenc and is passing
HDR10+ metadata is stored in the bit stream for HEVC. The story is different
for VP9 and cannot store the metadata in the bit stream. HDR10+ should be
passed to packet side data an stored in the container (mkv) for VP9.
This CL is taking HDR10+ from AVFrame side data in libvpxenc and is passing
All done.
On Wed, May 26, 2021 at 2:42 PM Lynne wrote:
> May 26, 2021, 20:43 by izadi-at-google@ffmpeg.org:
>
> > HDR10+ metadata is stored in the bit stream for HEVC. The story is
> different for VP9 and cannot store the metadata in the bit stream. HDR10+
> should be passed to packet side
HDR10+ metadata is stored in the bit stream for HEVC. The story is different
for VP9 and cannot store the metadata in the bit stream. HDR10+ should be
passed to packet side data an stored in the container (mkv) for VP9.
This CL is taking HDR10+ from AVFrame side data in libvpxenc and is passing
On Wed, May 26, 2021 at 9:17 PM James Zern
wrote:
> On Wed, May 26, 2021 at 6:35 PM Mohammad Izadi
> wrote:
> > [...]
> > +static void add_hdr10_plus(AVFifoBuffer *fifo, struct FrameHDR10Plus
> *data)
> > +{
> > +av_fifo_grow(fifo, sizeof(FrameHDR10Plus));
On Fri, May 28, 2021 at 4:49 AM Michael Niedermayer
wrote:
> On Thu, May 27, 2021 at 09:44:10AM -0700, Mohammad Izadi wrote:
> > HDR10+ metadata is stored in the bit stream for HEVC. The story is
> different for VP9 and cannot store the metadata in the bit stream. HDR10+
> shou
HDR10+ metadata is stored in the bit stream for HEVC. The story is different
for VP9 and cannot store the metadata in the bit stream. HDR10+ should be
passed to packet side data an stored in the container (mkv) for VP9.
This CL is taking HDR10+ from AVFrame side data in libvpxenc and is passing
HDR10+ metadata is stored in the bit stream for HEVC. The story is different
for VP9 and cannot store the metadata in the bit stream. HDR10+ should be
passed to packet side data an stored in the container (mkv) for VP9.
This CL is taking HDR10+ from AVFrame side data in libvpxenc and is passing
On Wed, Jun 2, 2021 at 1:31 PM James Zern
wrote:
> On Tue, Jun 1, 2021 at 6:47 PM Mohammad Izadi
> wrote:
> > [...]
> > +static av_cold int add_hdr10_plus(AVFifoBuffer *fifo, struct
> FrameHDR10Plus *data)
> > +{
> > +int err = av_fifo_grow(fifo, sizeof(Fr
On Wed, Jun 2, 2021 at 1:34 PM James Zern
wrote:
> On Tue, Jun 1, 2021 at 6:23 PM Mohammad Izadi
> wrote:
> >
> > On Fri, May 28, 2021 at 4:49 AM Michael Niedermayer
>
> > wrote:
> >
> > > On Thu, May 27, 2021 at 09:44:10AM -0700, Mohammad Izadi wrote
On Mon, Jun 7, 2021 at 9:51 AM Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> Mohammad Izadi:
> > HDR10+ metadata is stored in the bit stream for HEVC. The story is
> different for VP9 and cannot store the metadata in the bit stream. HDR10+
> should be passed t
HDR10+ metadata is stored in the bit stream for HEVC. The story is different
for VP9 and cannot store the metadata in the bit stream. HDR10+ should be
passed to packet side data an stored in the container (mkv) for VP9.
This CL is taking HDR10+ from AVFrame side data in libvpxenc and is passing
HDR10+ metadata is stored in the bit stream for HEVC. The story is different
for VP9 and cannot store the metadata in the bit stream. HDR10+ should be
passed to packet side data an stored in the container (mkv) for VP9.
This CL is taking HDR10+ from AVFrame side data in libvpxenc and is passing
On Mon, Jun 7, 2021 at 12:59 PM Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> Michael Niedermayer:
> > On Mon, Jun 07, 2021 at 10:39:19AM -0700, Mohammad Izadi wrote:
> >> HDR10+ metadata is stored in the bit stream for HEVC. The story is
> different f
On Tue, Jun 8, 2021 at 12:01 PM Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> Andreas Rheinhardt:
> > Mohammad Izadi:
> >> HDR10+ metadata is stored in the bit stream for HEVC. The story is
> different for VP9 and cannot store the metadata in the bit
HDR10+ metadata is stored in the bit stream for HEVC. The story is different
for VP9 and cannot store the metadata in the bit stream. HDR10+ should be
passed to packet side data an stored in the container (mkv) for VP9.
This CL is taking HDR10+ from AVFrame side data in libvpxenc and is passing
HDR10+ metadata is stored in the bit stream for HEVC. The story is different
for VP9 and cannot store the metadata in the bit stream. HDR10+ should be
passed to packet side data an stored in the container (mkv) for VP9.
This CL is taking HDR10+ from AVFrame side data in libvpxenc and is passing
On Thu, Jun 10, 2021 at 4:05 PM Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> Mohammad Izadi:
> > HDR10+ metadata is stored in the bit stream for HEVC. The story is
> different for VP9 and cannot store the metadata in the bit stream. HDR10+
> should be passe
HDR10+ metadata is stored in the bit stream for HEVC. The story is different
for VP9 and cannot store the metadata in the bit stream. HDR10+ should be
passed to packet side data an stored in the container (mkv) for VP9.
This CL is taking HDR10+ from AVFrame side data in libvpxenc and is passing
Thanks,
Mohammad
On Mon, Jun 14, 2021 at 4:42 PM Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> Mohammad Izadi:
> > HDR10+ metadata is stored in the bit stream for HEVC. The story is
> different for VP9 and cannot store the metadata in the bit stream. HDR10+
>
Thanks,
Mohammad
On Mon, Jun 14, 2021 at 5:17 PM Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> Mohammad Izadi:
> > On Thu, Jun 10, 2021 at 4:05 PM Andreas Rheinhardt <
> > andreas.rheinha...@outlook.com> wrote:
> >
> >> Mohammad Izadi:
HDR10+ metadata is stored in the bit stream for HEVC. The story is different
for VP9 and cannot store the metadata in the bit stream. HDR10+ should be
passed to packet side data an stored in the container (mkv) for VP9.
This CL is taking HDR10+ from AVFrame side data in libvpxenc and is passing
On Tue, Jun 15, 2021 at 5:18 PM Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> Mohammad Izadi:
> > HDR10+ metadata is stored in the bit stream for HEVC. The story is
> different for VP9 and cannot store the metadata in the bit stream. HDR10+
> should be passe
HDR10+ metadata is stored in the bit stream for HEVC. The story is different
for VP9 and cannot store the metadata in the bit stream. HDR10+ should be
passed to packet side data an stored in the container (mkv) for VP9.
This CL is taking HDR10+ from AVFrame side data in libvpxenc and is passing
On Thu, Jun 17, 2021 at 1:04 PM James Zern
wrote:
> On Wed, Jun 16, 2021 at 3:53 PM Mohammad Izadi
> wrote:
> >
> > HDR10+ metadata is stored in the bit stream for HEVC. The story is
> different for VP9 and cannot store the metadata in the bit stream. HDR10+
> should
LGTM?
On Thu, Jun 17, 2021 at 10:21 PM Mohammad Izadi wrote:
>
>
> On Thu, Jun 17, 2021 at 1:04 PM James Zern
> wrote:
>
>> On Wed, Jun 16, 2021 at 3:53 PM Mohammad Izadi
>> wrote:
>> >
>> > HDR10+ metadata is stored in the bit stream for HEVC.
HDR10+ metadata is stored in the bit stream for HEVC. The story is different
for VP9 and cannot store the metadata in the bit stream. HDR10+ should be
passed to packet side data an stored in the container (mkv) for VP9.
This CL is taking HDR10+ from AVFrame side data in libvpxenc and is passing
On Tue, Jun 22, 2021 at 1:47 PM James Zern
wrote:
> On Thu, Jun 17, 2021 at 10:21 PM Mohammad Izadi
> wrote:
> >
> > HDR10+ metadata is stored in the bit stream for HEVC. The story is
> different for VP9 and cannot store the metadata in the bit stream. HDR10+
> should
As Jan mentioned, we need to specify the kind of the HDR metadata. Here are
some alternatives:
AVDynamicHDRPlus
AVSMPTE2094App4 (Application 4 is HDR10+ while Dolby is application 1)
AVHDRPlusMetadata
Which one do you prefer?
--
Best,
Mohammad
On Mon, Dec 17, 2018 at 3:07 PM Jan Ekström
From: Mohammad Izadi
The dynamic metadata contains data for color volume transform - application 4
of SPMTE 2094-40:2016 standard. The data comes from HEVC in the
SEI_TYPE_USER_DATA_REGISTERED_ITU_T_T35.
I'll add support to HEVC in a follow-up.
---
libavutil/Makefile
From: Mohammad Izadi
The dynamic metadata contains data for color volume transform - application 4
of SMPTE 2094-40:2016 standard. The data comes from HEVC in the
SEI_TYPE_USER_DATA_REGISTERED_ITU_T_T35.
I'll add support to HEVC in a follow-up.
---
libavutil/Makefile
11:35 AM Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> On Wed, Dec 19, 2018 at 7:08 PM Mohammad Izadi
> wrote:
>
> > From: Mohammad Izadi
> >
> > The dynamic metadata contains data for color volume transform -
> > application 4 of
Thank you! Please go ahead and push the patch.
--
Best,
Mohammad
On Thu, Dec 20, 2018 at 11:07 AM Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> On Thu, Dec 20, 2018 at 7:18 PM Mohammad Izadi
> wrote:
>
> > Hi Vittorio,
> >
> > Thank you for your feed
From: Mohammad Izadi
The dynamic metadata contains data for color volume transform - application 4
of SMPTE 2094-40:2016 standard. The data comes from HEVC in the
SEI_TYPE_USER_DATA_REGISTERED_ITU_T_T35.
I'll add support to HEVC in a follow-up.
---
libavutil/Makefile
Decode HDR10+ metadata from SEI message and propagate it to side data.
---
libavcodec/avcodec.h | 10 +-
libavcodec/avpacket.c | 1 +
libavcodec/decode.c | 2 +-
libavcodec/hevc_sei.c | 234 --
libavcodec/hevc_sei.h | 7 ++
libavcodec/hevcdec.c |
Hi James,
Thank you for your comments. I applied all your notes and will sent you two
patches in reply to your email.
--
Best,
Mohammad
On Wed, Dec 26, 2018 at 12:11 PM James Almer wrote:
> On 12/26/2018 4:40 PM, Mohammad Izadi wrote:
> > Decode HDR10+ metadata from SEI message and
---
libavcodec/avcodec.h | 8
libavcodec/avpacket.c | 1 +
libavcodec/decode.c | 1 +
libavcodec/version.h | 2 +-
4 files changed, 11 insertions(+), 1 deletion(-)
diff --git a/libavcodec/avcodec.h b/libavcodec/avcodec.h
index 92567ec6d0..75fd44d74c 100644
--- a/libavcodec/avcodec.h
---
libavcodec/hevc_sei.c | 219 --
libavcodec/hevc_sei.h | 46 +
libavcodec/hevcdec.c | 195 +
3 files changed, 454 insertions(+), 6 deletions(-)
diff --git a/libavcodec/hevc_sei.c b/libavcodec/hevc_sei.c
index
I did that before and James ask me to copy. So now, James are you OK with
that?
--
Best,
Mohammad
On Thu, Jan 3, 2019 at 5:08 PM Rostislav Pehlivanov
wrote:
> On Thu, 3 Jan 2019 at 20:13, Mohammad Izadi wrote:
>
> >
> > /**
> > @@ -94,6 +95,50 @@ typedef struct
You mean a pointer in HEVCSEIDynamicHDRPlus, not in HEVCSEIContentLight?
--
Best,
Mohammad
On Thu, Jan 3, 2019 at 5:08 PM Rostislav Pehlivanov
wrote:
> On Thu, 3 Jan 2019 at 20:13, Mohammad Izadi wrote:
>
> >
> > /**
> > @@ -94,6 +95,50 @@ typedef struct
h new struct with
internal consumption? The problem would get more complicated when we add
more dynamic metadata standards (like Dolby) in the future under
ContentLight struct.
--
Best,
Mohammad
On Fri, Jan 4, 2019 at 10:54 AM Rostislav Pehlivanov
wrote:
> On Fri, 4 Jan 2019 at 18:12, Mohamm
t;
> > On 1/4/2019 3:53 PM, Rostislav Pehlivanov wrote:
> > > On Fri, 4 Jan 2019 at 18:12, Mohammad Izadi
> wrote:
> > >
> > >> You mean a pointer in HEVCSEIDynamicHDRPlus, not in
> HEVCSEIContentLight?
> > >> --
> > >> Best,
Thanks James.
--
Best,
Mohammad
On Fri, Jan 4, 2019 at 3:03 PM James Almer wrote:
> On 1/4/2019 7:51 PM, Rostislav Pehlivanov wrote:
> > On Fri, 4 Jan 2019 at 21:08, James Almer wrote:
> >
> >> On 1/4/2019 3:53 PM, Rostislav Pehlivanov wrote:
> >>> On Fri,
---
libavcodec/hevc_sei.c | 236 --
libavcodec/hevc_sei.h | 6 ++
libavcodec/hevcdec.c | 19
3 files changed, 255 insertions(+), 6 deletions(-)
diff --git a/libavcodec/hevc_sei.c b/libavcodec/hevc_sei.c
index c59bd4321e..7e59bf0813 100644
--- a/lib
e:
> On 1/7/2019 8:55 PM, Mohammad Izadi wrote:
> > ---
> > libavcodec/hevc_sei.c | 236 --
> > libavcodec/hevc_sei.h | 6 ++
> > libavcodec/hevcdec.c | 19
> > 3 files changed, 255 insertions(+), 6 deletions(
hat uninit function do you refer exactly? I did not find it.
>
>
>
> --
> Best,
> Mohammad
>
>
> On Mon, Jan 7, 2019 at 5:19 PM James Almer wrote:
>
>> On 1/7/2019 8:55 PM, Mohammad Izadi wrote:
>> > ---
>> > libavcodec/hevc_sei.c | 23
---
libavcodec/hevc_sei.c | 211 --
libavcodec/hevc_sei.h | 6 ++
libavcodec/hevcdec.c | 22 +
3 files changed, 233 insertions(+), 6 deletions(-)
diff --git a/libavcodec/hevc_sei.c b/libavcodec/hevc_sei.c
index c59bd4321e..265e3f4dd1 100644
--- a/li
---
libavcodec/hevc_sei.c | 211 --
libavcodec/hevc_sei.h | 6 ++
libavcodec/hevcdec.c | 22 +
3 files changed, 233 insertions(+), 6 deletions(-)
diff --git a/libavcodec/hevc_sei.c b/libavcodec/hevc_sei.c
index c59bd4321e..6edec9f0db 100644
--- a/li
---
libavcodec/hevc_sei.c | 216 --
libavcodec/hevc_sei.h | 6 ++
libavcodec/hevcdec.c | 21
3 files changed, 237 insertions(+), 6 deletions(-)
diff --git a/libavcodec/hevc_sei.c b/libavcodec/hevc_sei.c
index c59bd4321e..15cd956e85 100644
--- a/lib
---
libavcodec/hevc_sei.c | 216 --
libavcodec/hevc_sei.h | 6 ++
libavcodec/hevcdec.c | 21
3 files changed, 237 insertions(+), 6 deletions(-)
diff --git a/libavcodec/hevc_sei.c b/libavcodec/hevc_sei.c
index c59bd4321e..15cd956e85 100644
--- a/lib
I will add the test by the end of this week.
Thanks,
Mohammad
On Mon, Sep 7, 2020 at 2:56 AM Jan Ekström wrote:
> On Sat, Jul 25, 2020 at 12:09 AM Mohammad Izadi
> wrote:
> >
> > On Fri, Jul 24, 2020 at 9:30 AM Andreas Rheinhardt <
> > andreas.rheinha...@gmail.com
From: Mohammad Izadi
HDR10+ is dynamic metadata (A/341 Amendment - SMPTE2094-40) that needs to be
decoded from ITU-T T.35 in HEVC bitstream. The HDR10+ is transferred to side
data packet to be used or passed through.
The fate test file can be found here:
https://drive.google.com/file/d
Any comments?
Thanks,
Mohammad
On Tue, Oct 13, 2020 at 4:53 PM Mohammad Izadi wrote:
> From: Mohammad Izadi
>
> HDR10+ is dynamic metadata (A/341 Amendment - SMPTE2094-40) that needs to
> be decoded from ITU-T T.35 in HEVC bitstream. The HDR10+ is transferred to
> side data pa
Thank you, Jan! I hope you feel better soon.
On Sun, Oct 25, 2020 at 5:49 PM Jan Ekström wrote:
> On Wed, Oct 14, 2020 at 2:54 AM Mohammad Izadi
> wrote:
> >
> > From: Mohammad Izadi
> >
> > HDR10+ is dynamic metadata (A/341 Amendment - SMPTE2094-40) that need
Any update? Can we push it to the head?
Thanks,
Mohammad
On Mon, Oct 26, 2020 at 11:53 AM Mohammad Izadi wrote:
> Thank you, Jan! I hope you feel better soon.
>
>
>
> On Sun, Oct 25, 2020 at 5:49 PM Jan Ekström wrote:
>
>> On Wed, Oct 14, 2020 at 2:54 AM
Is anybody there? Any update? Can we push it to the head?
Thanks,
Mohammad
On Fri, Nov 6, 2020 at 9:42 PM Mohammad Izadi wrote:
> Any update? Can we push it to the head?
> Thanks,
> Mohammad
>
>
> On Mon, Oct 26, 2020 at 11:53 AM Mohammad Izadi wrote:
>
>> Than
Thank you Ian for your great detailed comments.
Thanks,
Mohammad
On Wed, Nov 11, 2020 at 5:10 PM Jan Ekström wrote:
> On 14.10.2020 2:53, Mohammad Izadi wrote:
> > From: Mohammad Izadi
> >
> > HDR10+ is dynamic metadata (A/341 Amendment - SMPTE2094-40) that needs
> to
From: Mohammad Izadi
HDR10+ is dynamic metadata (A/341 Amendment - SMPTE2094-40) that needs to be
decoded from ITU-T T.35 in HEVC bitstream. The HDR10+ is transferred to side
data packet to be used or passed through.
The fate test file can be found here:
https://drive.google.com/file/d
From: Mohammad Izadi
HDR10+ is dynamic metadata (A/341 Amendment - SMPTE2094-40) that needs to be
decoded from ITU-T T.35 in HEVC bitstream. The HDR10+ is transferred to side
data packet to be used or passed through.
---
The fate test file can be found here:
https://drive.google.com/file/d
From: Mohammad Izadi
HDR10+ is dynamic metadata (A/341 Amendment - SMPTE2094-40) that needs to be
decoded from ITU-T T.35 in HEVC bitstream. The HDR10+ is transferred to side
data packet to be used or passed through.
---
The fate test file can be found here:
https://drive.google.com/file/d
From: Mohammad Izadi
HDR10+ is dynamic metadata (A/341 Amendment - SMPTE2094-40) that needs to be
decoded from ITU-T T.35 in HEVC bitstream. The HDR10+ is transferred to side
data packet to be used or passed through.
---
The fate test file can be found here:
https://drive.google.com/file/d
On Sun, Nov 15, 2020 at 12:19 AM Andreas Rheinhardt <
andreas.rheinha...@gmail.com> wrote:
> Mohammad Izadi:
> > From: Mohammad Izadi
> >
> > HDR10+ is dynamic metadata (A/341 Amendment - SMPTE2094-40) that needs
> to be decoded from ITU-T T.35 in HEVC bitstream.
From: Mohammad Izadi
HDR10+ is dynamic metadata (A/341 Amendment - SMPTE2094-40) that needs to be
decoded from ITU-T T.35 in HEVC bitstream. The HDR10+ is transferred to side
data packet to be used or passed through.
---
The fate test file can be found here:
https://drive.google.com/file/d
The fate test file can be found here:
https://drive.google.com/file/d/1jGW3f94rglLfr5WGmMQe3SEnp1YkbMRy/view?usp=drivesdk
The video file needs to be copied to fate-suite/mkv/
---
libavcodec/dynamic_hdr10_plus.c | 269 +---
libavcodec/dynamic_hdr10_plus.h |
Thank you Derek for your comment ! It’s fixed.
On Wed, Sep 7, 2022 at 6:13 AM Derek Buitenhuis
wrote:
> On 9/6/2022 10:47 PM, Mohammad Izadi wrote:
> > +if (side_data && side_data_size > 0)
> > +
> ff_write_dynamic_hdr10_plus_to_full_itu_t_t35
The fate test file can be found here:
https://drive.google.com/file/d/1jGW3f94rglLfr5WGmMQe3SEnp1YkbMRy/view?usp=drivesdk
The video file needs to be copied to fate-suite/mkv/
---
libavcodec/dynamic_hdr10_plus.c | 269 +---
libavcodec/dynamic_hdr10_plus.h |
Michael, I appreciate it if you can take a look and give me your feedback.
On Thu, Sep 8, 2022 at 9:31 AM Michael Niedermayer
wrote:
> On Wed, Sep 07, 2022 at 02:12:46PM +0100, Derek Buitenhuis wrote:
> > On 9/6/2022 10:47 PM, Mohammad Izadi wrote:
> > > +if (side_data
Michael, I appreciate it if you can take a look and give me your feedback.
Thanks,
Mohammad
On Thu, Sep 8, 2022 at 10:03 AM Mohammad Izadi wrote:
> Michael, I appreciate it if you can take a look and give me your feedback.
>
>
> On Thu, Sep 8, 2022 at 9:31 AM Michael Niederma
Thanks,
Mohammad
On Fri, Nov 20, 2020 at 5:44 AM Anton Khirnov wrote:
> Quoting Mohammad Izadi (2020-11-20 04:57:11)
> > From: Mohammad Izadi
> >
> > HDR10+ is dynamic metadata (A/341 Amendment - SMPTE2094-40) that needs
> to be decoded from ITU-T T.35 in HEVC
From: Mohammad Izadi
HDR10+ is dynamic metadata (A/341 Amendment - SMPTE2094-40) that needs to be
decoded from ITU-T T.35 in HEVC bitstream. The HDR10+ is transferred to side
data packet to be used or passed through.
---
The fate test file can be found here:
https://drive.google.com/file/d
Ian, can you please take a look into it? And if it's fine to push it.
Thanks,
Mohammad
On Mon, Nov 23, 2020 at 1:29 PM Mohammad Izadi wrote:
> From: Mohammad Izadi
>
> HDR10+ is dynamic metadata (A/341 Amendment - SMPTE2094-40) that needs to
> be decoded from ITU-T T.35
From: Mohammad Izadi
---
libavcodec/avpacket.c | 1 +
libavcodec/decode.c | 1 +
libavcodec/hevc_sei.c | 40 +++---
libavcodec/hevc_sei.h | 5 ++
libavcodec/hevcdec.c | 7 ++
libavcodec/internal.h | 9 +++
libavcodec/packet.h | 9 +++
libavcodec/utils.c| 180
1 - 100 of 115 matches
Mail list logo
