On 2/8/2020 7:20 PM, Andriy Gelman wrote:
> From: Andriy Gelman <andriy.gel...@gmail.com>
>
> FMO is not supported and fields related to FMO are not parsed, meaning
> that any fields which follow will be corrupt.
> ---
> libavcodec/h264_ps.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/libavcodec/h264_ps.c b/libavcodec/h264_ps.c
> index edbaa96b64e..80216854079 100644
> --- a/libavcodec/h264_ps.c
> +++ b/libavcodec/h264_ps.c
> @@ -794,6 +794,8 @@ int ff_h264_decode_picture_parameter_set(GetBitContext
> *gb, AVCodecContext *avct
> if (pps->slice_group_count > 1) {
> pps->mb_slice_group_map_type = get_ue_golomb(gb);
> av_log(avctx, AV_LOG_ERROR, "FMO not supported\n");
Should probably be avpriv_report_missing_feature() instead. Look right
above this chunk for an usage example of this function.
> + ret = AVERROR_PATCHWELCOME;
> + goto fail;
> }
> pps->ref_count[0] = get_ue_golomb(gb) + 1;
> pps->ref_count[1] = get_ue_golomb(gb) + 1;
>
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
