View Single Post
Old 14th September 2019, 13:59   #1818  |  Link
redbtn
Registered User
 
redbtn's Avatar
 
Join Date: Jan 2019
Location: Russia
Posts: 105
Quote:
Originally Posted by LoRd_MuldeR View Post
So, I suppose you manually updated the x265 binary to v3.1+14. Does it only happen with x265 v3.1+14, but not with the x265 binary that originally shipped with Simple x264 Launcher? Is the "issue" reproducible?

Also: Which specific x265 build are you using? Are there any "custom" patches included in that build? If you run that binary in the terminal (no GUI), does the output look normal?
Yes, the "issue" is reproducible. I used builds from msystem.waw.pl/x265

I've made few tests:

1) x265 that shipped with Simple x264 Launcher - OK
2) x265 (3.1+14 and 3.1+19) AVX2 VS2019 from msystem.waw.pl/x265 - Have this bug
3) x265 (3.1+19) AVX2 GCC9.2 from from msystem.waw.pl/x265 - OK
4) x265 (3.1+19) build by Barough - OK

So, it seems like a VS2019 compile bug. So, LoRd_MuldeR , i'm sorry for disturbing.

Last edited by redbtn; 14th September 2019 at 14:03.
redbtn is offline   Reply With Quote