x265 HEVC Encoder

[Barough]

Originally Posted by stax76

I've private messages disabled.

But my mail address is on my GitHub profile.

I'll have a look there when i get bk home

[EDIT]
Sent you a email

[Kurogane]

I'm trying to figure out why pmode give me this warning

x265 [warning]: Limit reference options 2 and 3 are not supported with pmode. Disabling limit reference

I'm using this basic config

--preset slow --crf 18.0 --profile main10 --output-depth 10 --pmode

When i use another preset than slow not give me this warning.

I'm using 3.4+9-g1fb7c7960

[benwaggoner]

Originally Posted by Kurogane

I'm trying to figure out why pmode give me this warning

x265 [warning]: Limit reference options 2 and 3 are not supported with pmode. Disabling limit reference

I'm using this basic config

--preset slow --crf 18.0 --profile main10 --output-depth 10 --pmode

When i use another preset than slow not give me this warning.

You can see here that Limit Refs 3 is used in presets 2-6 only:

https://x265.readthedocs.io/en/master/presets.html

[Barough]

x265 v3.4+35-772bb4c84 (32 & 64-bit 8/10/12bit Multilib Windows Binaries) (GCC 10.2.0)

https://bitbucket.org/multicoreware/x265_git/commits/branch/Release_3.5

[Kurogane]

Originally Posted by benwaggoner

You can see here that Limit Refs 3 is used in presets 2-6 only:

https://x265.readthedocs.io/en/master/presets.html

I tested in all profiles and only the one give me this error is "slow".

[Greenhorn]

The table is out-of-date/wrong. Limit-refs 1 is only used on "Slow" these days. Everything else uses 3 (slower, medium and lower) or none (veryslow/placebo.)

@kurogane: it's just saying that a setting used by the preset is incompatible with pmode. It should probably be setting it to "1" instead of disabling it entirely, but you can use both features and the slow preset all together just by setting --preset slow --limit-refs 1 --pmode.

[Boulder]

Originally Posted by Greenhorn

The table is out-of-date/wrong. Limit-refs 3 is only used on "Slow" these days. Everything else uses 3 (slower, medium and lower) or none (veryslow/placebo.)

@kurogane: it's just saying that a setting used by the preset is incompatible with pmode. It should probably be setting it to "1" instead of disabling it entirely, but you can use both features and the slow preset all together just by setting --preset slow --limit-refs 1 --pmode.

--preset slower applies --limit-refs 1. I'm using it right now in my encodes and I don't have any separate --limit-refs call. The info section shows this:

x265 [info]: References / ref-limit cu / depth : 4 / off / on

[Greenhorn]

Originally Posted by Boulder

--preset slower applies --limit-refs 1. I'm using it right now in my encodes and I don't have any separate --limit-refs call. The info section shows this:

x265 [info]: References / ref-limit cu / depth : 4 / off / on

Typo in my post. Woops.

[FranceBB]

For those of you that use AVID Media Composer, from version 2020.12 it's possible to link and edit H.265 files. Considering that H.265 was released more than 8 years ago, it's about time, AVID! They should have done this long time ago!! What took them so long...?! -.- Still, habemus H.265 import support at last...

[Barough]

x265 v3.4+36-5239276dd (32 & 64-bit 8/10/12bit Multilib Windows Binaries) (GCC 10.2.0)

https://bitbucket.org/multicoreware/x265_git/commits/branch/Release_3.5

[FranceBB]

Originally Posted by FranceBB

I guess we're gonna have to wait 'till someone will upload a sample, then...

In case anyone is still interested in files produced by Iphone 12, here it is:



They're indeed in Dolby Vision with the HLG profile, so BT2020nc HLG HDR 4:2:0 10bit planar in H.265.
Too bad for the VFR stuff which mobiles seem to love and everyone else in the world hates... (especially us, working in broadcast!)
I'm not in the edit room in which I have an HDR monitor and scope, so I can't tell you exactly how many nits there actually are, but Apple claims to reach 699 nits...
I think they're way too many for such a tiny sensor. From a very quick analysis, it looks like it's more or less 300 nits, which, for a mobile phone, looks quite alright.


For the records: this is from a colleague of mine who bought it, I actually went for a Google Pixel 5 in early November.

[quietvoid]

Updated my scenecut-aware-qp patch, now applies directly on Release 3.5 @ 5239276

[LigH]

