[HEVC] x265.EXE: mingw builds

[Selur]

did anyone manage to build a mac version of x265?

[easyfab]

did anyone manage to build a mac version of x265?

I'm not on mac but what did you try ? the make-project.sh in xcode ?

[Selur]

I'm not on mac but what did you try ?

see https://forum.videohelp.com/threads/357754-%5BHEVC%5D-x265-EXE-mingw-builds?p=2277895&v...=1#post2277895 and following

the make-project.sh in xcode ?

I tried the linux way, since I don't know my way around xcode.
I called the make-project.sh and it created a xcode project file, I opened it, selected 'ALL_BUILD' as target and thought I told it to build the project by clicking Product->Build but it fails with exit code 1. No clue where to find additional infos.

-> Since I don't really know my way round building stuff on mac through xcode and since the cmake way didn't work either I wanted to know if someone successfully compiled x265 on mac.

[easyfab]

based on x265 wiki, can you try this :


First you make a cross-toolchain.cmake file like this:
# this one is important
SET(CMAKE_SYSTEM_NAME Darwin)
# specify the cross compiler
SET(CMAKE_C_COMPILER i686-w64-mingw32-gcc)
SET(CMAKE_CXX_COMPILER i686-w64-mingw32-g++)
SET(CMAKE_RC_COMPILER i686-w64-mingw32-windres)
SET(CMAKE_ASM_YASM_COMPILER yasm)

Then you use this in your cmake execution thusly:

cmake -G "Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=cross-toolchain.cmake ../../source

But change i686-w64-mingw32-gcc, i686-w64-mingw32-g++ and i686-w64-mingw32-windres with the correct mac name (see in your bin directory if you find GCC G++ and windres ))

[Selur]

no thanks, I pass on that, I would then first have to set up a cross compiling environment on Windows and tinker around with that,..
Sorry, but that is simply too much hassle for me. (got lots of other stuff I would rather do)

[easyfab]

No it's not a real cross compiling, you must try this on your mac

only create the 2 files

[easyfab]

And here the 2 files.

take them in a subdirectory of build.

[Selur]

here? forgot to attach something?
---

ah now it's there

[zbutsam]

These are the results from some tests I did using the preset system. The PC is Intel 2500K oc@4.1Ghz/ 8 GB ram/ Windows 7 64bit. x265 is VC11 64bit.

Source: vob file, cropped in Avisynth (no other filters), 720x304

-- ultrafast 59.17 fps, 747.59 kb/s, Global PSNR: 35.412 *doesn't play with MPC-HC+Strongene
-- superfast 53.50 fps, 725.19 kb/s, Global PSNR: 35.661 *doesn't play with MPC-HC+Strongene
-- veryfast 32.01 fps, 715.96 kb/s, Global PSNR: 35.846
-- faster 32.10 fps, 715.96 kb/s, Global PSNR: 35.846
-- fast 16.72 fps, 698.99 kb/s, Global PSNR: 36.700
-- medium 14.09 fps, 692.65 kb/s, Global PSNR: 36.700
-- slow 11.45 fps, 585.36 kb/s, Global PSNR: 36.205
-- slower 2.34 fps, 548.01 kb/s, Global PSNR: 36.430

Same source as above, adding --q 24 -F4 to x265 command line

-- fast 16.21 fps, 2115 kb/s, Global PSNR: 41.651
-- medium 14.11 fps, 2087 kb/s, Global PSNR: 41.654
-- slow 11.96 fps, 1937 kb/s, Global PSNR: 41.474

Source: 1920*1080 ts file resized to 1280*720 in Avisynth, adding --q 24 -F4 to x265 command line

-- fast 5.01 fps, 6089 kb/s, Global PSNR: 44.318
-- medium 4.33 fps, 6007 kb/s, Global PSNR: 44.324
-- slow 3.41 fps, 5495 kb/s, Global PSNR: 44.122

[Selur]

@easyfab: Not working, tried different compilers, always get:

cmake -G "Unix Makefiles" -DCMAKE_TOOLCHAIN_FILE=cross-toolchain.cmake ../../source 
-- The CXX compiler identification is unknown
-- Check for working CXX compiler: compiler
CMake Error: your CXX compiler: "compiler" was not found.   Please set CMAKE_CXX_COMPILER to a valid compiler path or name.
CMake Error: Internal CMake error, TryCompile configure of cmake failed
-- Check for working CXX compiler: compiler -- broken
CMake Error at /Applications/CMake 2.8-12.app/Contents/share/cmake-2.8/Modules/CMakeTestCXXCompiler.cmake:54 (message):
  The C++ compiler "compiler" is not able to compile a simple test program.

  It fails with the following output:

   

  

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:9 (project)


