Log in

View Full Version : x265 HEVC Encoder


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 [113] 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197

sneaker_ger
14th September 2017, 11:42
Example for your first file:
ffmpeg -i "input.mkv" -pix_fmt yuv420p10 -strict -1 -f yuv4mpegpipe - | x265 - --y4m --output-depth 10 --colorprim 9 --transfer 16 --colormatrix 9 --range limited --chromaloc 2 --max-cll "1000,96" --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15634,16450)L(10000000,50)" -o "output.265"
(--chromalog 2 is usually used for 4K HDR so I have set it. But MediaInfo doesn't show this about your source.)
remux with audio/subs from source: mkvmerge -o "output.mkv" "output.265" --no-video "input.mkv"

You can find some more examples/discussion here:
https://forum.doom9.org/showthread.php?t=174491
http://x265.readthedocs.io/en/default/cli.html#vui-video-usability-information-options

stax76
14th September 2017, 12:25
It's now --transfer smpte2084

edit:

Can anybody provide a sample file which such HDR metadata?

sneaker_ger
14th September 2017, 12:44
It's now --transfer smpte2084
Ah, I forgot. Thx. Edited.

Can anybody provide a sample file which such HDR metadata?
Knock yourself out:
http://demo-uhd3d.com/

_kermit
14th September 2017, 13:29
Example for your first file:
ffmpeg -i "input.mkv" -pix_fmt yuv420p10 -strict -1 -f yuv4mpegpipe - | x265 - --y4m --output-depth 10 --colorprim 9 --transfer 16 --colormatrix 9 --range limited --chromaloc 2 --max-cll "1000,96" --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15634,16450)L(10000000,50)" -o "output.265"
(--chromalog 2 is usually used for 4K HDR so I have set it. But MediaInfo doesn't show this about your source.)
remux with audio/subs from source: mkvmerge -o "output.mkv" "output.265" --no-video "input.mkv"

You can find some more examples/discussion here:
https://forum.doom9.org/showthread.php?t=174491
http://x265.readthedocs.io/en/default/cli.html#vui-video-usability-information-options

that was fast :)

so basically only --max-cll changes accordingly to the source?
Is there a need/benefit using any of the uhd/hdr Options like "--hdr-opt"?

You have some advice on the remaining regular settings for UHD? (preset, CRF value)?

thanks!

sneaker_ger
14th September 2017, 14:06
so basically only --max-cll changes accordingly to the source?
Other parameters might change as well but it seems most of the sources floating around use the same parameters, mostly. It's your job to check.

Also, some sources have parameters that don't make much sense. Like your second file which has "Mastering display luminance : min: 0.0000 cd/m2, max: 1000.0000 cd/m2".
Minimum luminance of 0? I don't think such a display is on the market.

Is there a need/benefit using any of the uhd/hdr Options like "--hdr-opt"?

You have some advice on the remaining regular settings for UHD? (preset, CRF value)?
[/QUOTE]
--hdr-opt is supposed to increase compression for HDR but I haven't actually tested it nor see other comparisons. I suggest you read the thread I linked and look around a bit around the forum. It's subjective.
Preset: as slow as you are willing to wait
CRF: as low as you are willing to sacrifice HDD space

stax76
14th September 2017, 14:59
@sneaker_ger

You can't really trust the documentation, it's not always in sync with the code, I would always use strings instead of integers for flags.

sneaker_ger
14th September 2017, 15:05
The integers should be the integers as they are stored in the bitstream, i.e. taken right out of the HEVC specs. I assume .. well .. hope they will never change. In this case I just chose them so it works with old and new x265 version.

stax76
14th September 2017, 15:12
I think if you compare with the console and online help you'll probably find more then one issue.

static const char * const x265_source_csp_names[] = { "i400", "i420", "i422", "i444", "nv12", "nv16", 0 };
static const char * const x265_video_format_names[] = { "component", "pal", "ntsc", "secam", "mac", "unknown", 0 };
static const char * const x265_fullrange_names[] = { "limited", "full", 0 };
static const char * const x265_colorprim_names[] = { "reserved", "bt709", "unknown", "reserved", "bt470m", "bt470bg", "smpte170m", "smpte240m", "film", "bt2020", "smpte428", "smpte431", "smpte432", 0 };
static const char * const x265_transfer_names[] = { "reserved", "bt709", "unknown", "reserved", "bt470m", "bt470bg", "smpte170m", "smpte240m", "linear", "log100",
"log316", "iec61966-2-4", "bt1361e", "iec61966-2-1", "bt2020-10", "bt2020-12",
"smpte2084", "smpte428", "arib-std-b67", 0 };
static const char * const x265_colmatrix_names[] = { "gbr", "bt709", "unknown", "", "fcc", "bt470bg", "smpte170m", "smpte240m",
"ycgco", "bt2020nc", "bt2020c", "smpte2085", "chroma-derived-nc", "chroma-derived-c", "ictcp", 0 };

