Oh no. Firefox is using nearest neighbor chroma upsampling. Literally unusable. I'm going back to Chromium.pic.twitter.com/V1Vxu1Dwnq
-
Linux/Gentoo/amd64/Intel. Here's a test case. First screenshot is ffplay, second is Firefox (both scaled x4). Look at the diagonals in particular. Can't take a Chromium one right now since Chromium crashes when opening it for me now
https://mrcn.st/t/chromatest_420.mp4 …pic.twitter.com/W7pHi56RLy
If it's using libswscale, it's probably asking for cheap quality. If shaders/GPU rendering are involved, then it could be more interesting to fix.
-
-
Turns out videos are, in fact, what's crashing my Chromium... https://bugs.chromium.org/p/chromium/issues/detail?id=1095962 …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
They use libyuv (Chromium project, didn't dig for details on what they're doing differently) Firefox WebRender uses a better filter. libswscale also does nearest neighbor chroma upsampling by default for 1:1 frame size (ffplay has SDL do pixel format conversion when possible)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.