CMake Error: your CXX compiler: "compiler" was not found.   Please set CMAKE_CXX_COMPILER to a valid compiler path or name.
-- Configuring incomplete, errors occurred!

tried:


SET(CMAKE_C_COMPILER /usr/bin/clang)
SET(CMAKE_CXX_COMPILER compiler /usr/bin/clang++)

SET(CMAKE_C_COMPILER /usr/bin/cc)
SET(CMAKE_CXX_COMPILER compiler /usr/bin/c++)

SET(CMAKE_C_COMPILER /usr/bin/gcc)
SET(CMAKE_CXX_COMPILER compiler /usr/bin/gcc++)

[Marchand]

x265 0.5+91-c51c35880df5

Chie
CRF is working perfectly in this version, along with the Hybrid Test program.
thank you

mkvextract started...
Starting Main@17:42:59.557:
"C:\PROGRA~1\HYBRID~1.1\MKVEXT~1.EXE" tracks "C:\Users\Marchand\Videos\101394662.mkv" 1:"C:\Users\Marchand\AppData\Local\Temp\iId_1_aid_ 0_DELAY_-60ms_17_42_52_5210_01.aac"
finished after 00:00:06.726
finished...

Created C:\Users\Marchand\AppData\Local\Temp\iId_1_aid_0_D ELAY_-60ms_17_42_52_5210_01.aac (2.00259 MB)
NeroAACEnc started...
Starting Main@17:43:06.342:
"C:\PROGRA~1\HYBRID~1.1\NEROAA~3.EXE" -br 128000 -ignorelength -if - -of "C:\Users\Marchand\AppData\Local\Temp\iId_1_aid_0_ 17_42_52_5210_02.aac"
finished after 00:00:05.309
finished...

Created C:\Users\Marchand\AppData\Local\Temp\iId_1_aid_0_1 7_42_52_5210_02.aac (1.97476 MB)
deleted C:\Users\Marchand\AppData\Local\Temp\iId_1_aid_0_D ELAY_-60ms_17_42_52_5210_01.aac
x265 (1 pass bitrate) x265 processing started
Starting Main@17:43:11.722:
"C:\PROGRA~1\HYBRID~1.1\x265-16bit.exe" --input - --input-res 1920x1080 --fps 23.976 --frames 3085 --crf 28 --ssim --output "C:\Users\Marchand\AppData\Local\Temp\test_17_42_5 2_5210_04.265"
x265 [info]: using cpu capabilities: MMX2 SSE SSE2Fast SSSE3 SSE4.1 Cache64
x265 [info]: performance primitives: intrinsic assembly
x265 [info]: Main profile, Level-4 (Main tier)
x265 [info]: WPP streams / pool / frames : 17 / 4 / 1
x265 [info]: CU size : 64
x265 [info]: Max RQT depth inter / intra : 1 / 1
x265 [info]: ME / range / subpel / merge : star / 60 / 5 / 3
x265 [info]: Keyframe min / max : 250 / 250
x265 [info]: Rate Control : CRF-28.000000
x265 [info]: Lookahead / bframes / badapt : 10 / 3 / 1
x265 [info]: tools: rect amp rd=0 ref=1 lft sao-lcu sign-hide
encoded 3084 frames in 2407.12s (1.28 fps), 2146.39 kb/s, Global PSNR: 45.481
x265 [info]: frame I:57 kb/s: 21057.35 PSNR Mean: Y:45.862 U:52.023 V:52.311
x265 [info]: frame P:2042 kb/s: 2407.93 PSNR Mean: Y:46.469 U:55.314 V:55.486
x265 [info]: frame B:985 kb/s: 509.86 PSNR Mean: Y:36.613 U:44.258 V:45.577
x265 [info]: global: kb/s: 2146.39 PSNR Mean: Y:43.310 U:51.722 V:52.262
finished after 00:40:07.340
finished...

