aboutsummaryrefslogtreecommitdiffstats
path: root/libavcodec/h264.h
diff options
context:
space:
mode:
authorAndreas Cadhalpun <Andreas.Cadhalpun@googlemail.com>2015-06-09 23:38:26 +0200
committerAndreas Cadhalpun <Andreas.Cadhalpun@googlemail.com>2015-06-12 21:22:00 +0200
commit1189af429211ac650aac730368a6cf5b23756605 (patch)
tree6e91ea70c031cb700402c5f6b82905eb36cf930c /libavcodec/h264.h
parentb5c71fba594353b0676fa41c1f279d42adb6e716 (diff)
downloadffmpeg-1189af429211ac650aac730368a6cf5b23756605.tar.gz
h264: update avctx width/height/pix_fmt when returning frame
Inconsistencies between the dimensions/pixel format of avctx and the frame can confuse API users. For example this can crash the demuxing_decoding example. Back up the previous values and restore them, when decoding the next frame. This is necessary, because these can be different between the returned frame and the last decoded frame. Reviewed-by: Michael Niedermayer <michaelni@gmx.at> Signed-off-by: Andreas Cadhalpun <Andreas.Cadhalpun@googlemail.com>
Diffstat (limited to 'libavcodec/h264.h')
-rw-r--r--libavcodec/h264.h8
1 files changed, 8 insertions, 0 deletions
diff --git a/libavcodec/h264.h b/libavcodec/h264.h
index 95db912465..548510d793 100644
--- a/libavcodec/h264.h
+++ b/libavcodec/h264.h
@@ -519,6 +519,14 @@ typedef struct H264Context {
int width, height;
int chroma_x_shift, chroma_y_shift;
+ /**
+ * Backup frame properties: needed, because they can be different
+ * between returned frame and last decoded frame.
+ **/
+ int backup_width;
+ int backup_height;
+ enum AVPixelFormat backup_pix_fmt;
+
int droppable;
int coded_picture_number;
int low_delay;