On 10/22/2024 11:26 AM, martin schitter wrote:


On 22.10.24 14:48, James Almer wrote:
+    AV_PIX_FMT_Y216BE,      ///< packed YUV 4:2:2 like YUYV422, 32bpp, big-endian +    AV_PIX_FMT_Y216LE,      ///< packed YUV 4:2:2 like YUYV422, 32bpp, little-endian

Why to you avoid any more verbose naming, where any developer would see the actual order of components by just looking at the actual letters to avoid wrong usage?

It's too late for that. This naming scheme goes back more than a decade. It would require a big, API breaking and disruptive overhaul to switch to one where the names follow the component order and bitdepth.


IMHO this would make anything much more handy and less error-prone than this old-fashioned FOURCC codes, which are hard to remember and very uncomfortable to grep in source code.

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

_______________________________________________
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".

Reply via email to