x265 HEVC Encoder

[benwaggoner]

Originally Posted by brumsky

Why would it disable psy rd?

Psy-rd adjusts QPs down for smoother areas and up for more complex areas of the video. SSIM as a metric weighs error in smoother areas higher than more complex areas, and thus optimize for exactly that sort of thing. Psy-rd + SSIM would likely give some kind of weird race condition.

HDR10+ delivers an optimized, high-quality HDR experience to consumers; Amazon Video is the first streaming video service that will implement HDR10+ technology to deliver a new source of high-quality digital video to Prime Video customers around the globe

LAS VEGAS--(BUSINESS WIRE)--Samsung Electronics Co., Ltd. and Amazon Video today announced the introduction of HDR10+, an updated open standard that leverages dynamic metadata to produce enhanced contrast and colors on an expanded range of televisions.

HDR10+ elevates the HDR10 open standard with the addition of Dynamic Tone Mapping. The current HDR10 standard utilizes static metadata that does not change during playback despite scene specific brightness levels. As a result, image quality may not be optimal in some scenes. For example, when a movie’s overall color scheme is very bright but has a few scenes filmed in relatively dim lighting, those scenes will appear significantly darker than what was originally envisioned by the director.

HDR10+ incorporates dynamic metadata that allows a high dynamic range (HDR) TV to adjust brightness levels on a scene-by-scene or even frame-by-frame basis. With the ability to display outstanding contrast with detailed highlights and a richer range of colors, HDR10+ produces images that are much closer to the director’s intent.

All of Samsung’s 2017 UHD TVs, including its premium QLED TV lineup, support HDR10+. In the second half of this year, Samsung’s 2016 UHD TVs will gain HDR10+ support through a firmware update.

“As an advanced HDR10 technology, HDR10+ offers an unparalleled HDR viewing experience — vivid picture, better contrast and accurate colors — that brings HDR video to life,” said Kyoungwon Lim, Vice President of Visual Display Division at Samsung Electronics. “We’re excited to work with world-class industry partners, including Amazon Video, to bring more amazing HDR content directly to our 2017 UHD TVs, including our QLED TV lineup.”

“Together with Samsung, we are excited to offer customers an enhanced viewing experience on a broad range of devices,” said Greg Hart, Vice President of Amazon Video, worldwide. “At Amazon, we are constantly innovating on behalf of customers and are thrilled to be the first streaming service provider to work with Samsung to make HDR10+ available on Prime Video globally later this year.”

The launch of the HDR10+ content continues Samsung’s and Amazon Video’s leadership in the HDR space. With the move to HDR 10+, Amazon Video is the first streaming service provider to begin development of the standard for its audiences. In May 2015, Samsung and Amazon Video brought HDR to the market using the HDR10 open standard, the first in the field. This bold and innovative advancement laid the groundwork for several HDR launches. From Hollywood film studios to global TV manufacturers, HDR10 is the most broadly used HDR standard today.

Samsung has also partnered with other industry leaders to deliver the best HDR10+ content viewing experience by establishing an HDR10+ ecosystem. Previously, Samsung collaborated with Colorfront to improve HDR10+ workflows for creative post-production mastering by using Colorfront’s Transkoder. Samsung also partnered with MulticoreWare to complete the integration of HDR10+ support in the x265 High Efficiency Video Coding (HEVC), which is available for free under an open source license, and is used by many popular commercial encoding system providers including Telestream, Haivision, and Rohde and Schwarz.

About Samsung Electronics Co., Ltd.

Samsung Electronics Co., Ltd. inspires the world and shapes the future with transformative ideas and technologies. The company is redefining the worlds of TVs, smartphones, wearable devices, tablets, digital appliances, network systems, and memory, system LSI and LED solutions. For the latest news, please visit the Samsung Newsroom at news.samsung.com.

About Amazon Video

Amazon Video is a premium on-demand entertainment service that offers customers the greatest choice in what to watch, and how to watch it. Prime Video offers thousands of movies and TV shows, including popular licensed content plus critically-acclaimed and award-winning Amazon Original Series and Movies from Amazon Studios like Transparent, The Man in the High Castle, Love & Friendship and kids series Tumble Leaf, available for unlimited streaming as part of an Amazon Prime membership. Prime Video is also now available to customers in more than 200 countries and territories around the globe at www.primevideo.com.

[Jamaika]

Originally Posted by x265_Project

Samsung and Amazon Video Deliver Next Generation HDR Video Experience With HDR10+

How write these colors HDR10+ and HDR10 in the commands for codec x265?

[LigH]

Relax and wait for new parameters in coming CLI builds... I already see proposed patches in the mailing list. But parameters are just half the fun; without matching video material, they don't fulfill a meaning.

[Midzuki]

x265.exe 2.3+40-2c6e6c9c3da7

http://www.mediafire.com/file/iymx3l...c6e6c9c3da7.7z

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;
              ^~~~

[LigH]

I tried to enable Dynamic HDR10 routines for compilation with GCC 6.3.0, but C++11 compatibility is missing in the current CMake scripts. Release postponed...

[nevcairiel]

Originally Posted by x265_Project

HDR10+ incorporates dynamic metadata that allows a high dynamic range (HDR) TV to adjust brightness levels on a scene-by-scene or even frame-by-frame basis. With the ability to display outstanding contrast with detailed highlights and a richer range of colors, HDR10+ produces images that are much closer to the director’s intent.

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.

[cojj]

I'm getting file sizes that are 25~50% bigger with the new 10bit lamda table with an identical setting (mostly preset slower).

Is this expected?

[Boulder]

Yes, it's expected. Adjust your CRF accordingly to compensate; as they say, the perceptual quality should be improved at the same bitrate.

[aymanalz]

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

[Midzuki]