sneaker_ger
14th September 2017, 15:30
I don't.

stax76
14th September 2017, 15:45
Maybe the order is correct, there are some incorrect names however like smpte-st-428 -> smpte428

cap5lock
18th September 2017, 12:42
Is there any h.265 parameters that remove digital noise and make background really still ?
I have no problem with color banding
Any possibilities to do it without additional filtering (avisynth, etc.)?

birdie
18th September 2017, 18:22
Is there any h.265 parameters that remove digital noise and make background really still ?
I have no problem with color banding
Any possibilities to do it without additional filtering (avisynth, etc.)?

None, it's not the codec's job to do.

Besides there are over several dozen of ways to remove noise and artifacts depending on the source.

Boulder
18th September 2017, 18:28
There are the --nr-intra and --nr-inter options available. Also the dreaded --sao a.k.a. Smooth All Objects could be helpful in your case.

birdie
18th September 2017, 21:37
sao is enabled by default, the two other options are not meant for removing noise or smoothing backgrounds because they will as well smooth everything else. If one wants to remove noise, use avisynth filters for that.

Natty
20th September 2017, 22:50
Is there any h.265 parameters that remove digital noise and make background really still ?
I have no problem with color banding
Any possibilities to do it without additional filtering (avisynth, etc.)?
u can set deblocking -3:0, raise qcomp, disable all smoothings, but these wont be enough until u use filters.

Midzuki
30th September 2017, 01:09
x265.exe 2.5+20-0967d0add97e

https://forum.videohelp.com/threads/357754-%5BHEVC%5D-x265-EXE-mingw-builds?p=2497549&viewfull=1#post2497549

