From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/libsvtav1: add version guard for external param
Date: Sun, 12 Nov 2023 20:27:27 +0530
Message-ID: <00ca1ae5-8673-4bdf-8a73-4d4b634ad468@gyani.pro> (raw)
In-Reply-To: <20231108045534.1529-1-ffmpeg@gyani.pro>
On 2023-11-08 10:25 am, Gyan Doshi wrote:
> Setting of external param 'force_key_frames' was added in 7bcc1b4eb8.
> It is available since v1.1.0 but ffmpeg allows linking against v0.9.0.
Plan to push tomorrow, barring objections.
Regards,
Gyan
> ---
> libavcodec/libsvtav1.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/libavcodec/libsvtav1.c b/libavcodec/libsvtav1.c
> index 8d2c7f3be4..862192945b 100644
> --- a/libavcodec/libsvtav1.c
> +++ b/libavcodec/libsvtav1.c
> @@ -250,6 +250,7 @@ static int config_enc_params(EbSvtAv1EncConfiguration *param,
> if (avctx->gop_size > 1)
> param->intra_period_length = avctx->gop_size - 1;
>
> +#if SVT_AV1_CHECK_VERSION(1, 1, 0)
> // In order for SVT-AV1 to force keyframes by setting pic_type to
> // EB_AV1_KEY_PICTURE on any frame, force_key_frames has to be set. Note
> // that this does not force all frames to be keyframes (it only forces a
> @@ -260,6 +261,7 @@ static int config_enc_params(EbSvtAv1EncConfiguration *param,
> // to be updated to set force_key_frames accordingly.
> if (avctx->gop_size == 1)
> param->force_key_frames = 1;
> +#endif
>
> if (avctx->framerate.num > 0 && avctx->framerate.den > 0) {
> param->frame_rate_numerator = avctx->framerate.num;
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-11-12 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 4:55 Gyan Doshi
2023-11-12 14:57 ` Gyan Doshi [this message]
2023-11-13 7:48 ` Gyan Doshi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00ca1ae5-8673-4bdf-8a73-4d4b634ad468@gyani.pro \
--to=ffmpeg@gyani.pro \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git