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.
-- Fun and success! Mario *LigH* Rohkrämer mailto:[email protected] _______________________________________________ x265-devel mailing list [email protected] https://mailman.videolan.org/listinfo/x265-devel
