diff options
| author | wm4 <nfxjfg@googlemail.com> | 2015-04-13 13:03:35 +0200 |
|---|---|---|
| committer | Michael Niedermayer <michaelni@gmx.at> | 2015-04-13 13:46:38 +0200 |
| commit | f4f3065c69cefd916c92ee2a8758bac799a30c00 (patch) | |
| tree | 15e28508c33092a1fc77992ad546e0ac6c7a9cea | |
| parent | d5dcd94630ca657f9c17d5e52fa9bbddbb32f8b6 (diff) | |
| download | ffmpeg-f4f3065c69cefd916c92ee2a8758bac799a30c00.tar.gz | |
h264: remove bogus YCgCo warning message
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.
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
| -rw-r--r-- | libavcodec/h264_slice.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/libavcodec/h264_slice.c b/libavcodec/h264_slice.c index a99bbd5143..57cc063045 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) |