Created C:\Users\Marchand\AppData\Local\Temp\test_17_42_52 _5210_04.265 (34.3207 MB)
Starting Main@18:23:19.101:
"C:\PROGRA~1\HYBRID~1.1\MP4Box.exe" -add "C:\Users\Marchand\AppData\Local\Temp\TEST_1~1.265 "#video:fps=23.976 -brand hvc1 -add "C:\Users\Marchand\AppData\Local\Temp\IID_1_~2.AAC "#audio:lang= -mpeg4 -itags tool="Hybrid 2013.11.1.1" -tmp "C:\Users\Marchand\AppData\Local\Temp" -new "C:\Users\Marchand\Videos\Test Hybrid\17_42_52_5210__05.mp4"
finished after 00:00:01.954
finished...

Created C:\Users\Marchand\Videos\Test Hybrid\17_42_52_5210__05.mp4 (36.3203 MB)
deleted C:\Users\Marchand\AppData\Local\Temp\test_17_42_52 _5210_04.265
deleted C:\Users\Marchand\AppData\Local\Temp\iId_1_aid_0_1 7_42_52_5210_02.aac
renamed C:\Users\Marchand\Videos\Test Hybrid\17_42_52_5210__05.mp4 to C:\Users\Marchand\Videos\Test Hybrid\test.mp4

[x265]

- news: --preset and --tune has been added.

Yes, we have started to implement x264 style presets. The "medium" performance preset is the new default setting for options not specified. I apologize that our documentation efforts haven't kept pace with our development efforts. We'll get a new Evaluator's Guide posted ASAP.

The presets are as follows (default values are used wherever a setting is not specified).

ultrafast=-s 32 --b-adapt 0 -b 4 --tu-inter-depth=1 --tu-intra-depth=1 --rd 0 --subme=0 --max-merge=1 --me=0 --no-amp --no-rect --no-tskip --early-skip --fast-cbf --no-lft --no-sao --no-signhide --no-weightp
superfast=-s 32 --b-adapt 0 -b 4 --tu-inter-depth=1 --tu-intra-depth=1 --rd 0 --subme=1 --max-merge=1 --me=1 --no-amp --no-rect --no-tskip --early-skip --fast-cbf --no-signhide --no-weightp
veryfast=--b-adapt 0 -b 4 --tu-inter-depth=1 --tu-intra-depth=1 --rd 0 --subme=1 --me=1 --max-merge=2 --no-amp --no-rect --no-tskip --early-skip --fast-cbf
faster=--b-adapt 0 -b 4 --tu-inter-depth=1 --tu-intra-depth=1 --rd 0 --subme=1 --me=1 --max-merge=2 --no-amp --no-rect --no-tskip --early-skip
fast=--tu-inter-depth=1 --tu-intra-depth=1 --rd 0 --subme=1 --me=1 --max-merge=2 --no-amp --no-rect --no-tskip
medium=--tu-inter-depth=1 --tu-intra-depth=1 --rd 2 --max-merge=3 --no-amp --no-rect --no-tskip
slow=--b-adapt 2 -b 4 --tu-inter-depth=1 --tu-intra-depth=1 --rd 2 --max-merge=3 --no-tskip
slower=--b-adapt 2 --rc-lookahead 20 -b 5 --tu-inter-depth=2 --tu-intra-depth=2 --rd 2 --max-merge=4 --no-tskip --ref 3
veryslow=--b-adapt 2 --rc-lookahead 30 -b 9 --max-merge=5 --ref 5
placebo=--b-adapt 2 -b 16 --max-merge=5 --ref 16 --merange 124 --rc-lookahead 60

These are a fairly quick first take at the right settings to use for these presets. We're not satisfied that these are optimal at this point. For example, placebo mode should produce HM reference quality compression efficiency under any circumstance, and in our early tests it doesn't yet. As you select slower presets we want to see a clear improvement in compression efficiency (quality@ any bit rate), and as you select faster presets we want to see the minimum possible tradeoff in compression efficiency for the maximum improvement in encoding speed.

Keep in mind that for faster performance you will need to set the number of frames to be encoded in parallel (-F), and that you should also use --no-progress.

As this is an open source project, we welcome your testing of these presets and your suggestions for improvement. I'll monitor this thread for your feedback. We have our own tests underway also.

Tom
MulticoreWare

[El Heggunte]

Very-well, now that LAV Splitter has proper support for HEVC,
it's time for an HEVC-in-TS sample file

http://www.mediafire.com/download/w7ja48666zlzmuc/stillpic-with-audio%5BHEVC%2BMP2%5D.ts.zip

