Sounds like a bug in some assembler code in x265 and x264, not a bug in Hybrid itself, so probably not something I can really help.
x264 has two options:
looking at https://code.videolan.org/videolan/x264/...ter/x264.h
Differently to what the command line states one can also list the parameters for asm with strings.
Potential values are listed in checkasm.c (https://code.videolan.org/videolan/x264/...asm.c#L189)
So what you could do is:
a. enable debug output (likE stated in the sticky; alternatively the report file also includes this info)
b. check out when x264 crashes which extension it is using. The debug output should contain a line like:
which states the used extension and would correspond to a x264 command line addition like:
(yours will probably contain different options)
c. remove one of the options, add the addition under x264->Misc->Imports/Additions->Command line->Addition and try encoding.
Repeat the last step until you figure out which assembler optimization is causing the issue.
d. report the problem to the x264 developers
Same thing for x265, see: https://x265.readthedocs.io/en/master/cl...option-asm
----
I attached the latest x264/x265 builds I compiled (no code changes since then) and attahed them, so you can try whether extracting the attached file into your Hybrid/64bit folder and replacing the x264.exe and x265.exe helps.
I doubt it since at least the x265 commit list (https://bitbucket.org/multicoreware/x265_git/commits/) does not mention anything that seems related.
Cu Selur
x264 has two options:
--asm <integer> Override CPU detection
--no-asm Disable all CPU optimizationsDifferently to what the command line states one can also list the parameters for asm with strings.
Potential values are listed in checkasm.c (https://code.videolan.org/videolan/x264/...asm.c#L189)
So what you could do is:
a. enable debug output (likE stated in the sticky; alternatively the report file also includes this info)
b. check out when x264 crashes which extension it is using. The debug output should contain a line like:
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2--asm mmx,sse2fast,ssse3,sse42,avx,fma3,bmi2,avx2c. remove one of the options, add the addition under x264->Misc->Imports/Additions->Command line->Addition and try encoding.
Repeat the last step until you figure out which assembler optimization is causing the issue.
d. report the problem to the x264 developers
Same thing for x265, see: https://x265.readthedocs.io/en/master/cl...option-asm
----
I attached the latest x264/x265 builds I compiled (no code changes since then) and attahed them, so you can try whether extracting the attached file into your Hybrid/64bit folder and replacing the x264.exe and x265.exe helps.
I doubt it since at least the x265 commit list (https://bitbucket.org/multicoreware/x265_git/commits/) does not mention anything that seems related.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.