Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > Video Encoding > High Efficiency Video Coding (HEVC)

Reply
 
Thread Tools Search this Thread Display Modes
Old 16th June 2017, 11:47   #5401  |  Link
iwod
Registered User
 
Join Date: Apr 2002
Posts: 756
I cant believe it has been 4 - 5 years since x265 first appeared on Doom9! And I cant believe I had to wait all these years for wide spread support and uses, starting with Apple. God I am Old!

Anyway, I wanted to ask, how far is x265 being developed in terms of Video Quality? Are we in the late stage of development where we are focusing on encoding speed and shouldn't expect any more dramatic improvement in Video Quality? Pretty much like x264 in 2011 onwards.
iwod is offline   Reply With Quote
Old 16th June 2017, 11:54   #5402  |  Link
LigH
German doom9/Gleitz SuMo
 
LigH's Avatar
 
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,752
More or less ... unfortunately there are still some quality issues to be investigated: Some people believe that detail retention could be improved (which is mainly an issue for smaller frame dimensions), and there are cases where tiny image elements are dragged away by motion (notorious example: Star Wars intro, star scroller).
__________________

New German Gleitz board
MediaFire: x264 | x265 | VPx | AOM | Xvid
LigH is offline   Reply With Quote
Old 16th June 2017, 21:57   #5403  |  Link
Motenai Yoda
Registered User
 
Motenai Yoda's Avatar
 
Join Date: Jan 2010
Posts: 709
Quote:
Originally Posted by iwod View Post
...starting with Apple. God I am Old!
starting with who?
HEVC has "wide spread support and uses" since years, s5 was the first smartphone with hevc hw decode capability as most of nowdays smartphones/tablets, Windows 10 has an integrate HEVC support (but only hw based), a lot of tvs can play even 10bit HEVC 4K HDR video/stream

this apple marketing piss me off when even my father's p8 lite can play a hevc file!!!
__________________
powered by Google Translator

Last edited by Motenai Yoda; 16th June 2017 at 22:01.
Motenai Yoda is offline   Reply With Quote
Old 18th June 2017, 15:35   #5404  |  Link
stax76
Registered User
 
stax76's Avatar
 
Join Date: Jun 2002
Location: On thin ice
Posts: 6,837
Does x264 --no-cabac fit into any of the tab page names that are used in the staxrip x265 GUI?

https://github.com/stax76/staxrip#x265-encoder-options

I'm re-implementing the x264 GUI, in the nvenc GUI I've put cabac to the 'Other' page, maybe there is a better fit.
stax76 is offline   Reply With Quote
Old 18th June 2017, 16:52   #5405  |  Link
iwod
Registered User
 
Join Date: Apr 2002
Posts: 756
Quote:
Originally Posted by Motenai Yoda View Post
starting with who?
HEVC has "wide spread support and uses" since years, s5 was the first smartphone with hevc hw decode capability as most of nowdays smartphones/tablets, Windows 10 has an integrate HEVC support (but only hw based), a lot of tvs can play even 10bit HEVC 4K HDR video/stream

this apple marketing piss me off when even my father's p8 lite can play a hevc file!!!
Ok.

Because of the way it works, most Android could play HEVC due to Software decoding. But not everyone will play it smoothly, due to the lacking single thread performance and hardware decode.
Not "Every" Samsung Phone or Tablet has HEVC hardware Decode. Namely their own SoC. Although most Qualcomm SoC should have by default.
Not every manufacture would have hardware decode by default EVEN if it is present on the SoC, because of patents licensing. And happens in certain countries.
And of coz there is a difference between FULL hardware decode and partial hardware decode.


Now name me a few big Network, services providers that are using HEVC for broadcasting or streaming? Purely for the numbers, there is more HEVC hardware decode capable product sold in China then US + EU + Japan combined. And yet most of their Streaming networks still aren't on HEVC. ( Actually not entirely true now in 2017 for China )
And which of these Network, has a FULL catalog of options available in HEVC. Not Amazon, Not Netflix, Not BBC, and heck the most common BT movie and shows are still on H.264 and not on HEVC. And this is the same in China.

May be i should have said "Ending" with Apple. Now the world could finally moves towards HEVC.
iwod is offline   Reply With Quote
Old 18th June 2017, 23:45   #5406  |  Link
Motenai Yoda
Registered User
 
Motenai Yoda's Avatar
 
Join Date: Jan 2010
Posts: 709
I didn't wrote that all products supports hevc, but most of them since years, also even most low budget phones like huawei p8 lite or samsung grand prime can easely hw decode a 720p 8bit, IIRC all tvs on sale in Germany, France and Italy should have a t2 decoder with hevc support, intel igpus from haswell (hw accelerated, from skylake full 8/10bit hw), nvidia gpus since gtx 960 and xbox one too.

You ask for some network? Netflix and Amazon streams 4k hevc to their subscribers, and PB lists me a lot of movies/series in hevc (405026)
UHD BD format rely on HEVC