INFO: it's just a still picture (one frame @ 2960x1888) + a 10-second silent MP2 stream,
and since it exists only for testing purposes, *anything goes* (again)

[Selur]

and that you should also use --no-progress.

How often does x265 output the progress, that this would influence the speed?
Wouldn't it be possible to only output progress every, in example, 100 frames if fps < 100 and every 1000 if last fps > 100 and thus limit the impact on performance?

medium=--tu-inter-depth=1 --tu-intra-depth=1 --rd 2 --max-merge=3 --no-amp --no-rect --no-tskip

common.cpp -> x265_param_default(x265_param *param)
states:

param->tuQTMaxInterDepth = 3;
param->tuQTMaxIntraDepth = 3;
param->maxNumMergeCand = 5u;
param->bEnableAMP = 1;
param->bEnableRectInter = 1;

where as common.cpp-> x265_param_default_preset(x265_param *param, const char *preset, const char *tune), states:

else if (!strcmp(preset, "medium"))         {
  param->tuQTMaxInterDepth = 1;
  param->tuQTMaxIntraDepth = 1;
  param->rdLevel = 0;
  param->maxNumMergeCand = 3;
  param->bEnableTransformSkip = 0;
 }

I apologize that our documentation efforts haven't kept pace with our development efforts

-> from the looks of it, the problem is not only the documentation, but also the code,..

[El Heggunte]

......
Wouldn't it be possible to only output progress every, in example, 100 frames if fps < 100 and every 1000 if last fps > 100 and thus limit the impact on performance?

+1, probably something like what xvid_encraw does:

-progress [integer]            : Show progress updates every n frames

[x265.cc]

x265.cc VC11 builds have been replaced by VC12 builds (Visual Studio 2013 Premium (RTM))

MinGW (gcc) x64 builds are still missing. (soon™)

[trox]

Very-well, now that LAV Splitter has proper support for HEVC

This is awesome!
Muxed my hevc video and aac audio into a MP4 container, and i could play the file without the Strongene Decoder installed, just Lavfilters 0.59. Commandline used for muxing:

mp4box -v -add iron.hevc:FMT=HEVC -fps 23.976 -add audio.aac -new output.mp4

When trying with MPC-HC, note that it may has older Lav filters built in (< 0.59), so you may need to disable the internal splitter for MP4, and add the external LAV splitter and LAV video decoder (0.59).

[El Heggunte]

^ Yes, BUT the ffmpeg-based HEVC decoder may still be "too slow" for streams "more complex",
according to http://forum.doom9.org/showthread.php?p=1651112#post1651112

Besides, you might want to test the sample file linked in the post http://forum.doom9.org/showthread.php?p=1651083#post1651083

[Jacobr]

Ive been playing around with frame parallelism options and for me it seems, at least for anime content, on dual core intel cpu, going higher than -f4 doesnt really make any sense and can make things worse if anthing.
Ive been getting around same fps with that param only changed and bitrate limited. It also doesnt help, when the resolution is large enough - i could only encode 4k ( 90 frames ) at 1 frame at a time. I got ~ 0.5 fps , used one of todays 0.5 builds


on presets though, i tried to encode higher resolutions like 1080p 1620p and 4k with slower presets and sometimes was getting crash at the start. the more -f the worse in that department it seemed ( i guess the cpu is likely to get killed ). As 'little' as 1.9 GB RAM usage while 4k encode on slow.

"slow" encode actually finished, just copied text too early, but veryslow crashing on frame 5 even with lookahead=10 and ref=2, needed to restrain bframes to 4 ( effectively changing the preset quite a bit, though i still got awful speed) .

x265 --q 18 --keyint 72 --hash 0
--preset fast  -o output.hvc

y4m  [info]: 3840x2160 23Hz, frames 0 - 90 of 91
x265 [info]: using cpu capabilities: MMX2 SSE SSE2Fast SSSE3 SSE4.2 AVX
x265 [info]: performance primitives: intrinsic assembly
x265 [info]: Main profile, Level-5 (Main tier)
x265 [info]: WPP streams / pool / frames  : 34 / 4 / 1
x265 [info]: CU size                      : 64
x265 [info]: Max RQT depth inter / intra  : 1 / 1
x265 [info]: ME / range / subpel / merge  : hex / 60 / 1 / 2
x265 [info]: Keyframe min / max           : 72 / 72
x265 [info]: Rate Control                 : CQP-18
x265 [info]: Lookahead / bframes / badapt : 10 / 3 / 1
x265 [info]: tools: rect rd=0 ref=1 lft sao-lcu sign-hide
x265 [info]: frame I:3      kb/s: 46455.09 PSNR Mean: Y:55.038 U:61.147 V:59.675

