#11515: Consider NV12 / P010 output pixel format support
--------------------------------------+-----------------------------------
Reporter: Robert Mader | Owner: (none)
Type: defect | Status: new
Priority: normal | Component: avcodec
Version: unspecified | Resolution:
Keywords: nv12, p010 | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
--------------------------------------+-----------------------------------
Comment (by Balling):
>The pixel-format / pixel-representation is not dictated by the codec and
decoders are free to choose whatever format they see fit.
H.264 spec describes a decoder only, not encoder and does in fact mandate
pixel formats in which the overlaying of vector/raster primitives must
happen. Also they may be 9 bits per pixel, you know? Whether as output or
internally.
>and what most HW decoders chose
That is too simple. Until Nvidia did not even support q>The pixel-format
/ pixel-representation is not dictated by the codec and decoders are free
to choose whatever format they see fit.
H.264 spec describes a decoder only, not encoder and does in fact mandate
pixel formats in which the overlaying of vector/raster primitives must
happen. Also they may be 9 bits per pixel, you know? Whether as output or
internally.
>and what most HW decoders chose
Okay at this point why not go to 10 years ago when this happened
81147b5596ea19f7c5c153f4a534e9314d291fd3
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11515#comment:9>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac
To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".
