Browse Source

vaapi_h265: Fix buffering parameters

A decoder may need this to be set correctly to output frames in the
right order.

(cherry picked from commit b8cac1e830)
tags/n3.3
Mark Thompson 8 years ago
parent
commit
30ebabca7c
1 changed files with 4 additions and 4 deletions
  1. +4
    -4
      libavcodec/vaapi_encode_h265.c

+ 4
- 4
libavcodec/vaapi_encode_h265.c View File

@@ -897,12 +897,12 @@ static int vaapi_encode_h265_init_sequence_params(AVCodecContext *avctx)

mseq->log2_max_pic_order_cnt_lsb_minus4 = 8;
mseq->vps_sub_layer_ordering_info_present_flag = 0;
mseq->vps_max_dec_pic_buffering_minus1[0] = 1;
mseq->vps_max_num_reorder_pics[0] = ctx->b_per_p;
mseq->vps_max_dec_pic_buffering_minus1[0] = (avctx->max_b_frames > 0) + 1;
mseq->vps_max_num_reorder_pics[0] = (avctx->max_b_frames > 0);
mseq->vps_max_latency_increase_plus1[0] = 0;
mseq->sps_sub_layer_ordering_info_present_flag = 0;
mseq->sps_max_dec_pic_buffering_minus1[0] = 1;
mseq->sps_max_num_reorder_pics[0] = ctx->b_per_p;
mseq->sps_max_dec_pic_buffering_minus1[0] = (avctx->max_b_frames > 0) + 1;
mseq->sps_max_num_reorder_pics[0] = (avctx->max_b_frames > 0);
mseq->sps_max_latency_increase_plus1[0] = 0;

mseq->vps_timing_info_present_flag = 1;


Loading…
Cancel
Save