x265 HEVC Encoder

[brumsky]

Originally Posted by need4speed

Thanks!
Was wondering about 10bits tables because my latest converted file has decreased in terms of size keeping the same crf. Have read it has happened the opposite so wondering how the story was.
Besides with regards of earlier 10bit encoded speed time latest versions seem to be a bit faster, around 2 fps increase in medium preset with some tweaks

Inviato dal mio GT-N7100 utilizzando Tapatalk

I've noticed an increase in speed as well. Much less but I think it is because I use modified placebo settings. Also, files initially seemed to be larger - 2000kbps ish increase.

[Midzuki]

Originally Posted by Ma

If you change in source/CMakeLists.txt line 190 from
add_definitions(-std=gnu++98)
to
add_definitions(-std=gnu++11)
you can compile x265 with '-DENABLE_DYNAMIC_HDR10=ON'.

I don't know if it make sense only in 10-bit depth or in any bit depth.
Compiled 10-bit x265 with dhdr10 for Windows (64-bit and 32-bit):
www.msystem.waw.pl/x265/x265-10hdr.7z

Many thanks for the info
Now the thing gets compiled.
BUT still with tons of warnings

FWIW: I disabled HDR10+ only for the 8-bit section in my new multilib building script.

[need4speed]

Originally Posted by brumsky

I've noticed an increase in speed as well. Much less but I think it is because I use modified placebo settings. Also, files initially seemed to be larger - 2000kbps ish increase.

Trying another session right now. Will get back but at the moment confirming the bitrate is lower than before, same everything

Inviato dal mio GT-N7100 utilizzando Tapatalk

[Midzuki]

Hmmm, commit 7f77e66 says:

compilation fix in dhdr10

However GCC 6.3.0 still returns TONS of warnings.
Also, CMakeLists.txt hasn't been fixed.

Unless you are encoding content that has been mastered with Samsung's tone mapping system, and you have the JSON file with the HDR metadata, you don't need to build x265 with this feature. You'll get errors if you're not using the same compiler that this feature was targeted to. I'll ask our development team to clarify which compilers are supported by this feature today.

[Midzuki]

Originally Posted by x265_Project

Unless you are encoding content that has been mastered with Samsung's tone mapping system, and you have the JSON file with the HDR metadata, you don't need to build x265 with this feature. You'll get errors if you're not using the same compiler that this feature was targeted to. I'll ask our development team to clarify which compilers are supported by this feature today.

Actually, the warnings have nothing to do with the Dynamic HDR support. The quote below is only a tiny sample of what I am talking about.

Originally Posted by Midzuki

............

NOTICE:

[ 75%] Building CXX object encoder/CMakeFiles/encoder.dir/sei.cpp.obj
D:/KOMPILES/MCW/x265/source/encoder/sei.cpp: In member function
'void x265::SEI::write(x265::Bitstream&, const x265::SPS&)':
D:/KOMPILES/MCW/x265/source/encoder/sei.cpp:51:18:
warning: declaration of 'type' shadows a previous local [-Wshadow]
uint32_t type = m_payloadType;
                  ^~~~
D:/KOMPILES/MCW/x265/source/encoder/sei.cpp:41:14: note: shadowed declaration is here
uint32_t type = m_payloadType;
              ^~~~

Originally Posted by Midzuki

Actually, the warnings have nothing to do with the Dynamic HDR support. The quote below is only a tiny sample of what I am talking about.

Sorry Midzuki! There were a few messages about building x265 with Dynamic HDR turned on. I thought you were trying this also.

[benwaggoner]

Originally Posted by nevcairiel

Is this an official HEVC standard, or a proprietary invention by Amazon and Samsung?
Any specifications about the SEI messages, their intepretation, and how to send them to a TV over HDMI (specifically, does this require HDMI 2.1)?

New tech is nice and all, knowing how to use it would be even nicer.

It is SMPTE standard 2094-40.

Generating the metadata is pretty complex, and that's not in x265. Colorfront's Transkoder product can generate the data from a source file. x265 supports incorporating the metadata into an encoded HDR-10 HEVC bitstream.

[nevcairiel]

Originally Posted by benwaggoner

It is SMPTE standard 2094-40.

Generating the metadata is pretty complex, and that's not in x265. Colorfront's Transkoder product can generate the data from a source file. x265 supports incorporating the metadata into an encoded HDR-10 HEVC bitstream.

I'm not interested in generating the data, just consuming it to various degrees, possibly to transmit it to a TV through HDMI down the line, have to at least try to keep PCs able to use those new formats.
For transmission, thats apprently in CTA-861-G (ie. the HDMI 2.0/2.1 standard), perhaps some software features can be supported on older HDMI interfaces by firmware updates (like dynamic metadata).

[benwaggoner]

Originally Posted by nevcairiel

I'm not interested in generating the data, just consuming it to various degrees, possibly to transmit it to a TV through HDMI down the line, have to at least try to keep PCs able to use those new formats.
For transmission, thats apprently in CTA-861-G (ie. the HDMI 2.0/2.1 standard), perhaps some software features can be supported on older HDMI interfaces by firmware updates (like dynamic metadata).

I'm not sure exactly how transport over HDMI will work and with what requirements. So far all the demonstrations have been on devices with integrated screens.

[Jamaika]

Originally Posted by nevcairiel

