From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v3 1/3] avcodec/nvenc: Enable recovery point SEI for intra refresh mode
Date: Thu, 23 Jan 2025 19:02:26 +0100
Message-ID: <beef0cf8-5550-43c7-b7ee-8015aca7884a@rothenpieler.org> (raw)
In-Reply-To: <tencent_A492AF723919C0F9B5686A7A034D6BD67D0A@qq.com>
On 23.01.2025 15:17, Zhao Zhili wrote:
> From: Zhao Zhili <zhilizhao@tencent.com>
>
> Otherwise all frames can be dropped after seek without the
> output_corrupt/showall flags.
> ---
> libavcodec/nvenc.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/libavcodec/nvenc.c b/libavcodec/nvenc.c
> index 06e3fb81a4..68b1b661e4 100644
> --- a/libavcodec/nvenc.c
> +++ b/libavcodec/nvenc.c
> @@ -1247,6 +1247,7 @@ static av_cold int nvenc_setup_h264_config(AVCodecContext *avctx)
> h264->intraRefreshPeriod = cc->gopLength;
> h264->intraRefreshCnt = cc->gopLength - 1;
> cc->gopLength = NVENC_INFINITE_GOPLENGTH;
> + h264->outputRecoveryPointSEI = 1;
> #ifdef NVENC_HAVE_SINGLE_SLICE_INTRA_REFRESH
> h264->singleSliceIntraRefresh = ctx->single_slice_intra_refresh;
> #endif
> @@ -1380,6 +1381,7 @@ static av_cold int nvenc_setup_hevc_config(AVCodecContext *avctx)
> hevc->intraRefreshPeriod = cc->gopLength;
> hevc->intraRefreshCnt = cc->gopLength - 1;
> cc->gopLength = NVENC_INFINITE_GOPLENGTH;
> + hevc->outputRecoveryPointSEI = 1;
> #ifdef NVENC_HAVE_SINGLE_SLICE_INTRA_REFRESH
> hevc->singleSliceIntraRefresh = ctx->single_slice_intra_refresh;
> #endif
Is there any reason someone might not want this?
Or could it break certain scenarios?
Reads to me like it'd only make the bitstream slightly larger, or are
there other implications?
_______________________________________________
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:[~2025-01-23 18:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 14:17 Zhao Zhili
2025-01-23 18:02 ` Timo Rothenpieler [this message]
2025-01-24 3:57 ` Zhao Zhili
2025-01-24 15:05 ` Kieran Kunhya via ffmpeg-devel
2025-01-24 19:08 ` Timo Rothenpieler
2025-02-03 17:45 ` Zhao Zhili
-- strict thread matches above, loose matches on Subject: below --
2025-01-23 14:12 Zhao Zhili
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=beef0cf8-5550-43c7-b7ee-8015aca7884a@rothenpieler.org \
--to=timo@rothenpieler.org \
--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