Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Sean McGovern <gseanmcg@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v11 07/14] avcodec/vaapi_encode: extract the init and close function to base layer
Date: Sat, 25 May 2024 10:18:43 -0400
Message-ID: <CAPBf_O=b7=mMCczMQHbNwQheS4SaBZWKpOXmim=M120vWOk9Ng@mail.gmail.com> (raw)
In-Reply-To: <e8329dc1-e4e9-4402-8cc2-bed811ea871a@lynne.ee>

Hi,


On Sat, May 25, 2024, 09:07 Lynne via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
wrote:

> On 25/05/2024 12:30, tong1.wu-at-intel.com@ffmpeg.org wrote:
> > From: Tong Wu <tong1.wu@intel.com>
> >
> > Related parameters such as device context, frame context are also moved
> > to base layer.
> >
> > Signed-off-by: Tong Wu <tong1.wu@intel.com>
> > ---
> >   libavcodec/hw_base_encode.c     | 49 ++++++++++++++++++
> >   libavcodec/hw_base_encode.h     | 17 +++++++
> >   libavcodec/vaapi_encode.c       | 90 +++++++++++----------------------
> >   libavcodec/vaapi_encode.h       | 10 ----
> >   libavcodec/vaapi_encode_av1.c   |  2 +-
> >   libavcodec/vaapi_encode_h264.c  |  2 +-
> >   libavcodec/vaapi_encode_h265.c  |  2 +-
> >   libavcodec/vaapi_encode_mjpeg.c |  6 ++-
> >   8 files changed, 102 insertions(+), 76 deletions(-)
> >
> > diff --git a/libavcodec/hw_base_encode.c b/libavcodec/hw_base_encode.c
> > index 16afaa37be..c4789380b6 100644
> > --- a/libavcodec/hw_base_encode.c
> > +++ b/libavcodec/hw_base_encode.c
> > @@ -592,3 +592,52 @@ end:
> >
> >       return 0;
> >   }
> > +
> > +int ff_hw_base_encode_init(AVCodecContext *avctx)
> > +{
> > +    FFHWBaseEncodeContext *ctx = avctx->priv_data;
>
> This is the issue I was talking about, this requires that
> FFHWBaseEncodeContext is always the main context.
>
> Could you change it so everything takes FFHWBaseEncodeContext as an
> argument, rather than AVCodecContext (apart from where the function
> absolutely must read some data from it)?
>

Might this suggestion involve having to do some ugly down-casting?

-- Sean McGovern

>
_______________________________________________
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".

  reply	other threads:[~2024-05-25 14:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-25 10:30 [FFmpeg-devel] [PATCH v11 01/14] avcodec/vaapi_encode: introduce a base layer for vaapi encode tong1.wu-at-intel.com
2024-05-25 10:30 ` [FFmpeg-devel] [PATCH v11 02/14] avcodec/hw_base_encode: add FF_HW_ prefix for two enums tong1.wu-at-intel.com
2024-05-25 10:30 ` [FFmpeg-devel] [PATCH v11 03/14] avcodec/vaapi_encode: add async_depth to common options tong1.wu-at-intel.com
2024-05-25 10:30 ` [FFmpeg-devel] [PATCH v11 04/14] avcodec/vaapi_encode: add picture type name to base tong1.wu-at-intel.com
2024-05-25 10:30 ` [FFmpeg-devel] [PATCH v11 05/14] avcodec/vaapi_encode: move pic->input_surface initialization to encode_alloc tong1.wu-at-intel.com
2024-05-25 10:30 ` [FFmpeg-devel] [PATCH v11 06/14] avcodec/vaapi_encode: move the dpb logic from VAAPI to base layer tong1.wu-at-intel.com
2024-05-25 10:30 ` [FFmpeg-devel] [PATCH v11 07/14] avcodec/vaapi_encode: extract the init and close function " tong1.wu-at-intel.com
2024-05-25 13:07   ` Lynne via ffmpeg-devel
2024-05-25 14:18     ` Sean McGovern [this message]
2024-05-25 14:25       ` Lynne via ffmpeg-devel
2024-05-27  0:35     ` Wu, Tong1
2024-05-27  1:04       ` Lynne via ffmpeg-devel
2024-05-28 15:53         ` Wu, Tong1
2024-05-25 10:30 ` [FFmpeg-devel] [PATCH v11 08/14] avcodec/vaapi_encode: extract gop configuration and two options " tong1.wu-at-intel.com
2024-05-25 10:30 ` [FFmpeg-devel] [PATCH v11 09/14] avcodec/vaapi_encode: extract set_output_property " tong1.wu-at-intel.com
2024-05-25 10:30 ` [FFmpeg-devel] [PATCH v11 10/14] avcodec/vaapi_encode: extract a get_recon_format function " tong1.wu-at-intel.com
2024-05-25 10:30 ` [FFmpeg-devel] [PATCH v11 11/14] avcodec/vaapi_encode: extract a free funtion " tong1.wu-at-intel.com
2024-05-25 10:30 ` [FFmpeg-devel] [PATCH v11 12/14] avutil/hwcontext_d3d12va: add Flags for resource creation tong1.wu-at-intel.com
2024-05-25 10:30 ` [FFmpeg-devel] [PATCH v11 13/14] avcodec: add D3D12VA hardware HEVC encoder tong1.wu-at-intel.com
2024-05-25 10:30 ` [FFmpeg-devel] [PATCH v11 14/14] Changelog: add D3D12VA HEVC encoder changelog tong1.wu-at-intel.com

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='CAPBf_O=b7=mMCczMQHbNwQheS4SaBZWKpOXmim=M120vWOk9Ng@mail.gmail.com' \
    --to=gseanmcg@gmail.com \
    --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