From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/videotoolboxenc: add hw_configs Date: Thu, 12 Oct 2023 16:55:47 +0200 Message-ID: <DU0P250MB07472643B13E3616AAA04C998FD3A@DU0P250MB0747.EURP250.PROD.OUTLOOK.COM> (raw) In-Reply-To: <tencent_1B6D4D032063CD9FCFE05541A749388D9607@qq.com> Zhao Zhili: > >> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Andreas Rheinhardt >> Sent: 2023年10月12日 22:01 >> To: ffmpeg-devel@ffmpeg.org >> Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/videotoolboxenc: add hw_configs >> >> Zhao Zhili: >>> From: Zhao Zhili <zhilizhao@tencent.com> >>> >>> Will be used in the following patches. >> >> It doesn't seem to be used for 2/2, so it should be applied with the >> patches that actually need it. > > It's used in an nonobvious way. With hw_config we can get avctx->hw_frames_ctx, > and with avctx->hw_frames_ctx we get sw_pix_fmt. Otherwise sw_pix_fmt is none. > I need sw_pix_fmt before get the first frame. > So setting these hw_config magically sets AVCodecContext.sw_pix_fmt? How does this work? Does this work magically with callers other than the ffmpeg cli? >> >>> --- >>> libavcodec/videotoolboxenc.c | 9 +++++++++ >>> 1 file changed, 9 insertions(+) >>> >>> diff --git a/libavcodec/videotoolboxenc.c b/libavcodec/videotoolboxenc.c >>> index 1d1595329a..b685bf4cc4 100644 >>> --- a/libavcodec/videotoolboxenc.c >>> +++ b/libavcodec/videotoolboxenc.c >>> @@ -37,6 +37,7 @@ >>> #include "encode.h" >>> #include "h264.h" >>> #include "h264_sei.h" >>> +#include "hwconfig.h" >>> #include <dlfcn.h> >>> >>> #if !HAVE_KCMVIDEOCODECTYPE_HEVC >>> @@ -2830,6 +2831,11 @@ static const enum AVPixelFormat prores_pix_fmts[] = { >>> "Sets the maximum number of reference frames. This only has an effect when the value is less than the maximum allowed >> by the profile/level.", \ >>> OFFSET(max_ref_frames), AV_OPT_TYPE_INT, { .i64 = 0 }, 0, INT_MAX, VE }, >>> >>> +static const AVCodecHWConfigInternal *const vt_encode_hw_configs[] = { >>> + HW_CONFIG_ENCODER_FRAMES(VIDEOTOOLBOX, VIDEOTOOLBOX), >>> + NULL, >>> +}; >>> + >>> #define OFFSET(x) offsetof(VTEncContext, x) >>> static const AVOption h264_options[] = { >>> { "profile", "Profile", OFFSET(profile), AV_OPT_TYPE_INT, { .i64 = AV_PROFILE_UNKNOWN }, AV_PROFILE_UNKNOWN, INT_MAX, >> VE, "profile" }, >>> @@ -2886,6 +2892,7 @@ const FFCodec ff_h264_videotoolbox_encoder = { >>> .close = vtenc_close, >>> .p.priv_class = &h264_videotoolbox_class, >>> .caps_internal = FF_CODEC_CAP_INIT_CLEANUP, >>> + .hw_configs = vt_encode_hw_configs, >>> }; >>> >>> static const AVOption hevc_options[] = { >>> @@ -2923,6 +2930,7 @@ const FFCodec ff_hevc_videotoolbox_encoder = { >>> .p.priv_class = &hevc_videotoolbox_class, >>> .caps_internal = FF_CODEC_CAP_INIT_CLEANUP, >>> .p.wrapper_name = "videotoolbox", >>> + .hw_configs = vt_encode_hw_configs, >>> }; >>> >>> static const AVOption prores_options[] = { >>> @@ -2961,4 +2969,5 @@ const FFCodec ff_prores_videotoolbox_encoder = { >>> .p.priv_class = &prores_videotoolbox_class, >>> .caps_internal = FF_CODEC_CAP_INIT_CLEANUP, >>> .p.wrapper_name = "videotoolbox", >>> + .hw_configs = vt_encode_hw_configs, >>> }; >> _______________________________________________ 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-10-12 14:54 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-12 12:49 Zhao Zhili 2023-10-12 14:00 ` Andreas Rheinhardt 2023-10-12 14:32 ` Zhao Zhili 2023-10-12 14:55 ` Andreas Rheinhardt [this message] 2023-10-12 15:09 ` Zhao Zhili 2023-10-16 12:32 ` 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=DU0P250MB07472643B13E3616AAA04C998FD3A@DU0P250MB0747.EURP250.PROD.OUTLOOK.COM \ --to=andreas.rheinhardt@outlook.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