but now apple with its 100 milions iphone 6s/7 will change everything, sure
__________________
powered by Google Translator
Motenai Yoda is offline   Reply With Quote
Old 19th June 2017, 06:10   #5407  |  Link
x265_Project
Guest
 
Posts: n/a
FYI - Kavitha and Santhoshini are 2 of our developers. As they mentioned, we'll work on improving the documentation for all of x265's analysis load/save/optimization features.
  Reply With Quote
Old 21st June 2017, 14:22   #5408  |  Link
GhostAFRippEr
FoReVeR MoViE
 
GhostAFRippEr's Avatar
 
Join Date: Feb 2008
Location: Port
Posts: 19
x265 Where can I add HDR ?
GhostAFRippEr is offline   Reply With Quote
Old 21st June 2017, 14:26   #5409  |  Link
sneaker_ger
Registered User
 
Join Date: Dec 2002
Posts: 5,565
http://x265.readthedocs.io/en/defaul...mation-options

You can use those options to add the necessary flags. Actual creation of HDR content has to be done outside of x265.
sneaker_ger is offline   Reply With Quote
Old 21st June 2017, 16:35   #5410  |  Link
LigH
German doom9/Gleitz SuMo
 
LigH's Avatar
 
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,752
x265 2.4+75-80c23559084c (GCC 6.3.0)
x265 2.4+75-80c23559084c (GCC 7.1.0)

mostly improvements for SEA integral calculations with AVX2 assembly; some tidy-up.

Note: make directive "ENABLE_DYNAMIC_HDR10" is now renamed to "ENABLE_HDR10_PLUS"

Attention: New archive structure! (May change next time again, it feels bloated already... what to omit, what to keep?)
_

libhdr10plus.dll — separate DLL to handle Dynamic HDR10+ definitions in JSON format (possibly to be used by a custom application, used in parallel to a libx265.dll?)

libx265_main.dll — DLL with 8 bit precision x265 encoder core, to be used by a custom application or another x265 CLI, Dynamic HDR10+ support disabled
libx265_main10.dll — DLL with 10 bit precision x265 encoder core, to be used by a custom application or another x265 CLI, Dynamic HDR10+ support disabled
libx265_main12.dll — DLL with 12 bit precision x265 encoder core, to be used by a custom application or another x265 CLI, Dynamic HDR10+ support disabled
libx265.dll — multi-library DLL with 8+10+12 bit precision x265 encoder cores, to be used by a custom application, Dynamic HDR10+ support disabled

x265_main.exe — CLI application with 8 bit precision x265 encoder core (can use DLLs with different precisions), Dynamic HDR10+ support disabled
x265_main10.exe — CLI application with 10 bit precision x265 encoder core (can use DLLs with different precisions), Dynamic HDR10+ support disabled
x265_main12.exe — CLI application with 12 bit precision x265 encoder core (can use DLLs with different precisions), Dynamic HDR10+ support disabled
x265_ml.exe — multi-library CLI application with 8+10+12 bit precision x265 encoder cores (needs no other DLLs), Dynamic HDR10+ support disabled

HDR10plus\libx265.dll — multi-library DLL with 8+10+12 bit precision x265 encoder cores, to be used by a custom application, Dynamic HDR10+ support enabled
HDR10plus\x265_ml.exe — multi-library CLI application with 8+10+12 bit precision x265 encoder cores (needs no other DLLs), Dynamic HDR10+ support enabled
_

I don't see any reference to the libhdr10plus.dll in any x265 CLI or DLL when built with Dynamic HDR10+ disabled, so I doubt that they will be able to support it simply because the libhdr10plus.dll resides in the same directory (similar to supporting a core with different precision); I guess that if you want Dynamic HDR10+ to be supported, you have to use an enabled build, but then it will already contain the code, so there is no obvious need for that separate DLL, at least for [lib]x265; maybe for a custom application handling both tasks separately.

I did not yet try to discover if it is possible to build a mostly dynamically linked package with Dynamic HDR10+ support, consisting of one CLI and all the rest as DLLs, with the libhdr10plus.dll still separated... I would assume that its code would be included in the CLI or DLLs at least once, if not everywhere.

As a GUI author using any x265 CLI, I assume you would prefer using only the HDR10plus\x265_ml.exe (All-In-One build) as x265.exe called by your GUI.
__________________

New German Gleitz board
MediaFire: x264 | x265 | VPx | AOM | Xvid
LigH is offline   Reply With Quote
Old 24th June 2017, 03:33   #5411  |  Link
Midzuki
Unavailable
 
Midzuki's Avatar
 
Join Date: Mar 2009
Location: offline
Posts: 1,480
x265.exe 2.4+87-5f2330bdb8fa

https://forum.videohelp.com/threads/...22#post2489522
Midzuki is offline   Reply With Quote
Old 24th June 2017, 14:03   #5412  |  Link
LigH
German doom9/Gleitz SuMo
 
LigH's Avatar
 
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,752
x265 2.4+87-5f2330bdb8fa (GCC 6.3.0)
x265 2.4+87-5f2330bdb8fa (GCC 7.1.0)

merge with stable; several renames, optimizations, refinements... most obvious CLI changes:

Code:
   --analysis-reuse-mode <string|int>  save - Dump analysis info into file, load - Load analysis buffers from the file. Default 0
   --analysis-reuse-file <filename>    Specify file name used for either dumping or reading analysis data. Deault x265_analysis.dat
   --analysis-reuse-level <1..10>      Level of analysis reuse indicates amount of info stored/reused in save/load mode, 1:least..10:most. Default 5

   --[no-]refine-mv              Enable mv refinement for load mode. Default disabled

   --[no-]const-vbv              Enable consistent vbv. turned on with tune grain. Default disabled
__________________

New German Gleitz board
MediaFire: x264 | x265 | VPx | AOM | Xvid
LigH is offline   Reply With Quote
Old 24th June 2017, 14:05   #5413  |  Link
Atak_Snajpera
RipBot264 author
 
Atak_Snajpera's Avatar
 
Join Date: May 2006
Location: Poland
Posts: 7,806
Quote:
As a GUI author using any x265 CLI, I assume you would prefer using only the HDR10plus\x265_ml.exe (All-In-One build) as x265.exe called by your GUI.
Yeah. Single executable makes more sense for GUI maker like me.
Atak_Snajpera is offline   Reply With Quote
Old 24th June 2017, 16:01   #5414  |  Link
stax76
Registered User
 
stax76's Avatar
 
Join Date: Jun 2002
Location: On thin ice
Posts: 6,837
less is sometimes more...
stax76 is offline   Reply With Quote
Old 26th June 2017, 04:43   #5415  |  Link
pradeeprama
Registered User
 
Join Date: Sep 2015
Posts: 48
Quote:
Originally Posted by LigH View Post

I don't see any reference to the libhdr10plus.dll in any x265 CLI or DLL when built with Dynamic HDR10+ disabled, so I doubt that they will be able to support it simply because the libhdr10plus.dll resides in the same directory (similar to supporting a core with different precision); I guess that if you want Dynamic HDR10+ to be supported, you have to use an enabled build, but then it will already contain the code, so there is no obvious need for that separate DLL, at least for [lib]x265; maybe for a custom application handling both tasks separately.
We've enabled exporting libhdr10plus.dll in case any application integrator wants to use the functions exported by this library (which enable parsing json files that contain creative intent meta-data for the SMPTR-2094-40) in their own video library.

By default, libx265 already integrates this code natively when HDR10PLUS is enabled in Cmake, to avoid extra library dependence. When disabled, the options --dhdr10-info, and --dhdr10-plus won't work.

Hope this clarifies things.
pradeeprama is offline   Reply With Quote
Old 26th June 2017, 07:36   #5416  |  Link
LigH
German doom9/Gleitz SuMo
 
LigH's Avatar
 
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 6,752
So I have to ask: Does anyone here need anything more than the "All-in-one" EXE? If not, I will release only that regularly in the future. Alternative files by request only (e.g. a library for GUIs like Avidemux).
__________________

New German Gleitz board
MediaFire: x264 | x265 | VPx | AOM | Xvid
LigH is offline   Reply With Quote
Old 26th June 2017, 09:13   #5417  |  Link
stax76
Registered User
 
stax76's Avatar
 
Join Date: Jun 2002
Location: On thin ice
Posts: 6,837
All-in-one sounds good.
stax76 is offline   Reply With Quote
Old 26th June 2017, 10:55   #5418  |  Link
Magik Mark
Registered User
 
Join Date: Dec 2014
Posts: 666
Can somebody confirm my finding:

Using +87 in --multi* causes a lot of blocking in 2pass 10bit x265. Video is unwatchable. No problem before +87
__________________
Asus ProArt Z790 - 13th Gen Intel i9 - RTX 3080 - DDR5 64GB Predator - LG OLED C9 - Yamaha A3030 - Windows 11 x64 - PotPlayerr - Lav - MadVR
Magik Mark is offline   Reply With Quote
Old 26th June 2017, 10:58   #5419  |  Link
Magik Mark
Registered User
 
Join Date: Dec 2014
Posts: 666
How do I use the --analysis-reuse *?

If I use "Save", When and how do i use the "Load"? In 2nd pass?
__________________
Asus ProArt Z790 - 13th Gen Intel i9 - RTX 3080 - DDR5 64GB Predator - LG OLED C9 - Yamaha A3030 - Windows 11 x64 - PotPlayerr - Lav - MadVR
Magik Mark is offline   Reply With Quote
Old 26th June 2017, 11:13   #5420  |  Link
Ma
Registered User
 
Join Date: Feb 2015
Posts: 326
Quote:
Originally Posted by Magik Mark View Post
Can somebody confirm my finding:

Using +87 in --multi* causes a lot of blocking in 2pass 10bit x265. Video is unwatchable. No problem before +87
Yes, see issue #354 https://bitbucket.org/multicoreware/...2pass-encoding
--------------------------------
Now 2pass encoding is fixed (from ver. 2.4+89).

Last edited by Ma; 28th June 2017 at 06:51.
Ma is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 10:37.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.