On 20/01/15 09:07, Anton Khirnov wrote:
They are always constructed anew when needed, so there is no need to reset them explicitly. --- libavcodec/h264.c | 4 ---- 1 file changed, 4 deletions(-)diff --git a/libavcodec/h264.c b/libavcodec/h264.c index 7e3b70f..d203f0a 100644 --- a/libavcodec/h264.c +++ b/libavcodec/h264.c @@ -1057,10 +1057,6 @@ void ff_h264_flush_change(H264Context *h) if (h->cur_pic_ptr) h->cur_pic_ptr->reference = 0; h->first_field = 0; - memset(h->ref_list[0], 0, sizeof(h->ref_list[0])); - memset(h->ref_list[1], 0, sizeof(h->ref_list[1])); - memset(h->default_ref_list[0], 0, sizeof(h->default_ref_list[0])); - memset(h->default_ref_list[1], 0, sizeof(h->default_ref_list[1])); ff_h264_reset_sei(h); h->recovery_frame = -1; h->frame_recovered = 0;
Could you check another time before pushing it? In particular check the vaapi usage. It looks fine to me but I'm afraid to be wrong.
lu _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
