[FFmpeg-trac] #11515(avcodec:new): Consider NV12 / P010 output pixel format support
FFmpeg
trac at avcodec.org
Wed Mar 26 11:54:36 EET 2025
#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):
I still do not get this issue. Imagine you have 120 fps stream. The
inverse of that is how much you have time to spend on convert, and it is
so much more than conversion from anything to semi-planar NV12 or weird
packed chroma, planar luma format like P010. Whatever you are doing here
it is clearly wrong. AVX512 and other can be used to accelerate this
further.
GPUs adding more garbage formats is also stupid since it adds even more
transistors in silicon budget.
Changing h264 decoder or x264 encoder or whatever to a different pixel
format is even more insane, since the question is what and how oixels are
koced internally and it is 100x more complex than whatever you want to
output.
Moroever nvenc supports p010 input and it makes sense to use HW encoder
more less energy and less problems.
Finally, as I said it is impossible to decode 4k60 VP9 already in
software, so it does not even matter, because with Hardware overlays
(color management of which Intel will fix soon, I hope) output to display
directly, CPU just draws the overlay and menus.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/11515#comment:7>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list