[FFmpeg-trac] #8455(avcodec:open): libaom-av1 damages brightness range by switching yuvj420p to yuv420p

[FFmpeg]

#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):

 "but you're saying ffmpeg is correct and every browser is broken?"

 Both Mozilla and Chrome use ffmpeg on all platforms anyway to decode and
 demux. But Chrome uses HW accelerated GPU shaders to do YCbCr transforms
 and has specific HW decoder, including newer Directx12on11 and new Mojo
 Video Decoder, that uses MFF. There is this thing called Surface API in
 modern Android to support HDR and stuff. There is a bug somehwere that
 breaks full range. AFAIK it is in Android itself. You can install latest
 Chrome Canary and check there or use --disable-gpu Chrome command option
 to turn of YCbCr shaders. YCbCr shaders in chrome also have a bug that
 makes them off-by-one.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/8455#comment:26>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker