#8530 closed defect (invalid)
HDR10+ metadata in nvenc and decoding support
| Reported by: | Balling | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | undetermined |
| Version: | git-master | Keywords: | |
| Cc: | izadi@google.com | Blocked By: | |
| Blocking: | Reproduced by developer: | no | |
| Analyzed by developer: | no |
Description
Google already fully wrote the code for their Google Videos and Youtube HDR10+ (works on Galaxy S10), and they want to submit code to us. As a whole implemenation could be too big, lets ask the author https://patchwork.ffmpeg.org/project/ffmpeg/patch/20200210194408.251496-1-moh.izadi@gmail.com/ to give us repo link instead of patches (just like in linux kernel).
Change History (3)
comment:1 by , 5 years ago
| Component: | avcodec → undetermined |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
| Type: | enhancement → defect |
comment:2 by , 5 years ago
comment:3 by , 3 years ago
Nice test video that has the same colors in cycle yet HDR10+ metadata is changing and so must change the colors. Crazy. https://drive.google.com/file/d/1mvahcFpCFCN8cO8aFI0Q6stI9-Nnvdrc/view?usp=sharing (or here https://ff.de/hdr10plus-metadata-test/)
Same for Dolby Vision profile 8 RPU. https://drive.google.com/file/d/1-8C0ZYnIhEqOVJQ532hIJobP5XR6A7gj/view?usp=sharing
Note:
See TracTickets
for help on using tickets.
No meta-tickets please, including no tickets to „remind“.
No repos please, only patches sent to the development mailing list.