[FFmpeg-devel] [PATCH]Fill range_map* in VC1Context
Carl Eugen Hoyos
cehoyos
Sat Jan 10 03:59:49 CET 2009
Hi!
NVIDIA suggests to actually fill the range_map* variables in VC1Context.
(Do we have a sample that uses these flags?)
Please comment, Carl Eugen
-------------- next part --------------
Index: libavcodec/vc1.c
===================================================================
--- libavcodec/vc1.c (revision 16504)
+++ libavcodec/vc1.c (working copy)
@@ -1086,13 +1086,13 @@
}
if(v->extended_mv)
v->extended_dmv = get_bits1(gb);
- if(get_bits1(gb)) {
+ if((v->range_mapy_flag = get_bits1(gb))) {
av_log(avctx, AV_LOG_ERROR, "Luma scaling is not supported, expect wrong picture\n");
- skip_bits(gb, 3); // Y range, ignored for now
+ v->range_mapy = get_bits(gb, 3);
}
- if(get_bits1(gb)) {
+ if((v->range_mapuv_flag = get_bits1(gb))) {
av_log(avctx, AV_LOG_ERROR, "Chroma scaling is not supported, expect wrong picture\n");
- skip_bits(gb, 3); // UV range, ignored for now
+ v->range_mapuv = get_bits(gb, 3);
}
av_log(avctx, AV_LOG_DEBUG, "Entry point info:\n"
More information about the ffmpeg-devel
mailing list