[FFmpeg-cvslog] avcodec/mpeg4videoenc: use MpegEncContext->picture_number instead of encode function parameter

Marton Balint git at videolan.org
Thu Jan 26 21:44:57 EET 2023


ffmpeg | branch: master | Marton Balint <cus at passwd.hu> | Sun Jan 22 00:58:22 2023 +0100| [7e4ad6e6a854c13f0c8b499a03cf50f21398874d] | committer: Marton Balint

avcodec/mpeg4videoenc: use MpegEncContext->picture_number instead of encode function parameter

They should be the same and that is what most encode functions use.

Signed-off-by: Marton Balint <cus at passwd.hu>

> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=7e4ad6e6a854c13f0c8b499a03cf50f21398874d
---

 libavcodec/mpeg4videoenc.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libavcodec/mpeg4videoenc.c b/libavcodec/mpeg4videoenc.c
index a2a14afbd0..e327334d59 100644
--- a/libavcodec/mpeg4videoenc.c
+++ b/libavcodec/mpeg4videoenc.c
@@ -1065,7 +1065,7 @@ int ff_mpeg4_encode_picture_header(MpegEncContext *s, int picture_number)
         if (!(s->avctx->flags & AV_CODEC_FLAG_GLOBAL_HEADER)) {
             if (s->avctx->strict_std_compliance < FF_COMPLIANCE_VERY_STRICT)  // HACK, the reference sw is buggy
                 mpeg4_encode_visual_object_header(s);
-            if (s->avctx->strict_std_compliance < FF_COMPLIANCE_VERY_STRICT || picture_number == 0)  // HACK, the reference sw is buggy
+            if (s->avctx->strict_std_compliance < FF_COMPLIANCE_VERY_STRICT || s->picture_number == 0)  // HACK, the reference sw is buggy
                 mpeg4_encode_vol_header(s, 0, 0);
         }
         if (!(s->workaround_bugs & FF_BUG_MS))



More information about the ffmpeg-cvslog mailing list