x265 [info]: frame P:30     kb/s: 6163.21  PSNR Mean: Y:52.807 U:58.495 V:56.842

x265 [info]: frame B:58     kb/s: 697.66   PSNR Mean: Y:52.985 U:58.337 V:56.964

x265 [info]: global:        kb/s: 4007.98  PSNR Mean: Y:52.994 U:58.482 V:57.013


encoded 91 frames in 162.38s (0.56 fps), 4007.98 kb/s, Global PSNR: 54.182

x265 --q 18 --keyint 72 --hash 0
--preset slow 
---------------------------------------------------------
y4m  [info]: 3840x2160 23Hz, frames 0 - 90 of 91
x265 [info]: using cpu capabilities: MMX2 SSE SSE2Fast SSSE3 SSE4.2 AVX
x265 [info]: performance primitives: intrinsic assembly
x265 [info]: Main profile, Level-5 (Main tier)
x265 [info]: WPP streams / pool / frames  : 34 / 4 / 1
x265 [info]: CU size                      : 64
x265 [info]: Max RQT depth inter / intra  : 1 / 1
x265 [info]: ME / range / subpel / merge  : star / 60 / 5 / 3
x265 [info]: Keyframe min / max           : 72 / 72
x265 [info]: Rate Control                 : CQP-18
x265 [info]: Lookahead / bframes / badapt : 10 / 4 / 2
x265 [info]: tools: rect amp rd=1 ref=1 lft sao-lcu sign-hide
[94.5%] 86/91 frames, 0.34 fps, 4014.56 kb/s, eta 0:00:14


x265 --q 18 --keyint 72 --hash 0
--preset veryslow --rc-lookahead 10 --ref 2 -b 4 
---------------------------------------------------------
y4m  [info]: 3840x2160 23Hz, frames 0 - 90 of 91
x265 [info]: using cpu capabilities: MMX2 SSE SSE2Fast SSSE3 SSE4.2 AVX
x265 [info]: performance primitives: intrinsic assembly
x265 [info]: Main profile, Level-5 (Main tier)
x265 [info]: WPP streams / pool / frames  : 34 / 4 / 1
x265 [info]: CU size                      : 64
x265 [info]: Max RQT depth inter / intra  : 3 / 3
x265 [info]: ME / range / subpel / merge  : star / 60 / 5 / 5
x265 [info]: Keyframe min / max           : 72 / 72
x265 [info]: Rate Control                 : CQP-18
x265 [info]: Lookahead / bframes / badapt : 10 / 4 / 2
x265 [info]: tools: rect amp rd=2 ref=2 lft sao-lcu sign-hide tskip(fast+rdo)
x265 [info]: frame I:3      kb/s: 42516.76 PSNR Mean: Y:54.882 U:60.718 V:59.280

x265 [info]: frame P:33     kb/s: 5645.38  PSNR Mean: Y:53.392 U:59.484 V:57.650

x265 [info]: frame B:55     kb/s: 667.56   PSNR Mean: Y:53.272 U:58.966 V:57.413

x265 [info]: global:        kb/s: 3852.35  PSNR Mean: Y:53.369 U:59.212 V:57.561


encoded 91 frames in 1210.14s (0.08 fps), 3852.35 kb/s, Global PSNR: 54.623

Just for laugh, placebo 4k started at 0.05 fps (not going to finish it tho )

[Mephesto]

What's with the recent influx of doom9 users on this thread? I recognize Tommy Carrot (sup!) and foxyshadis (die!).

Is there no x265 thread on doom9? Did the x265 developer decode to invest in Videohelp instead?

[Selur]

@Mephesto: There are a lot of users like me, which are active in doom9 and other forums and wouldn't label them selfs 'Doom9 users' or 'VideoHelp users'. -> Please, discuss such stuff in a separate thread, that just screams for a flamewar and it would be a shame to ruin this thread.

[Mephesto]

Yes except the users I'm referring to unlike you only joined weeks ago and for the sole purpose of posting in this thread. I'm asking a serious, legitimate question. I was gonna ask a few weeks ago but I didn't wanna interrupt the flow of this thread.

[Selur]

