HDR10+ General Discussion

[SeeMoreDigital]

As some of you may already know, the first UHD disc's encoded with HDR10+ have been released.

Currently only the newest Panasonic and Samsung devices support this version of 'dynamic' HDR, with the OPPO UDP-20x range of players and its clones to follow.

However, a guy over on the AVS forum has managed to back-up two of the new HDR10+ disc releases (https://www.avsforum.com/forum/39-networking-media-servers-content-streaming/2942740-ripping-uhd-4k-discs-makemkv-instructions-how-50.html#post57269248) but has encountered an interesting issue that requires more analysis, help and feed-back from others.

Long story short, when the (HEVC/HDR10+).m2ts file is accessed/played outside its original UHD disc folder-set, not only is the HDR10+ meta-data/flag lost, the basic HDR10 information is lost too. Meaning no HDR at all. And, re-muxing the HEVC/HDR10+ elementary video stream into the MKV container does not work either :eek:

Can anybody here offer any help?

[nevcairiel]

Which titles use HDR10+? AVSforum didnt seem to say.

[SeeMoreDigital]

Which titles use HDR10+? AVSforum didnt seem to say.Not many...

Here's a link to the current/proposed movies: List of UHDs that contain HDR10+ (https://forum.blu-ray.com/showthread.php?t=300877)


Cheers and thanks for your interest...

[sneaker_ger]

Since HDR10+ wasn't in the original spec, how do they achieve backwards-compability? Or do all UltraHD Blu-Ray players receive firmware updates for it (not that many players exist)? Maybe the movie is stored twice, e.g. one SDR and one HDR10+ version and the remuxing software accesses the SDR one?

[nevcairiel]

Specs evolve over time. They may just have two discs in the package, like some 3D movies. The 3D disc never played on non-3D players, they just had to use the other one.

[foxyshadis]

Since HDR10+ wasn't in the original spec, how do they achieve backwards-compability? Or do all UltraHD Blu-Ray players receive firmware updates for it (not that many players exist)? Maybe the movie is stored twice, e.g. one SDR and one HDR10+ version and the remuxing software accesses the SDR one?

HDR10 is mandatory and basically backwards compatible. In practice, the only thing a non-HDR10+ device will lose is the occasional retina-searing highlight, since the HDR10 average will be set to meet most scenes' needs.

[TomV]

Since HDR10+ wasn't in the original spec, how do they achieve backwards-compability? Or do all UltraHD Blu-Ray players receive firmware updates for it (not that many players exist)? Maybe the movie is stored twice, e.g. one SDR and one HDR10+ version and the remuxing software accesses the SDR one?
HDR10+ is HDR with additional color volume metadata (in SEI messages) to enable the display device to better map the dynamic range of each scene to the display. The encoded video is exactly the same for HDR and HDR10+.

[sneaker_ger]

I see. I wasn't sure what OP meant by "Meaning no HDR at all". Guess he meant the metadata was lost but the encoding is HDR (i.e. you see the washed out colors).

But if all the metadata is simply in SEI messages it would be unusual for muxers to drop them.

[nevcairiel]

I got my hands on one of those discs, and just playing the straight up m2ts file produces proper HDR10 playback. So if ripping to MKV screws that up, then the ripping tool removed something it was not meant to.
I'll peek at the HDR10+ metadata later.

The only odd thing is that the disc claims to be 60GB in size, but the main m2ts is just 22GB, I wonder if something is wrong with the decryption or reading of the disc.
But the movie seems to be all there regardless. Its only 46 minutes (A Beautiful Planet documentary), so maybe the 60GB is just a fluke in being the max size it could be.

[SeeMoreDigital]

I got my hands on one of those discs, and just playing the straight up m2ts file produces proper HDR10 playback...That's interesting. I'll report that back.

So if ripping to MKV screws that up, then the ripping tool removed something it was not meant to.
I'll peek at the HDR10+ metadata later.Did you use MakeMKV to do the back-up to .mkv. If so, I wonder if the loss of the HDR10+ meta-data is due to limitations in their version of their Matroska muxer.

Perhaps, Mosu's Matroska muxer is able to do a better job. I have found this to be the case with regular Blu-ray and UHD disc back-ups!

[nevcairiel]

A MakeMKV MKV file of that disc also preserves the HDR10 charecteristics.

[SeeMoreDigital]

A MakeMKV MKV file of that disc also preserves the HDR10 charecteristics.Really... Does it trigger the HDR10 flag in your hardware player and/or supporting TV?

[nevcairiel]

I don't have such a thing. But my software PC player still reports full HDR just like normal. Hardware playback failure can have a million reasons.
But clearly enough data is preserved to indicate its at least HDR10.

[SeeMoreDigital]

I don't have such a thing. But my software PC player still reports full HDR just like normal. Hardware playback failure can have a million reasons.This is most confusing...

Which HDR10+ disc did you end up purchasing Nev, so I can buy the same one?

In the meantime... Are you able to post a short MKV and/or M2TS sample?

[nevcairiel]

I finally got around to looking at the metadata (well a couple days ago actually), and the .mkv rip from MakeMKV does also contain the HDR10+ SEI metadata. So its all there. If some player cannot play that in HDR10 or HDR10+, then its entirely up to the player.

PS:
I got the A Beautiful Planet documentary, as mentioned above already.

[SeeMoreDigital]

I finally got around to looking at the metadata (well a couple days ago actually), and the .mkv rip from MakeMKV does also contain the HDR10+ SEI metadata. So its all there. If some player cannot play that in HDR10 or HDR10+, then its entirely up to the player.

PS:
I got the A Beautiful Planet documentary, as mentioned above already.Thanks for looking into this, I'll pass the information onto OPPO.

I recently purchased 'A Beautiful Planet' too (via Amazon UK). It's currently on its way from the US of A :eek:

[benwaggoner]

I finally got around to looking at the metadata (well a couple days ago actually), and the .mkv rip from MakeMKV does also contain the HDR10+ SEI metadata. So its all there. If some player cannot play that in HDR10 or HDR10+, then its entirely up to the player.
Anything that doesn't change the video elementary stream should retain HDR10+ metadata.

[SeeMoreDigital]

I wonder if MKV muxer that MakeMKV GUI uses is doing something weird?!

[SeeMoreDigital]

Looks like we're getting a bit closer...

A new AVS forum member, going by the name avsforum2 has just posted the following: -
I have an MKV file and it must carry HDR10+ since when I play it directly on the internal TV player (Panasonic FZ800) it triggers HDR10+ on the TV, when I play the same file on Oppo (beta) it don´t see any HDR information and send out SDR BT.2020 to the TV.

Link: https://www.avsforum.com/forum/149-blu-ray-players/2676801-official-oppo-udp-203-owner-s-thread-869.html#post57398770

[Selur]

Anyone got a link to a HDR-10+ sample file?

[SeeMoreDigital]

Anyone got a link to a HDR-10+ sample file?I've been trying to obtain some official samples for months but without success.

I now hoping some might shake loose after CES...

[hajj_3]

These UHD blurays have HDR10+ on them: https://forum.blu-ray.com/showthread.php?t=300877

You could rip them yourself if you have a specific uhd bluray drive and ripping software. Alternatively you would need to find an uncompressed rip of these online somewhere.

[Selur]

@hajj_3: looking for a legally available sample. (uncompressed and untouched, a remux might not work either)

[hajj_3]

I have managed to cut a 24 second 93MB sample of the uncompressed UHD bluray of Robin Hood, pm me if anyone wants a link to download it. Mediainfo detects it as having HDR10 as i think mediainfo can't detect HDR10+ at the moment. Please note that the low bitrate is because there isn't much movement in some of the scene. The full movie has an average video bitrate of 48.3Mb/s.

Format : Matroska
Format version : Version 4
File size : 92.3 MiB
Duration : 24 s 952 ms
Overall bit rate mode : Variable
Overall bit rate : 31.0 Mb/s
Movie name : Robin Hood Theatrical 4K
Encoded date : UTC 2019-01-12 19:37:28
Writing application : mkvmerge v30.1.0 ('Forever And More') 64-bit
Writing library : libebml v1.3.6 + libmatroska v1.4.9

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Commercial name : HDR10
Format profile : Main 10@L5.1@High
Codec ID : V_MPEGH/ISO/HEVC
Duration : 24 s 942 ms
Bit rate : 23.1 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.116
Stream size : 68.8 MiB (75%)
Writing library : ATEME Titan File 3.8.16 (4.8.16.0)
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 1001 cd/m2
Maximum Frame-Average Light Level : 328 cd/m2

Audio
ID : 2
Format : DTS XLL
Format/Info : Digital Theater Systems
Commercial name : DTS-HD Master Audio
Codec ID : A_DTS
Duration : 24 s 950 ms
Bit rate mode : Variable
Bit rate : 7 888 kb/s
Channel(s) : 8 channels
Channel layout : C L R LFE Lb Rb Lss Rss
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossless
Delay relative to video : 2 ms
Stream size : 23.5 MiB (25%)
Title : DTS:X 7.1
Language : English
Default : Yes
Forced : No

Text #1
ID : 3
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Bit rate : 0 b/s
Count of elements : 0
Stream size : 0.00 Byte (0%)
Title : English (SDH)
Language : English
Default : No
Forced : No

Text #2
ID : 4
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Bit rate : 0 b/s
Count of elements : 0
Stream size : 0.00 Byte (0%)
Title : French
Language : French
Default : No
Forced : No

Text #3
ID : 5
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Bit rate : 0 b/s
Count of elements : 0
Stream size : 0.00 Byte (0%)
Title : Japanese
Language : Japanese
Default : No
Forced : No

Text #4
ID : 6
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Bit rate : 0 b/s
Count of elements : 0
Stream size : 0.00 Byte (0%)
Title : Portuguese (Brazilian)
Language : Portuguese
Default : No
Forced : No

Text #5
ID : 7
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Bit rate : 0 b/s
Count of elements : 0
Stream size : 0.00 Byte (0%)
Title : Spanish (Latin American)
Language : Spanish
Default : No
Forced : No

Menu
00:00:00.000 : en:Difficult Times
00:00:04.379 : en:Hard News

[SeeMoreDigital]

I have managed to cut a 24 second sample of the uncompressed UHD bluray of Robin Hood, pm me if anyone wants a link to download it. Mediainfo detects it as having HDR10 as i think mediainfo can't detect HDR10+ at the moment. Please note that the low bitrate is because there isn't much movement in some of the scene. The full movie has an average video bitrate of 48.3Mb/s.I didn't think that Robin Hood (2018) disc was available until mid Feb. And from what I understand, it should also contain a Dolby Vision meta-data layer.

I'd quite like a link please...

[mini-moose]

I have managed to cut a 24 second 93MB sample of the uncompressed UHD bluray of Robin Hood

Is this not the Robin Hood from 2010? Don't think HDR10+ appeared on UHD discs till end of 2018.

[hajj_3]

Is this not the Robin Hood from 2010? Don't think HDR10+ appeared on UHD discs till end of 2018.

ahhh, it is from 2010. It was released on uhd bluray around 3-4 months ago. My mistake. Crazy that they made a new film with the same name just 8 years later.

[hajj_3]

I have managed to make a 20 second 104MB sample of 'Bad Times at the El Royale' UHD Bluray, which has HDR10+ on, mediainfo detects it as HDR10 but i don't think it that hasn't been updated to detect HDR10+. https://www.blu-ray.com/movies/Bad-Times-at-the-El-Royale-4K-Blu-ray/217590/#Review

PM me if you want a link to the sample to test.

Format : Matroska
Format version : Version 4
File size : 104 MiB
Duration : 20 s 2 ms
Overall bit rate mode : Variable
Overall bit rate : 43.7 Mb/s
Encoded date : UTC 2019-01-13 23:46:55
Writing application : mkvmerge v30.1.0 ('Forever And More') 64-bit
Writing library : libebml v1.3.6 + libmatroska v1.4.9

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Commercial name : HDR10
Format profile : Main 10@L5.1@High
Codec ID : V_MPEGH/ISO/HEVC
Duration : 19 s 979 ms
Bit rate : 36.4 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (23976/1000) FPS
Original frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.183
Stream size : 86.6 MiB (83%)
Writing library : ATEME Titan File 3.9.0 (4.9.0.0)
Language : English
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 1000 cd/m2

Audio #1
ID : 2
Format : MLP FBA 16-ch
Format/Info : Meridian Lossless Packing FBA with 16-channel presentation
Commercial name : Dolby TrueHD with Dolby Atmos
Codec ID : A_TRUEHD
Duration : 19 s 978 ms
Bit rate mode : Variable
Bit rate : 6 123 kb/s
Maximum bit rate : 8 373 kb/s
Channel(s) : 8 channels
Channel layout : L R C LFE Ls Rs Lb Rb
Sampling rate : 48.0 kHz
Frame rate : 1 200.000 FPS (40 SPF)
Compression mode : Lossless
Stream size : 14.6 MiB (14%)
Language : English
Default : Yes
Forced : No
Number of dynamic objects : 13
Bed channel count : 1 channel
Bed channel configuration : LFE

Audio #2
ID : 3
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : A_AC3
Duration : 20 s 0 ms
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Bit depth : 16 bits
Compression mode : Lossy
Delay relative to video : 2 ms
Stream size : 1.53 MiB (1%)
Language : English
Service kind : Complete Main
Default : No
Forced : No

Audio #3
ID : 4
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : A_AC3
Duration : 20 s 0 ms
Bit rate mode : Constant
Bit rate : 448 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Bit depth : 16 bits
Compression mode : Lossy
Delay relative to video : 2 ms
Stream size : 1.07 MiB (1%)
Language : English
Service kind : Complete Main
Default : No
Forced : No

Text #1
ID : 5
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 18 s 143 ms
Bit rate : 65.9 kb/s
Count of elements : 15
Stream size : 146 KiB (0%)
Language : frs
Default : Yes
Forced : No

Text #2
ID : 6
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 6 s 548 ms
Bit rate : 76.1 kb/s
Count of elements : 4
Stream size : 60.8 KiB (0%)
Language : Spanish
Default : No
Forced : No

Text #3
ID : 7
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 6 s 548 ms
Bit rate : 60.7 kb/s
Count of elements : 4
Stream size : 48.5 KiB (0%)
Language : French
Default : No
Forced : No

Text #4
ID : 8
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Bit rate : 0 b/s
Count of elements : 0
Stream size : 0.00 Byte (0%)
Language : French
Default : No
Forced : No

Menu
00:00:00.000 : :CapÃ*tulo 09

[Selur]

https://patchwork.ffmpeg.org/patch/11674/ -> Nice, seems like someone is working of decoding support for HDR-10+ in ffmpeg. :)

[nevcairiel]

"Decoding" is a bit much. Reading the metadata is trivial. Doing something useful with it, that's the real challenge.

[SeeMoreDigital]

Yesterday I transferred hajj_3's 20 second sample to a USB pen-drive and got very different playback results using my LG television and OPPO.

On my LG television, although it does not support HDR+, the sample played and displayed regular HDR (HDR10). Which is as expected.
But on my OPPO, which does support HDR10+, although the sample played, no flavour of HDR (HDR10) was detected at all by the player and sent to the TV.

I also tried de-muxing the streams and re-muxing them to different containers and got the same results...

[benwaggoner]

"Decoding" is a bit much. Reading the metadata is trivial. Doing something useful with it, that's the real challenge.
Although it is easier to do good tone mapping with HDR10+ metadata than without it, as the tone mapper can "look into the future" and read the metadata for future frames and thus can know how much headroom to leave per-shot.

[quietvoid]

Hi, since HDR10+ titles started coming out I've been working on extracting the metadata from them.
For now the only purpose is to generate JSON files that x265 can use when reencoding these sources.

So I've made a tool which does just that, extracts the metadata and creates a compatible JSON file for x265.
It outputs a .log file with the raw bytes of every SEI message as well as a .json file with metadata formatted for HDR10+ LLC (not legacy).
HDR10+ LLC is what most current titles have been formatted like for now.

The tool is available on GitHub here: https://github.com/quietvoid/hdr10plus_parser
HDR10+ samples are available in the assets folder, they're also used for regression tests.

Hopefully this is useful for anyone wanting to retain HDR10+ after reencode as well as developers who have ideas about reusing the metadata on decode :)

