[FFmpeg-trac] #11515(avcodec:new): Consider NV12 / P010 output pixel format support

[FFmpeg]

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

 Replying to [comment:11 compn]:
 > GPUbuf ? /s
 >
 > patches are welcome for this change in ffmpeg.
 >
 > to clear up things in this trac issue, would you want ffmpeg to pad
 everything to a certain colorspace internally? or would this be on a per-
 codec basis?

 This ticket is purely about the pixel-formats (as in memory
 representations). The core point is that GPUs, or more specifically
 display engines, often have fixed function hardware for colorspace etc.
 conversions. Right now those can typically only be used with hw-decoders.
 Those produce the same values as sw-decoders, just with different formats.

 > or do you want an output device for nv12? like the xv shared memory
 buffer outdev
 https://git.ffmpeg.org/gitweb/ffmpeg.git/blob/HEAD:/libavdevice/xv.c

 I don't think there's a need for something like that. Clients like
 Gstreamer can allocate DMABufs that are compatible with both the
 GPU/display engine and the decoder (not trivial but possible), and pass
 references to them around through various APIs (including Wayland and KMS)
 - that already works.

 > said another way, which specific files in ffmpeg would you want to be
 changed ?

 From what I understand this would require (substantial) changes to the
 individual codec implementations - which is why I can fully understand
 reluctance from codec devs.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/11515#comment:12>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker