This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

x264 and x265
#2
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:
--asm <integer>         Override CPU detection
      --no-asm                Disable all CPU optimizations
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. Wink
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
which states the used extension and would correspond to a x264 command line addition like:
--asm mmx,sse2fast,ssse3,sse42,avx,fma3,bmi2,avx2
(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
Reply


Messages In This Thread
x264 and x265 - by humanoid86 - 27.08.2022, 10:37
RE: x264 and x265 - by Selur - 27.08.2022, 11:15
RE: x264 and x265 - by humanoid86 - 27.08.2022, 12:01
RE: x264 and x265 - by Selur - 27.08.2022, 12:11
RE: x264 and x265 - by humanoid86 - 28.08.2022, 07:53
RE: x264 and x265 - by Selur - 28.08.2022, 07:59
RE: x264 and x265 - by humanoid86 - 28.08.2022, 08:24
RE: x264 and x265 - by shijan - 28.08.2022, 23:35
RE: x264 and x265 - by humanoid86 - 29.08.2022, 05:03
RE: x264 and x265 - by Selur - 29.08.2022, 05:22
RE: x264 and x265 - by humanoid86 - 29.08.2022, 09:39
RE: x264 and x265 - by Selur - 29.08.2022, 18:21
RE: x264 and x265 - by humanoid86 - 30.08.2022, 04:33
RE: x264 and x265 - by Selur - 30.08.2022, 04:52
RE: x264 and x265 - by humanoid86 - 30.08.2022, 06:49
RE: x264 and x265 - by humanoid86 - 01.09.2022, 06:35
RE: x264 and x265 - by karthauzi - 02.09.2022, 16:21
RE: x264 and x265 - by Selur - 02.09.2022, 16:34
RE: x264 and x265 - by humanoid86 - 02.09.2022, 16:41
RE: x264 and x265 - by humanoid86 - 03.09.2022, 06:29
RE: x264 and x265 - by Selur - 03.09.2022, 07:06
RE: x264 and x265 - by humanoid86 - 03.09.2022, 07:27
RE: x264 and x265 - by humanoid86 - 03.09.2022, 08:50

Forum Jump:


Users browsing this thread: 1 Guest(s)