https://x265.readthedocs.io/en/default/c...dhdr10-opt
which Hybrid supports through:
"x265->Signaling->HDR-10->Add"
and
"x265->Signaling->HDR-10->optimize"
So to my knowledge Hybrid already supports HDR-10+ as far as it can atm.
If you know of a way Hybrid could improve the support for HDR-10+ I'm happy to listen to any possible improvement.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Thank you for your answer.
I'm surprised that hybrids support HDR 10+,but I don't know how to set up hybrids to get HDR 10 + format when I output video.Can you give me a simple step?
I sent you an attachment explaining SMPTE 2094.
I think it's similar to SMPTE 2084.
Quote:I don't know how to set up hybrids to get HDR 10 + format when I output video.Can you give me a simple step?
Since I haven't used x265 myself to create HDR10+, reading the x265 documentation I linked to I would say setting your HDR-10+ meta data under py pressing "x265->Signaling->HDR-10->Add" and enabling "x265->Signaling->HDR-10->optimize" should do the trick.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
https://x265.readthedocs.io/en/default/c...dhdr10-opt
which Hybrid supports through:
"x265->Signaling->HDR-10->Add"
and
"x265->Signaling->HDR-10->optimize"
So to my knowledge Hybrid already supports HDR-10+ as far as it can atm.
If you know of a way Hybrid could improve the support for HDR-10+ I'm happy to listen to any possible improvement.
Cu Selur
The two things I know are different. --dhdr10-info is a production tool for hdr10plus. --dhdr10-opt is the hdr10plus verification tool.
I would like to ask you for your comments on what I have suggested.
Quote:I would like to ask you for your comments on what I have suggested.
I already linked to the description of the options:
--dhdr10-info <filename>
Quote:Inserts tone mapping information as an SEI message. It takes as input, the path to the JSON file containing the Creative Intent Metadata to be encoded as Dynamic Tone Mapping into the bitstream.
Click here for the syntax of the metadata file. A sample JSON file is available in the downloads page
Quote:Limits the frames for which tone mapping information is inserted as SEI message. Inserts SEI only for IDR frames and for frames where tone mapping information has changed.
So with the first option you add your meta data and with the second once you tell x265 to minimize the overhead through that meta data.
Not sure how I could help more.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Hi Selur
I set up Hybrid to output several times according to the suggestion you gave me, and the output was destroyed. Specific settings I added screenshots to the email attachment. Hope to help me solve this problem.
You are using a Hybrid version from '2017.10.05.1', x265 didn't support HDR-10+ back then, so I'm not surprised that Hybrid will crash when you add custom options which aren't supported by either Hybrid or x265 at that point in time.
Just looking at the shortened changelog of x265 stable releases over at https://x265.readthedocs.io/en/default/r...notes.html, shows the last HDR-10+ related changed were in version 2.9 with release date 05/10/2018, which is a year later than the version you used!
As a side note: read the sticky on what data to provide when reporting problems/bugs.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
I'm sorry, I didn't see the version information clearly. The screenshot in the attachment below is set to output with the latest version of hybrids, but the result is the same. I don't know if there is a problem with my settings.