> On Aug 13, 2021, at 3:00 PM, Anselm Busse <[email protected]> wrote: > > Hey everyone, > > I posted this patch almost a month ago and got no reaction. Is there anything > else I have to/can do to get this fix merged? I’m a little bit worried that > it gets lost.
LGTM. > > - Anselm > >> Am 21.07.2021 um 20:00 schrieb Anselm Busse <[email protected]>: >> >> This commit fixes the bug as report in https://trac.ffmpeg.org/ticket/9231 >> by removing the line that overwrites the user settings for max_b_frames. >> >> Signed-off-by: Anselm Busse <[email protected]> >> --- >> libavcodec/videotoolboxenc.c | 1 - >> 1 file changed, 1 deletion(-) >> >> diff --git a/libavcodec/videotoolboxenc.c b/libavcodec/videotoolboxenc.c >> index 4eaabed5d8..8dfd6e3d0c 100644 >> --- a/libavcodec/videotoolboxenc.c >> +++ b/libavcodec/videotoolboxenc.c >> @@ -1398,7 +1398,6 @@ static int vtenc_configure_encoder(AVCodecContext >> *avctx) >> } >> >> vtctx->codec_id = avctx->codec_id; >> - avctx->max_b_frames = 16; >> >> if (vtctx->codec_id == AV_CODEC_ID_H264) { >> vtctx->get_param_set_func = >> CMVideoFormatDescriptionGetH264ParameterSetAtIndex; >> -- >> 2.32.0 >> > > _______________________________________________ > ffmpeg-devel mailing list > [email protected] > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > [email protected] with subject "unsubscribe". _______________________________________________ ffmpeg-devel mailing list [email protected] https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