Because the Yuuki mod appears to be well maintained, I tried to download and build this one alternatively in an interactive shell in MABS. Unfortunately, in contrast to the original x265 git, this modified fork apparently needs Ruby. A compatible version was found in the MSYS2 installation of MABS (2.7.0; minimum required is 1.8.0); but several include directories were missing, so cmake halted. I guess I could make it work if I knew where to include which shell variable exports?

[MeteorRain]

>tree /f D:\dev\x265-Yuuki-Asuna\include
D:\DEV\X265-YUUKI-ASUNA\INCLUDE
│  lsmash.h
│
├─avisynth
│  │  avisynth.h
│  │  avisynth_c.h
│  │
│  └─avs
│          alignment.h
│          capi.h
│          config.h
│          cpuid.h
│          minmax.h
│          posix.h
│          types.h
│          win.h
│
└─vapoursynth
        VapourSynth.h
        VSHelper.h
        VSScript.h

You'll need those to support avs/vpy/lsmash. ffmpeg input on msvc wasn't tested.

For msvc multi lib build you need to

-DLSMASH_SOURCE_DIR=../../x265-Yuuki-Asuna/include -DEXTRA_LINK_FLAGS="/LIBPATH:../../../x265-Yuuki-Asuna/lib-msvc /LIBPATH:.."

something like that.

For gcc you just compile and make install dependencies into system directories. That includes ffmpeg, avisynth (header only), vapoursynth(header only), lsmash.

Ruby script was to compose version number, so it's not absolute necessary and can be replaced by you own code to produce your own version number. I use Ruby because I'm a Ruby developer.

It may not be easy to use yuuki mod in mabs due to extra libraries being linked.

[LigH]

One hurdle after another ... the first one looked rather low to me, as a layman:

-- Could NOT find Ruby (missing: Ruby_INCLUDE_DIR Ruby_LIBRARY Ruby_CONFIG_INCLUDE_DIR) (found suitable version "2.7.2", minimum required is "1.8.0")

If that is all cmake complains about, I guess it can be solved. Then we will see further from there.

[MeteorRain]

Says found suitable version, so I guess it's just fine? I have the mingw-w64-x86_64-ruby package installed from pacman, and it works.

[LigH]

Well, the Ruby package as such is installed, but it misses configured environment variables. Therefore cmake halts.

[MeteorRain]

That's weird. I'm getting a similar error but cmake did generate all the project files without any problem.

-- Found Nasm 2.15.05 to build assembly primitives
-- Could NOT find Ruby (missing: Ruby_LIBRARY) (found suitable version "2.7.1", minimum required is "1.8.0")
-- x265 version 3.4+13-g729a838d3+38

[LigH]

So maybe the reason is somewhere else, like the cmake command line may need more explicit parameters than the vanilla x265 multilib configuration.

...
-- Found nasm: E:/MABS/msys64/mingw64/bin/nasm.exe (found version "2.15.05") 
-- Found Nasm 2.15.05 to build assembly primitives
CMake Deprecation Warning at dynamicHDR10/CMakeLists.txt:13 (cmake_minimum_required):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.


-- Found Git: E:/MABS/msys64/usr/bin/git.exe (found version "2.30.0") 
-- Could NOT find Ruby (missing: Ruby_INCLUDE_DIR Ruby_LIBRARY Ruby_CONFIG_INCLUDE_DIR) (found suitable version "2.7.2", minimum required is "1.8.0")
-- x265 Release Version 
-- The ASM_NASM compiler identification is NASM
-- Found assembler: E:/MABS/msys64/mingw64/bin/nasm.exe
-- Looking for strtok_r
-- Looking for strtok_r - found
CMake Error at CMakeLists.txt:637 (list):
  list GET given empty list


CMake Error at CMakeLists.txt:638 (list):
  list GET given empty list


-- Configuring incomplete, errors occurred!
See also "E:/MABS/x265-Yuuki-Asuna-Yuuki/build/msys64_hdr10_ml/12bit/CMakeFiles/CMakeOutput.log".
See also "E:/MABS/x265-Yuuki-Asuna-Yuuki/build/msys64_hdr10_ml/12bit/CMakeFiles/CMakeError.log".
make: *** No targets specified and no makefile found.  Stop.
cp: cannot stat 'libx265.a': No such file or directory
make: *** No rule to make target 'clean-generated'.  Stop.

Shall we discuss this elsewhere? A new thread here? An issue in your github repo?

[MeteorRain]

Please open an issue ticket.

EDIT:

Actually, I think you are on the wrong branch. Please switch to Asuna branch to test. Yuuki branch is not ready yet because 3.5 is not ready yet. As soon as 3.5 is tagged I'm going to revise the version generation code, which should solve the issue you are seeing.