Originally Posted by LigH

I tried to enable Dynamic HDR10 routines for compilation with GCC 6.3.0, but C++11 compatibility is missing in the current CMake scripts. Release postponed...

Thanks for the clarification. I stopped reading x265's CMakeLists.txt ages ago... and its readme.rst is no replacement for a (still non-existent) What's-New.txt...
In other words, HDR10 support is disabled by default, and I would never notice that by myself.

Anyway, and FWIW:

make[2]: *** [dynamicHDR10/CMakeFiles/dynamicHDR10.dir/build.make:82: dynamicHDR10/CMakeFiles/dynamicHDR10.dir/json11/json11.cpp.obj] Error 1
make[1]: *** [CMakeFiles/Makefile2:147: dynamicHDR10/CMakeFiles/dynamicHDR10.dir/all] Error 2
make: *** [Makefile:117: all] Error 2
cp: cannot stat 'libx265.a': No such file or directory

[Barough]

x265 v2.3+41-6dc49dcff6da (MSYS/MinGW, GCC 6.3.0, 32 & 64bit 8/10/12bit multilib EXEs)

x265 [info]: HEVC encoder version 2.3+41-6dc49dcff6da
x265 [info]: build info [Windows][GCC 6.3.0][32 bit/64 bit] 8bit+10bit+12bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX AVX2 FMA3 LZCNT BMI2

https://bitbucket.org/multicoreware/x265/commits/branch/default

[nevcairiel]

Originally Posted by Midzuki

In other words, HDR10 support is disabled by default, and I would never notice that by myself.

Its only about HDR10+ (not ordinary HDR10), and its a brand new feature which clearly still has issues even building properly everywhere, so it might get enabled by default later.

[need4speed]

Dumb question on encoding 10bit:
Do I need to enable both depth10 AND profile main10?
Sorry but have tried to read all posts and a couple of white papers, this to improve banding and still it's not clear.
Thanks in advance!
So new 10bit table is active in latest builds (.40 and .41)?

[sneaker_ger]

Originally Posted by need4speed

Dumb question on encoding 10bit:
Do I need to enable both depth10 AND profile main10?

If you set output depth to 10 bit it will automatically choose main10 profile. If you have a build that's only compiled for 10 bit you don't have to set anything at all.
Just check the output in MediaInfo and look at the x265 log if you are not sure.

Originally Posted by need4speed

So new 10bit table is active in latest builds (.40 and .41)?

Yes, the new tables for 10 and 12 bit have arrived.

[LigH]

Regarding Dynamic HDR10: It is not enabled by default, but a CMake switch is available. I tried to enable this supporting switch. The resulting errors point at C++11 support not yet being enabled in the MSYS/GCC branch of the make scripts, possibly just forgotten when another preferred compiler of a developer supports it per default.

Originally Posted by nevcairiel

Its only about HDR10+ (not ordinary HDR10), and its a brand new feature which clearly still has issues even building properly everywhere, so it might get enabled by default later.

To get the HDR10+ capability to market more quickly, the developers used Standard Template Libraries. As you noticed, STLs may introduce compiler compatibility issues, so for now, compiling HDR10+ in x265 is off by default. We expect the HDR10+ code to be updated to avoid the use of STLs, so that it can be compiled in x265 by default.

[need4speed]

Originally Posted by sneaker_ger

If you set output depth to 10 bit it will automatically choose main10 profile. If you have a build that's only compiled for 10 bit you don't have to set anything at all.
Just check the output in MediaInfo and look at the x265 log if you are not sure.


Yes, the new tables for 10 and 12 bit have arrived.

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

HDR10 is a static HDR system defined by SMPTE 2084 (Electro Optical Transfer Function, or EOTF) and SMPTE 2086 (HEVC metadata). By static, we mean that the EOTF (the curve that defines how to map color sample values in the HEVC bitstream to luminance levels on the display) is the same for the entire video. Static HDR works, but it isn't ideal because with only 10 bits (1024 values) to map a very wide range of luminance levels, colorists have to pick a single setting that works well on average for the whole title. This means that brighter than average scenes may have regions that are washed out, and darker than average scenes might have regions where it is hard to distinguish what is happening in the shadows.

HDR10+ is a dynamic HDR system defined by the SMPTE 2094-40 standard. It lets colorists adjust the EOTF on a scene-by-scene basis. There are 4 flavors of SMPTE 2094...
•2094-1 –the core definitions document
•2094-10 –[Dolby Vision] metadata for a tone mapping based on the source content characteristics and colorist adjustments.
•2094-20 –[Philips] metadata for a color transform based on a creatively set tone mapping curve and a luminance dependent saturation gain curve.
•2094-30 –[Technicolor] metadata for reference-based color volume remapping, derived from two grades of the same content.
•2094-40 –[Samsung HDR10+] metadata for tone mapping and color saturation based on mastering and target displays peak luminances and content characteristics.

x265's HDR10+ support was contributed by Samsung. It provides the capability to parse a JSON file containing metadata generated by Samsung's tone mapping software. Samsung is working with content creators, color grading software developers and content distributors to enable HDR10+ tone mapping (generating the JSON file).

If you want to know more about Dynamic HDR, I suggest ...
https://www.smpte.org/sites/default/...V2-Handout.pdf
http://www.ste-ca.org/images/STE_Pre..._Apil_2016.pdf
http://set6.tempsite.ws/eventos/pale..._expo_2016.pdf

[Ma]

Originally Posted by LigH

Regarding Dynamic HDR10: It is not enabled by default, but a CMake switch is available. I tried to enable this supporting switch. The resulting errors point at C++11 support not yet being enabled in the MSYS/GCC branch of the make scripts, possibly just forgotten when another preferred compiler of a developer supports it per default.

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