Am 24.02.2016, 13:50 Uhr, schrieb Mario *LigH* Rohkrämer <[email protected]>:
Am 24.02.2016, 13:07 Uhr, schrieb Mario *LigH* Rohkrämer
<[email protected]>:
I will try to recreate this result with some older versions to narrow
down a possible reason...
This issue was introduced between versions 1.8+167-e951ab673b1c and
1.8+201-769081eb5f4c.
'Ma' in the doom9 forum discovered that it happened after the big patch
for 2-pass CRF:
https://bitbucket.org/multicoreware/x265/commits/73cc1cd4c7fc0920a6b126fefebeea6269749498
http://forum.doom9.org/showthread.php?p=1758434#post1758434
Quite an expectable discovery.
--
Fun and success!
Mario *LigH* Rohkrämer
mailto:[email protected]
_______________________________________________
x265-devel mailing list
[email protected]
https://mailman.videolan.org/listinfo/x265-devel
