YCgCo decoding works just fine. It depends on the API user what is done
with the output. Some API users might support it, some not. Some users
might support it under certain circumstances only.
It is not the job of the decoder to print this message. If the API user
supports it, this message is extremely unhelpful.
---
Resent because I accidentally posted this as a reply to an old thread.
---
libavcodec/h264_slice.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/libavcodec/h264_slice.c b/libavcodec/h264_slice.c
index d3c57eb..7a55e02 100644
--- a/libavcodec/h264_slice.c
+++ b/libavcodec/h264_slice.c
@@ -1004,8 +1004,6 @@ static enum AVPixelFormat get_pixel_format(H264Context
*h, int force_callback)
*fmt++ = AV_PIX_FMT_VDPAU;
#endif
if (CHROMA444(h)) {
- if (h->avctx->colorspace == AVCOL_SPC_YCGCO)
- av_log(h->avctx, AV_LOG_WARNING, "Detected unsupported YCgCo
colorspace.\n");
if (h->avctx->colorspace == AVCOL_SPC_RGB)
*fmt++ = AV_PIX_FMT_GBRP;
else if (h->avctx->color_range == AVCOL_RANGE_JPEG)
--
2.1.4
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