Barough
2nd October 2017, 01:47
x265 v2.5+20-0967d0add97e (http://ge.tt/6zNsfkm2) (GCC 7.2.0, 32 & 64-bit 8/10/12bit Multilib Windows Binaries)

x265 [info]: HEVC encoder version 2.5+20-0967d0add97e
x265 [info]: build info [Windows][GCC 7.2.0][32/64 bit] 8bit+10bit+12bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2


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

LigH
3rd October 2017, 11:38
x265 2.5+22-8db95a1da9f8 (http://www.mediafire.com/file/2no1g79b81oakl6/x265_2.5%2B22-8db95a1da9f8.7z) (MSYS/MinGW, GCC 7.1.0) ... does XhmikosR still update?

Fixes for analysis load, WPP, bitstream payload size, VBV hanging; new (internal?) parameter for disabling lookahead; Windows DLL will export x265_encoder_ctu_info()

benwaggoner
6th October 2017, 19:40
sao is enabled by default, the two other options are not meant for removing noise or smoothing backgrounds because they will as well smooth everything else. If one wants to remove noise, use avisynth filters for that.

--nr-inter works sort of like an adaptive deadzone for predicted blocks. It absolutely will reduce random noise with a high spatial and temporal frequency, and will help stabalize the background of noisy sources. This can also yield significant bitrate reduction since encoding all those high frequency residuals every frame is expensive.

Of course it can also lose detail in moving areas as well.

Barough
7th October 2017, 12:46
x265 v2.5+25-4b95f82c9fb1 (http://ge.tt/1PDysom2) (GCC 7.2.0, 32 & 64-bit 8/10/12bit Multilib Windows Binaries)

x265 [info]: HEVC encoder version 2.5+25-4b95f82c9fb1
x265 [info]: build info [Windows][GCC 7.2.0][32/64 bit] 8bit+10bit+12bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2


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

RieGo
7th October 2017, 17:00
hey there. are there any commands to improve multithreading on x265?
i'm running an i9 @ 12/24x3.5ghz i end up with 70-80% cpu usage at most, using presets medium slow slower slowest / main10
it's running at ~5/6fps on a slower 4k encode
or do you think something else is bottlenecking me?

birdie
7th October 2017, 17:08
hey there. are there any commands to improve multithreading on x265?
i'm running an i9 @ 12/24x3.5ghz i end up with 70-80% cpu usage at most, using presets medium slow slower slowest / main10
it's running at ~5/6fps on a slower 4k encode
or do you think something else is bottlenecking me?

This has been discussed numerous times already. x265 doesn't scale past a certain number of cores. You either buy and use UHDKit or run several copies of x265 simultaneously.

RieGo
7th October 2017, 17:35
This has been discussed numerous times already. x265 doesn't scale past a certain number of cores. You either buy and use UHDKit or run several copies of x265 simultaneously.

thanks for explaining.
i was thinking x265 team wrote it scales up to 20(??) threads or something, but i wasn't sure
i also tried to disable HT to run with (only) 12 threads, which doesn't sound like much to me, but same result.
i'll run 2 instances of x265 then. ::thanks:

Atak_Snajpera
8th October 2017, 12:56
thanks for explaining.
i was thinking x265 team wrote it scales up to 20(??) threads or something, but i wasn't sure
i also tried to disable HT to run with (only) 12 threads, which doesn't sound like much to me, but same result.
i'll run 2 instances of x265 then. ::thanks:

You won't notice huge fps boost because HT on intel cpus gives only extra ~15%
http://i.cubeupload.com/4hEisV.png

If you see cpu utilization at ~75% then this means that in practice you get ~93% of your CPU.
100-15/50*(100-75)=92.5

AMED
8th October 2017, 18:16
x265 v2.5+25-4b95f82c9fb1 (http://ge.tt/1PDysom2) (GCC 7.2.0, 32 & 64-bit 8/10/12bit Multilib Windows Binaries)

x265 [info]: HEVC encoder version 2.5+25-4b95f82c9fb1
x265 [info]: build info [Windows][GCC 7.2.0][32/64 bit] 8bit+10bit+12bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2


https://bitbucket.org/multicoreware/x265/commits/branch/defaultBarough's link doesn't seem to work for me, just goes to a page saying "Drop to share files".

excellentswordfight
9th October 2017, 11:13
thanks for explaining.
i was thinking x265 team wrote it scales up to 20(??) threads or something, but i wasn't sure
i also tried to disable HT to run with (only) 12 threads, which doesn't sound like much to me, but same result.
i'll run 2 instances of x265 then. ::thanks:
I ran a few benchmarks on some machines a few weeks ago, I thought that x265 scaled quite nicely.

2x Intel Xeon E5-2690 v3 @ 2.9Ghz (24C48T): 3.36 fps
2x Intel Xeon E5-2643 v4 @ 3.6Ghz (12C24T): 2.37 fps

Barough
9th October 2017, 15:47
Barough's link doesn't seem to work for me, just goes to a page saying "Drop to share files".


No issues with DL'ing the archive here.

Barough
9th October 2017, 15:48
x265 v2.5+27-0e168bdeb48b (http://www93.zippyshare.com/v/54EYlZED/file.html) (GCC 7.2.0, 32 & 64-bit 8/10/12bit Multilib Windows Binaries)

x265 [info]: HEVC encoder version 2.5+27-0e168bdeb48b
x265 [info]: build info [Windows][GCC 7.2.0][32/64 bit] 8bit+10bit+12bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2


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

d3rd3vil
9th October 2017, 16:04
If I have an m2ts file with 2 layers and HDR10 PLUS Dolby Vision but the TV only recognizes HDR10, is there a way to force Dolby Vision somehow?

x265_Project
9th October 2017, 17:22
If I have an m2ts file with 2 layers and HDR10 PLUS Dolby Vision but the TV only recognizes HDR10, is there a way to force Dolby Vision somehow?

If there is metadata for multiple HDR standards, the TV decides which HDR format to use. If it has a choice between HDR10 (static HDR) and Dolby Vision (dynamic HDR), it will certainly choose Dolby Vision.

d3rd3vil
9th October 2017, 17:45
Yeah well but it doesnt. MKVToolNix shows 2 streams one with 4k and one with 1080p. Ofc thats not really accurate cause MKVToolNix doesnt support Dolby Vision but both standards are there. The TV doesnt play the m2ts.

So I have to convert the m2ts to mkv which THEN only seems to support HDR10.

As an example this one: http://4kmedia.org/lg-dolby-vision-uhd-4k-demo/

Once I've used MKVToolNix, the Dolby Vision is gone

Is there at least a way to see if I am using Dolby Vision or not? The TS and the MKV files look pretty much the same in MediaInfo for example. But one has DV the other doesnt....

Thunderbolt8
10th October 2017, 10:10
are you sure your TV supports Dolby Vision or 12-bit in general? From what Ive read most panels dont.

d3rd3vil
10th October 2017, 10:24
12 bit doesnt matter atm. No TV supports that, thats true.

I got an LG Oled B6. All these Oleds support Dolby Vision. So as I said the TS file has DV and it works fine! After using MKVToolNix, cause the program doesnt support DV, Dolby Vision is gone from the MKV.

But still some information wether the file has DV or not would be nice. But MediaInfo, nor MPC or VLC or any program show anything regarding Dolby Vision....its like it doesnt exist yet. Unfortunate

nevcairiel
10th October 2017, 11:05
This entire discussion is rather off-topic for the x265 thread, since x265 cannot encode Dolby Vision, nor is it in any way related to handling your existing Dolby Vision files.

jlpsvk
11th October 2017, 07:59
Hi... how can I use extracted Dolby Vision Enhancement layer to encode it to HEVC stream directly with x265?

d3rd3vil
11th October 2017, 14:17
And how to even detect it properly with eac3to

LigH
11th October 2017, 15:30
Why do you add a question about eac3to to a thread specifically discussing the development of x265? Stay in each thread, separately, please.

jlpsvk
11th October 2017, 18:44
Why do you add a question about eac3to to a thread specifically discussing the development of x265? Stay in each thread, separately, please.

I asked about using the layer in x265! :)

LigH
11th October 2017, 18:51
@jlpsvk: I directed that to d3rd3vil. Being interested in enhancing x265 is a valid intention here. But using eac3to is best discussed in a thread about eac3to, instead. And there I already expressed my doubts that eac3to is the first choice software to treat video streams, because it was originally made to handle audio streams.

jlpsvk
11th October 2017, 19:56
@LigH
Yeah. Ok. :) But. Can I use the demuxed Dolby Vision stream and mux it to encoded video with x265? in MKV new eac3to (3.22) is recognizing Dolby Vision Enhancement Layer too.

nevcairiel
11th October 2017, 20:52
x265 has no support for anything Dolby Vision, you would need external tools that support this, including writing the required metadata for Dolby Vision.

LigH
11th October 2017, 22:43
... yet?

x265_Project
12th October 2017, 00:07
x265 has no support for anything Dolby Vision, you would need external tools that support this, including writing the required metadata for Dolby Vision.

All dynamic HDR requires external tools to analyze the color volume of the video, frame by frame, saving this metadata to a file. For example, Samsung contributed code to x265 enabling us to parse this metadata and insert it into the HEVC bitstream as SEI messages. We are always working with partners in the video ecosystem to find ways to make these kinds of integrations easier and more reliable for our mutual end-users.

jlpsvk
12th October 2017, 06:46
if i will mux the second dolby layer to encoded mkv...will it work?

nevcairiel
12th October 2017, 07:15
if i will mux the second dolby layer to encoded mkv...will it work?

No. MKV has no support for Dolby Vision. Not to mention the additional metadata to even identify the streams as Dolby Vision.

byteshare
12th October 2017, 18:51
@x265_Project, is it possible to have metric data, such as SSIM scores put into the media info like the encoding settings are?

d3rd3vil
12th October 2017, 19:40
All dynamic HDR requires external tools to analyze the color volume of the video, frame by frame, saving this metadata to a file. For example, Samsung contributed code to x265 enabling us to parse this metadata and insert it into the HEVC bitstream as SEI messages. We are always working with partners in the video ecosystem to find ways to make these kinds of integrations easier and more reliable for our mutual end-users.

Well that sounds very good. Hopefully you can achieve sth. sooner or later :)

With mkv not supporting DV you mean Matroska as the stream, right? Cause there are mkv containers with mpeg-ts Dolby Vision streams, that seems to work. But the matroska stream doesnt work?!

For example this one is an mkv: https://drive.google.com/file/d/0BwxFVkl63-lEc3k0aldZaGtaVm8/view

SeeMoreDigital
12th October 2017, 21:22
Oh jeez @d3rd3vil,

That so-called 'sample' is a classic example where some idiot has simply changed the file extension from .ts to .mkv :eek:

The sample has not been muxed into the .mkv container!

LigH
16th October 2017, 12:23
Just in case you do not yet know already: The intel C++ compiler under Linux is not compatible with glibc 2.24-9 and newer (https://software.intel.com/en-us/articles/intel-compiler-not-compatible-with-glibc-224-9-and-newer), because:

According to x86-64 psABI, xmm0-xmm7 can be used to pass function parameters. But ICC also uses xmm8-xmm15 to pass function parameters which violates x86-64 psABI.

As a workaround, you can set environment variable LD_BIND_NOW=1 by

# export LD_BIND_NOW=1

This seems to be exposed especially on CPU's with AVX support. Of course, x265 will mainly use hand-crafted assembly where possible. But where this is not yet available ... you may have to be aware of possible risks if a recent version of glibc is used (well, I am not sure if x265 uses that, but I believe it is a quite basic library).

There are bug reports from the glibc project (https://sourceware.org/bugzilla/show_bug.cgi?id=21236) and RedHat (https://bugzilla.redhat.com/show_bug.cgi?id=1499012).

Please don't mind me if this issue is irrelevant for x265. I just assumed that a cross-platform project using AVX instructions may be among the possibly affected.

Archimondro
18th October 2017, 19:24
Hey Guys

Im encoding some Videos to h.265 using megui and x265 Encoder.
In 95% everything runs smooth, but from time to time i encounter an error. Half of the time when i restart the encode, it works, withouth changing anything.

Here is the Log:
[Error] Log for job3 (video, Matrix.(03).2003.Revolutions.German.AAC51.DL.1080p.BluRay.x264-Kristallprinz.mkv.avs -> Matrix.(03).2003.Revolutions.German.AAC51.DL.1080p.BluRay.hevc)
-[Information] [18.10.2017 10:08:19] Started handling job
-[Information] [18.10.2017 10:08:19] Preprocessing
-[Information] [18.10.2017 10:08:19] AviSynth input script
--[NoImage] global MeGUI_darx = 120
--[NoImage] global MeGUI_dary = 49
--[NoImage] #resize
--[NoImage] LoadPlugin("C:\Users\Gandolf\Desktop\meGUI\tools\lsmash\LSMASHSource.dll")
--[NoImage] LWLibavVideoSource("F:\MeguiWorking\1g2hykjs.0bm\Matrix.(03).2003.Revolutions.German.AAC51.DL.1080p.BluRay.x264-Kristallprinz.mkv")
-[Information] [18.10.2017 10:08:30] resolution: 1920x784
-[Information] [18.10.2017 10:08:30] frame rate: 24000/1001
-[Information] [18.10.2017 10:08:30] frames: 185956
-[Information] [18.10.2017 10:08:30] aspect ratio (avs): 120:49 (2.449)
-[Information] [18.10.2017 10:08:30] custom command line: --bframes 6 --pmode --pools 24,0 --pme --wpp --me star
-[Information] [18.10.2017 10:08:31] Job command line: "C:\Users\Gandolf\Desktop\meGUI\tools\x265\avs4x26x.exe" --x26x-binary "C:\Users\Gandolf\Desktop\meGUI\tools\x265\x64\x265.exe" --preset slow --crf 24.0 --bframes 6 --pmode --pools 24,0 --pme --wpp --me star --sar 1:1 --output "F:\MeguiWorking\1g2hykjs.0bm\Matrix.(03).2003.Revolutions.German.AAC51.DL.1080p.BluRay.hevc" "F:\MeguiWorking\1g2hykjs.0bm\Matrix.(03).2003.Revolutions.German.AAC51.DL.1080p.BluRay.x264-Kristallprinz.mkv.avs"
-[Information] [18.10.2017 10:08:31] Process started
-[Information] [18.10.2017 10:08:31] Standard output stream
--[Information] [18.10.2017 15:44:42] avs [info]: AviSynth 2.60, build:Mar 31 2015 [16:38:54]
--[Information] [18.10.2017 15:44:42] avs [info]: Video colorspace: YV12
--[Information] [18.10.2017 15:44:42] avs [info]: Video resolution: 1920x784
--[Information] [18.10.2017 15:44:42] avs [info]: Video framerate: 24000/1001
--[Information] [18.10.2017 15:44:42] avs [info]: Video framecount: 185956
--[Information] [18.10.2017 15:44:42] avs4x26x [info]: "C:\Users\Gandolf\Desktop\meGUI\tools\x265\x64\x265.exe" - --preset slow --crf 24.0 --bframes 6 --pmode --pools 24,0 --pme --wpp --me star --sar 1:1 --output F:\MeguiWorking\1g2hykjs.0bm\Matrix.(03).2003.Revolutions.German.AAC51.DL.1080p.BluRay.hevc --frames 185956 --fps 24000/1001 --input-res 1920x784 --input-csp i420
-[Error] [18.10.2017 10:08:31] Standard error stream
--[Information] [18.10.2017 10:08:42] yuv [info]: 1920x784 fps 24000/1001 i420p8 sar 1:1 unknown frame count
--[Information] [18.10.2017 10:08:42] raw [info]: output file: F:\MeguiWorking\1g2hykjs.0bm\Matrix.(03).2003.Revolutions.German.AAC51.DL.1080p.BluRay.hevc
--[Information] [18.10.2017 10:08:42] x265 [info]: HEVC encoder version 2.5+2-18fa144d453e
--[Information] [18.10.2017 10:08:42] x265 [info]: build info [Windows][GCC 7.1.0][64 bit] 8bit+10bit+12bit
--[Information] [18.10.2017 10:08:42] x265 [info]: using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
--[Warning] [18.10.2017 10:08:42] x265 [warning]: Limit reference options 2 and 3 are not supported with pmode. Disabling limit reference
--[Information] [18.10.2017 10:08:42] x265 [info]: Main profile, Level-4 (Main tier)
--[Information] [18.10.2017 10:08:42] x265 [info]: Thread pool 0 using 24 threads on numa nodes 0
--[Information] [18.10.2017 10:08:42] x265 [info]: Slices : 1
--[Information] [18.10.2017 10:08:42] x265 [info]: frame threads / pool features : 4 / wpp(13 rows)+pmode+pme
--[Information] [18.10.2017 10:08:42] x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
--[Information] [18.10.2017 10:08:42] x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
--[Information] [18.10.2017 10:08:42] x265 [info]: ME / range / subpel / merge : star / 57 / 3 / 3
--[Information] [18.10.2017 10:08:42] x265 [info]: Keyframe min / max / scenecut / bias: 23 / 250 / 40 / 5.00
--[Information] [18.10.2017 10:08:42] x265 [info]: Lookahead / bframes / badapt : 25 / 6 / 2
--[Information] [18.10.2017 10:08:42] x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 0
--[Information] [18.10.2017 10:08:42] x265 [info]: References / ref-limit cu / depth : 4 / off / off
--[Information] [18.10.2017 10:08:42] x265 [info]: AQ: mode / str / qg-size / cu-tree : 1 / 1.0 / 32 / 1
--[Information] [18.10.2017 10:08:42] x265 [info]: Rate Control / qCompress : CRF-24.0 / 0.60
--[Information] [18.10.2017 10:08:42] x265 [info]: tools: rect limit-modes rd=4 psy-rd=2.00 rdoq=2 psy-rdoq=1.00
--[Information] [18.10.2017 10:08:42] x265 [info]: tools: rskip signhide tmvp strong-intra-smoothing lslices=4
--[Information] [18.10.2017 10:08:42] x265 [info]: tools: deblock sao
--[Error] [18.10.2017 15:44:42] avs [error]: Error occurred while writing frame 149307
--[Information] [18.10.2017 15:44:42] (Maybe x26x closed)
-[Error] [18.10.2017 15:44:42] Process exits with error: 0xC0000025 STATUS_NONCONTINUABLE_EXCEPTION (-1073741787)
-[Information] [18.10.2017 15:44:42] Job completed


My System:
-WIndows 10 64bit
-64gb RAM
-2x Xeon e5-2697-v3 (36C/72T)
&
-WIndows 10 64bit
-64gb RAM
-2x Xeon e5-2670-v3 (24C/48T)

There is more than enough free HDD space, that cant be the problem.

I run two Workers simulatneously, one with --pools 36,0 and the other --pools 0,36

It also happens when i set --pools 36,36 (running two or a single worker)

If you need any more information, let me know.

Cheers