On 22.10.24 04:37, James Almer wrote:
On 10/21/2024 8:51 PM, James Almer wrote:
On 10/21/2024 10:02 PM, martin schitter wrote:
I didn't participate in earlier rounds, but at least my opinion is
that we shouldn't add new pixel formats if they are only used for a
single codec and have no RIFF or ISOBMFF mapping.
hwaccels like Vulkan/VAAPI/QSV/D3DVA/VideoToolbox defining them is also
an argument in favor to add and map them.
YES! -- We should look forward and not only glorify the good old FOURCC
naming and legacy pixel data arrangements.
The more verbose and systematically ordered sets of pixel format
definitions used by those newer GPU processing oriented APIs (e.g. the
vulkan one: https://docs.vulkan.org/spec/latest/chapters/formats.html)
are very useful in practice. Supporting them makes code much more
compatible and future-proof.
Martin
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
