[FFmpeg-trac] #8455(avcodec:open): libaom-av1 damages brightness range by switching yuvj420p to yuv420p
FFmpeg
trac at avcodec.org
Sat Aug 28 20:02:59 EEST 2021
#8455: libaom-av1 damages brightness range by switching yuvj420p to yuv420p
-------------------------------------+-----------------------------------
Reporter: john123 | Owner: (none)
Type: enhancement | Status: open
Priority: wish | Component: avcodec
Version: git-master | Resolution:
Keywords: libaom | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-----------------------------------
Comment (by Balling):
Android Chrome does not support full range! At all, in all codecs! Even
windows one is very broken now and fixed only in Canary, but even there
rises black. I know since I am one of Android Chrome and Chromium color
developers. See (yes comment 97, it is a big thread):
https://bugs.chromium.org/p/chromium/issues/detail?id=1068690#c97
>switch from yuvj420p to yuv420p
There is no such thing as yuvj420p with new encoder like AV1 or jpeg2000!
It is just not supported. When you used that it selected limited range.
Now, modern way is to select yuv420p and then select the tange of that
yuv420p with -vf scale. Okay?
--
Ticket URL: <https://trac.ffmpeg.org/ticket/8455#comment:22>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list