[hajj_3]

Hi, since HDR10+ titles started coming out I've been working on extracting the metadata from them.
For now the only purpose is to generate JSON files that x265 can use when reencoding these sources.

So I've made a tool which does just that, extracts the metadata and creates a compatible JSON file for x265.
It outputs a .log file with the raw bytes of every SEI message as well as a .json file with metadata formatted for HDR10+ LLC (not legacy).
HDR10+ LLC is what most current titles have been formatted like for now.

The tool is available on GitHub here: https://github.com/quietvoid/hdr10plus_parser
HDR10+ samples are available in the assets folder, they're also used for regression tests.

Hopefully this is useful for anyone wanting to retain HDR10+ after reencode as well as developers who have ideas about reusing the metadata on decode :)

Nice, hopefully you can work with the mediainfo developer(s) to add detection support to that. Does Mkvtoolnix use a mediainfo dll or do they do their own detection as that can't detect hdr10+ either. Would love to see those add detection support.

[FranceBB]

Hi, since HDR10+ titles started coming out I've been working on extracting the metadata from them.
For now the only purpose is to generate JSON files that x265 can use when reencoding these sources.

So I've made a tool which does just that, extracts the metadata and creates a compatible JSON file for x265.
It outputs a .log file with the raw bytes of every SEI message as well as a .json file with metadata formatted for HDR10+ LLC (not legacy).
HDR10+ LLC is what most current titles have been formatted like for now.

