x265 HEVC Encoder

[stax76]

Sorry to repost, MediaInfo.NET supports a special presentation for x265 parameters, it can be enabled in the settings.

Meanwhile, it was ported to run on .NET Framework 4.8 (so people don't need to install .NET Core) and it has a PowerShell based folder view.

https://github.com/stax76/MediaInfo.NET

https://forum.doom9.org/showthread.php?t=176886

[Blue_MiSfit]

Hey that's really neat! Thanks for adding this ^

[filler56789]

x265.exe 3.3+26-193db49

http://msystem.waw.pl/x265/

Fix bug in frame-dup + multi pass

Add save-load regression test CLI for Frame Duplication

[Patman]

Updated to version x265-3.3+25-ga6489d2fb (git source). See my sig

[Sagittaire]

Originally Posted by filler56789

x265.exe 3.3+26-193db49

http://msystem.waw.pl/x265/

Fix bug in frame-dup + multi pass

Add save-load regression test CLI for Frame Duplication

Well seem don't change anything. I make test for benwaggoner encoding challenge and I must make 3 pass to have good rate control. 2 pass encoding have too agressive quantizer curve compression at the start of encoding.

[tuanden0]

Originally Posted by Patman

Updated to version x265-3.3+25-ga6489d2fb (git source). See my sig

Thank for your build

[filler56789]

x265.exe 3.3+29-1e3dbf0

--- Cleanup
--- save-load-tests: Fix CLI
--- EQT Updates.

1. Improves documentation in help and x265readthedocs for rskip cli options.
2. Renamed rskip variable in x265_param structure & rectified regression clis.
3. Removed rskip mode 3 which is same as mode 2 with min-cu-size 16.

http://msystem.waw.pl/x265/

[Patman]

Updated (git source):

x265-3.3+4-g6a7df3229-* (marked as 3.4 branch, but the version shows 3.3+4 / maybe stable) [* built with msvc1925 and gcc11.0.0]
x265-3.3+27-g4780a8d99-* (master branch) [* built with msvc1925 and gcc11.0.0]

Downloadlink, see my sig

[RainyDog]

Originally Posted by Patman

Updated (git source):

x265-3.3+4-g6a7df3229-* (marked as 3.4 branch, but the version shows 3.3+4 / maybe stable) [* built with msvc1925 and gcc11.0.0]
x265-3.3+27-g4780a8d99-* (master branch) [* built with msvc1925 and gcc11.0.0]

Downloadlink, see my sig

Thanks for your builds as always

Is there a reason why they no longer support raw .avs (no piping) input?

[Patman]

Originally Posted by RainyDog

Thanks for your builds as always



Is there a reason why they no longer support raw .avs (no piping) input?

You're welcome. My builds have never supported direct avs input. Maybe I will add avs input support in future releases.

[stax76]

Are there builds that support both avs and vpy? libavformat supports both, that's how mpv opens avs and vpy, but does not support portable mode, blocks DLL loading from path env var.

[RainyDog]

Originally Posted by Patman

You're welcome. My builds have never supported direct avs input. Maybe I will add avs input support in future releases.

Hmm, I was sure there was a point last year when I had the piping tool option set to none in StaxRip across the board. Unless it was just with my x264 set-up...

In any case, be good if you can make your x265 builds work with raw input too. Thanks

[Patman]

Originally Posted by RainyDog

Hmm, I was sure there was a point last year when I had the piping tool option set to none in StaxRip across the board. Unless it was just with my x264 set-up...



In any case, be good if you can make your x265 builds work with raw input too. Thanks

Yeah, x264 support that. I do my best and give you a feedback

[RainyDog]

Originally Posted by Patman

Yeah, x264 support that. I do my best and give you a feedback

Thanks

I've now remembered how I was previously using raw input with x265... It was when Stax was using Wolfberry's builds. So seems it is possible to implement at least, unless something's changed with x265 itself since then.

I'll leave it in your capable hands anyway

[MeteorRain]

Direct AVS input was there for a while. x265 official denied my attempt to enhance the I/O part, so I have been keeping all patches out of the tree.

No one wrote direct VPY input so far.

[stax76]

If somebody is looking for vpy code:

https://github.com/rigaya/NVEnc/blob..._input_vpy.cpp

https://github.com/FFmpeg/FFmpeg/blo.../vapoursynth.c

[stax76]

Maybe I build a chunk encoding console app as it seems to be relatively simple and nobody else seems to be interested in building it. Are there any special x265 settings needed? x264 has a --stitchable option. How does ripbot264 do it? vspipe and avs2pipemod allow defining start and end frame. Are two chunks enough?

[vpupkind]

Originally Posted by stax76

Maybe I build a chunk encoding console app as it seems to be relatively simple and nobody else seems to be interested in building it. Are there any special x265 settings needed? x264 has a --stitchable option. How does ripbot264 do it? vspipe and avs2pipemod allow defining start and end frame. Are two chunks enough?

You may want to use their "chunked encoding" mode which will improve performance at the chunk boundaries

[LigH]

x265 3.3+27-g4780a8d99 (multilib, GCC 10.1)

[stax76]

Originally Posted by vpupkind

You may want to use their "chunked encoding" mode which will improve performance at the chunk boundaries

Thanks, so --chunk-start and --chunk-end, would be helpful if somebody can share experience with it. How many extra frames are needed? I'll use vspipe and avs2pipemod for trimming, modifying the avs/vpy file has too many implications.