From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavc/vaapi_encode: fix propagating durations and opaques
Date: Wed, 1 Feb 2023 02:59:47 +0000
Message-ID: <98a71bdc2e90bb875f487ff416f72b0674614e88.camel@intel.com> (raw)
In-Reply-To: <20230131131447.24732-1-anton@khirnov.net>
On Di, 2023-01-31 at 14:14 +0100, Anton Khirnov wrote:
> input_image is freed by the time the output packet is constructed, so we
> need to store copies in VAAPIEncodePicture.
> ---
> Is this better?
> ---
> libavcodec/vaapi_encode.c | 22 +++++++++++++++++-----
> libavcodec/vaapi_encode.h | 4 ++++
> 2 files changed, 21 insertions(+), 5 deletions(-)
>
> diff --git a/libavcodec/vaapi_encode.c b/libavcodec/vaapi_encode.c
> index 6787b90e8d6..bfca315a7ad 100644
> --- a/libavcodec/vaapi_encode.c
> +++ b/libavcodec/vaapi_encode.c
> @@ -695,7 +695,7 @@ static int vaapi_encode_output(AVCodecContext *avctx,
> pkt->flags |= AV_PKT_FLAG_KEY;
>
> pkt->pts = pic->pts;
> - pkt->duration = pic->input_image->duration;
> + pkt->duration = pic->duration;
>
> vas = vaUnmapBuffer(ctx->hwctx->display, pic->output_buffer);
> if (vas != VA_STATUS_SUCCESS) {
> @@ -706,10 +706,11 @@ static int vaapi_encode_output(AVCodecContext *avctx,
> }
>
> // for no-delay encoders this is handled in generic codec
> - if (avctx->codec->capabilities & AV_CODEC_CAP_DELAY) {
> - err = ff_encode_reordered_opaque(avctx, pkt, pic->input_image);
> - if (err < 0)
> - goto fail;
> + if (avctx->codec->capabilities & AV_CODEC_CAP_DELAY &&
> + avctx->flags & AV_CODEC_FLAG_COPY_OPAQUE) {
> + pkt->opaque = pic->opaque;
> + pkt->opaque_ref = pic->opaque_ref;
> + pic->opaque_ref = NULL;
> }
>
> av_buffer_unref(&pic->output_buffer_ref);
> @@ -785,6 +786,8 @@ static int vaapi_encode_free(AVCodecContext *avctx,
> av_frame_free(&pic->input_image);
> av_frame_free(&pic->recon_image);
>
> + av_buffer_unref(&pic->opaque_ref);
> +
> av_freep(&pic->param_buffers);
> av_freep(&pic->slices);
> // Output buffer should already be destroyed.
> @@ -1152,6 +1155,15 @@ static int vaapi_encode_send_frame(AVCodecContext
> *avctx, AVFrame *frame)
>
> pic->input_surface = (VASurfaceID)(uintptr_t)frame->data[3];
> pic->pts = frame->pts;
> + pic->duration = frame->duration;
> +
> + if (avctx->flags & AV_CODEC_FLAG_COPY_OPAQUE) {
> + err = av_buffer_replace(&pic->opaque_ref, frame->opaque_ref);
> + if (err < 0)
> + goto fail;
> +
> + pic->opaque = frame->opaque;
> + }
>
> av_frame_move_ref(pic->input_image, frame);
>
> diff --git a/libavcodec/vaapi_encode.h b/libavcodec/vaapi_encode.h
> index 359f954ffff..a1e639f56b0 100644
> --- a/libavcodec/vaapi_encode.h
> +++ b/libavcodec/vaapi_encode.h
> @@ -75,8 +75,12 @@ typedef struct VAAPIEncodePicture {
> int64_t display_order;
> int64_t encode_order;
> int64_t pts;
> + int64_t duration;
> int force_idr;
>
> + void *opaque;
> + AVBufferRef *opaque_ref;
> +
> #if VA_CHECK_VERSION(1, 0, 0)
> // ROI regions.
> VAEncROI *roi;
LGTM and the command for transcoding with vaapi works well now.
BRs
Haihao
_______________________________________________
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-02-01 3:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 5:23 [FFmpeg-devel] [PATCH] lavc/vaapi_encode: fix segfault Xiang, Haihao
2023-01-30 7:55 ` Anton Khirnov
2023-01-30 15:15 ` Xiang, Haihao
2023-01-31 13:14 ` [FFmpeg-devel] [PATCH] lavc/vaapi_encode: fix propagating durations and opaques Anton Khirnov
2023-02-01 2:59 ` Xiang, Haihao [this message]
2023-02-02 2:47 ` Xiang, Haihao
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=98a71bdc2e90bb875f487ff416f72b0674614e88.camel@intel.com \
--to=haihao.xiang-at-intel.com@ffmpeg.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