@Mephesto: I'm not doubting that your question, in itself, isn't legitimate. I doubt that this thread is the right place for it, which is mainly because you had to comment on some users, which simply takes away a lot of legitimation and makes it look more like a 'I want to bash users'-startUp than a serious question.

To answer your question:
Yes, Doom9 does have HEVC and x264 related threads (easy to check if you visit the Doom9 forum), but they are not that active with users testing the encoder (compared to here), probably because most of them want to wait, till x265 is more mature. So users which like to read a bit more about early testing read here and some of them decided to even post.

[LigH.de]

I am not yet certain about it ... but I believe that the development of the bitrate display in the console output is a bit strange. It seems to constantly raise. I remember that it started around 300 kbps in the beginning, is now around 35 Mbps after ~700 frames, and I think I have seen more than 100 Mbps close to the end of the encode of 1440 frames. To be checked...

[Selur]

@LigH: What does you call look like? Which x265 version did you use?

[LigH.de]

v0.5+95 VC12 x86-64

--preset slower --crf 12 -F 6 -i 240 --psnr --ssim

[Selur]

using:

mencoder -ovc raw -noskip -vf scale,format=i420 -forcedsubsonly -nosub -nosound -mc 0 -lavdopts threads=8 -really-quiet -of rawvideo -o - -dvd-device "H:\TestClips&Co\DVDs\ElephantsDream\VIDEO_TS" dvd://1 | x265 --frame-threads 6 --input - --input-res 720x576 --fps 25 --frames 15900 --keyint 240 --crf 12 --ssim --psnr --output "H:\Output\test_16_04_58_3910_01.265"

0.5+153-21e08cf159c5 (UTC 11:04:49 AM) 32bit and 64bit - 8bpp simply crash for me

x265_0.5+95-37903c6fd1f9 x86_64 8bpp -> bit rate does grow after encoding a few thousend frame, at the beginning everything is fine,...
-> looks like a bug

[Tommy Carrot]

What's with the recent influx of doom9 users on this thread? I recognize Tommy Carrot (sup!) and foxyshadis (die!).

Is there no x265 thread on doom9? Did the x265 developer decode to invest in Videohelp instead?

The x265 thread seems more active here, and there is more discussion about the technical details and stuff that interests me. The doom9 thread is more about how to use the encoder. And i don't even remember my password there, it's been ages since i stopped posting there. I'm surprised you still remember me.

@Selur: same here, the latest build crashes at the start of encoding.

[LigH.de]

Testing v0.5+153 with the new AQ mode 1: Not crashy with the small test video (Sintel trailer 640x272), but produces visible artefacts with some option sets. Possibly due to an unsupported combination of parameters?

This option set produced a clean file, though:

*.y4m -o *.hevc --preset slower --crf 24 -F 6 -w --bframe-bias 30 -i 240 --rdpenalty 1 --aq-mode 1 --psnr --ssim --log 3 --csv *.csv

The CLI parser is more tolerant than reported in the help output: "--input" appears to be optional, and other options are accepted even after the input/output filenames, not only before.
__

And now for something completely different:

In the debug-level output (--log 3), there are uppercase 'P-SLICE' and lowercase 'p-SLICE' frames. I wonder if that is related to the referencing count? Lowercase p's usually appear for tiny P frames, e.g. during black scenes, which are probably not referenced by B frames (always lowercase 'b-SLICE'). There are also upper and lower case 'i/I-SLICE' (possibly differing decoder-resetting and intermediate I frames?).

Does the sourcecode reveal the reason and meaning?

[Mephesto]

Selur, what bashing? I said 'sup to Tommy Carrot and foxy I remember nothing about except the name so I gave my default greet reserved for familiar strangers.
El Heggunte answered my question in detail in a PM.

The x265 thread seems more active here, and there is more discussion about the technical details and stuff that interests me. The doom9 thread is more about how to use the encoder. And i don't even remember my password there, it's been ages since i stopped posting there. I'm surprised you still remember me.

My memories are from ages ago when I stopped visiting. We never spoke but I remember you for the x264vfw and Snow codec guide you wrote or partly wrote. Welcome to Videohelp, we hope your stay is a pleasant one.

About x265, I'd like to join the fun but I've been unable to get x265 to recognize my input so I've only been able to test DivxHEVC so far and its quality is disappointing.

Is huffyuv a codec that outputs adequate YUV output because x265 still encoded garbage when I tried it.