The tool is available on GitHub here: https://github.com/quietvoid/hdr10plus_parser

This is exactly what I was looking for!
Thank you very much indeed; it really comes in handy. :D

[mini-moose]

So I've made a tool which does just that, extracts the metadata and creates a compatible JSON file for x265.

Very nice! Thanks for this tool.

Would this only work on an elementary stream (.hevc)?

Also, is it needed to use the --dhdr10-opt switch? I noticed your samples didn't use that.

[quietvoid]

Very nice! Thanks for this tool.

Would this only work on an elementary stream (.hevc)?

Also, is it needed to use the --dhdr10-opt switch? I noticed your samples didn't use that.Yes the input has to be raw HEVC.

For the x265 --dhdr10-opt switch, as far as I lnow it breaks the specifications for proper SMPTE 2094-40 metadata. It (doc (https://www.atsc.org/wp-content/uploads/2018/02/S34-301r2-A341-Amendment-2094-40.pdf)) states that every frame should have a SEI message for it.
And all the titles I have tested have the same number of metadata messages as frames, you can verify the number of lines in the .log file created.

However the samples are encoded with only metadata for the first frame, and are only useful to verify the metadata stays the same as the source after reencoding.
So essentially to make sure the bytes are interpreted correctly in the JSON.

[sneaker_ger]

It states that every frame should have a SEI message for it.
What is "it"? Where can I read "it"?

[quietvoid]

What is "it"? Where can I read "it"?https://www.atsc.org/wp-content/uploads/2018/02/S34-301r2-A341-Amendment-2094-40.pdf
Specifically this part:
The syntax and semantics for payload user_data_registered_itu_t_t35() shall be as specified in [ref
to new Annex described below] section [ref to new Annex, Section 1 described below]. Where
present the corresponding NAL unit type shall be set equal to PREFIX_SEI_NUT.
If a 2094-40 metadata message is present, the following constraints shall apply:
• The 2094-40 metadata message shall be associated with every access unit of the bitstream.
If this message is present, it shall only be present once per access unit

[nevcairiel]

To be fair, this is the ATSC broadcast standard, its not the authoritative standard on all 2094-40 usage, and there is no clear indication that for example Blu-ray discs require the same.

[buratino]

hi,

i create json data in DaVinci Resolve for my hdr video.
How to implement the JSON data in the video?

[benwaggoner]

--dhdr10-info <foo>.json

[buratino]

--dhdr10-info <foo>.json

sorry...
I just started to study this topic. what utility should i use?

[benwaggoner]

sorry...
I just started to study this topic. what utility should i use?
That's the syntax for x265.exe. That will inject the JSON into the SEI messages while encoding the video.

[mini-moose]

That's the syntax for x265.exe. That will inject the JSON into the SEI messages while encoding the video.

Do you have definite opinion if this should be used with --dhdr10-opt or not?

[mariner]

Hi, since HDR10+ titles started coming out I've been working on extracting the metadata from them.
For now the only purpose is to generate JSON files that x265 can use when reencoding these sources.

So I've made a tool which does just that, extracts the metadata and creates a compatible JSON file for x265.
It outputs a .log file with the raw bytes of every SEI message as well as a .json file with metadata formatted for HDR10+ LLC (not legacy).
HDR10+ LLC is what most current titles have been formatted like for now.

The tool is available on GitHub here: https://github.com/quietvoid/hdr10plus_parser
HDR10+ samples are available in the assets folder, they're also used for regression tests.

Hopefully this is useful for anyone wanting to retain HDR10+ after reencode as well as developers who have ideas about reusing the metadata on decode :)

Thank you, quietvoid.

[Selur]

okay so far we can:

verify whether a HEVC file contains HDR-10+ dynamic data (using hdr10plus_parser)
extract existing HDR-10+ dynamic data from a file (using hdr10plus_parser + ffmpeg, in case the video isn't available as raw video)
convert to HDR-10+ using x265 and the corresponding dynamic data

tested the above and they all seem to work fine.

Next question is: How to playback such content on a pc?

Cu Selur

Ps.: Thanks to quietvoid for hdr10plus_parser. Really useful! :)

[nevcairiel]

I'm working on making the HDR10+ metadata available to a renderer when decoding with LAV Video, so eg. madVR could then make use of it. madshi has already expressed interest in making use of it. A timeframe for that is however not available.

[Selur]

@nevcairiel: Thanks for the info. Happy to hear someone is working on it. :)

[jlpsvk]

Another question. Can we crop video, while encoding with HDR10+ metadata?