I'm not interested in generating the data, just consuming it to various degrees, possibly to transmit it to a TV through HDMI down the line, have to at least try to keep PCs able to use those new formats.
For transmission, thats apprently in CTA-861-G (ie. the HDMI 2.0/2.1 standard), perhaps some software features can be supported on older HDMI interfaces by firmware updates (like dynamic metadata).

Interesting thought. I don't know how it is, but I think @sneaker once wrote that HDR is also for 8bit video in VP9 codec. It seems to me that google policy has also changed. The site is only about 10bit movies.
https://support.google.com/youtube/answer/7126552?hl=en
http://www.androidcentral.com/new-nv...-hdr-streaming
https://www.heise.de/newsticker/meld...t-3488970.html

Dolby Vision also works with the older HDMI 1.4a standard, while HDR10 requires HDMI 2.0. Dolby Vision is backwardly compatible to HDR10, but it's not clear if it will work with the new standard HDR10+.
But what exactly does that mean? HDR10/HDR10+ is the current industry standard for HDR in consumer televisions. This first-generation “open” format technology is the starting point for High Dynamic Range, which needs a compatible interface—either HDMI 2.0a/HDMI 2.1 or Internet connection...
Make sure your TV and AV receiver firmware are up to date. Many newer TVs and devices can take updates—if you find that it doesn't support some 4K or HDR features, a TV or receiver firmware update may resolve the problem. Check your TV or device manual to see how to update the firmware.

Edit: Who knows what this is for the Dynamic Range Pro for HDR10? Is it also set in HEVC codecs?

[benwaggoner]

Originally Posted by Jamaika

Interesting thought. I don't know how it is, but I think @sneaker once wrote that HDR is also for 8bit video in VP9 codec. It seems to me that google policy has also changed. The site is only about 10bit movies.

Doing some degree of HDR in 8-bit is possible. I had some working prototypes a couple of years ago. But using the full PQ range isn't feasible without a lot of banding. 10-bit is definitely required to do "standard" HDR over HDMI.

Edit: Who knows what this is for the Dynamic Range Pro for HDR10? Is it also set in HEVC codecs?

The HDR10+/SMPTE 2094-40 metadata is inside the HEVC bitstream as SEI messages. I don't know if there is a final spec for transmission over HDMI.

[Jamaika]

Originally Posted by benwaggoner

The HDR10+/SMPTE 2094-40 metadata is inside the HEVC bitstream as SEI messages. I don't know if there is a final spec for transmission over HDMI.

Thanks for the answer. I ask curiosity, because it amazes me advertising SONY. We have 10x more contrast range products than Dynamic Range HDR10 called Dynamic Range Pro which aren't HDR10+. Where are these extra information extracted from the metadata?
It begins to be it for me even more puzzling.

[nevcairiel]

Sony's "Dynamic Range Pro" is not "dynamic HDR", its just static HDR with some proprietary contrast booster.

So far there have been 4 competing dynamic HDR concepts grouped under SMPTE 2094
2094-10: Dolby Vision
2094-20: Phillips
2094-30: Technicolor (used by LG, IIRC)
2094-40: Samsung

Its a rather unfortunate situation that we have 4 competing concepts already, and possibly more in the future.
We'll have to see how they differ and if TVs will be able to just handle content in all of the formats.

From what I could turn up, the next release of the HEVC spec (October 2017) should also encorporate the SEI messages for these officially.
I also found information that claims that ST 2094-10 and ST 2094-20 are optional parts of the UHD Blu-ray Specification, but the other two didn't make it in at all.

Transmission over HDMI will likely require HDMI 2.1 for all variants of SMTPE ST 2094 - with the exception of Dolbys proprietary transmission format, which requires full hardware support on both ends.

[Sagittaire]

I want make direct comparison with HT On and HT Off.

It's possible to change the wpp raws number in x265?

[dipje]

Originally Posted by aymanalz

Has the 10 bit lambda table been incorporated into the latest build? If so, what build number?

In the bitbucket of multicoreware (official x265 repo I'm guessing) I see the commit of the new lambda tables (10bit / 12bit) being commited on the 13th of april, both in the 'default' branch and the 'stable' branch.

I'm guessing any build from that point on has it?
Or is the commit I'm seeing still something that needs to be approved?

[Selur]

I'm guessing any build from that point on has it?

not exactly, it was merged to default branch two days ago, and since then any new build includes the new lambda tables.

[Ma]

Originally Posted by Sagittaire

I want make direct comparison with HT On and HT Off.

It's possible to change the wpp raws number in x265?

To simulate encoding with CPU with different numbers of logical cores, there are needed two options: '--pools <N>' and '-F <NF>' where N is number of logical cores that you want to simulate and NF is number of frame threads that x265 uses for N logical cores -- formula is at:
https://bitbucket.org/multicoreware/...ncoder.cpp-137

Example: if you want to simulate 4 logical cores system, use
--pools 4 -F 2

for 8 cores:
--pools 8 -F 3

for 20 cores:
--pools 20 -F 5

for 32 cores and 1080p source movie:
--pools 32 -F 6

wpp you can only turn on or off (for '--no-wpp' option number of frame threads are min(logical cores, 16) for high resolution source).

[Natty]

how to use 10 bit lambda table

[nevcairiel]

Originally Posted by Natty

how to use 10 bit lambda table

Its always used when you encode 10-bit content, and any builds of the last few days should have the new table.