I to base layer
>
>On 07/06/2024 18:48, Lynne wrote:
>> On 07/06/2024 17:22, Wu, Tong1 wrote:
>>>> From: ffmpeg-devel On Behalf Of
>Lynne
>>>> via ffmpeg-devel
>>>> Sent: Friday, June 7, 2024 11:10 PM
>>>> To: ffmpeg-devel@ffmpeg.org
>From: ffmpeg-devel On Behalf Of Lynne
>via ffmpeg-devel
>Sent: Friday, June 7, 2024 11:10 PM
>To: ffmpeg-devel@ffmpeg.org
>Cc: Lynne
>Subject: Re: [FFmpeg-devel] [PATCH v13 06/15] avcodec/vaapi_encode: move
>the dpb logic from VAAPI to base layer
>
>On 03/06/2024 11:18, tong1.wu-at-intel@ffm
ng FFHWBaseEncodeContext from avctx
>
>On 06/06/2024 08:46, Wu, Tong1 wrote:
>>> From: ffmpeg-devel On Behalf Of
>Lynne
>>> via ffmpeg-devel
>>> Sent: Thursday, June 6, 2024 2:11 PM
>>> To: ffmpeg-devel@ffmpeg.org
>>> Cc: Lynne
>>>
>From: ffmpeg-devel On Behalf Of Lynne
>via ffmpeg-devel
>Sent: Thursday, June 6, 2024 2:11 PM
>To: ffmpeg-devel@ffmpeg.org
>Cc: Lynne
>Subject: Re: [FFmpeg-devel] [PATCH v13 15/15] avcodec/hw_base_encode:
>avoid getting FFHWBaseEncodeContext from avctx
>
>On 03/06/2024 11:19, tong1.wu-at-intel..
>From: Lynne
>Sent: Wednesday, May 29, 2024 8:02 AM
>To: Wu, Tong1 ; FFmpeg development discussions and
>patches
>Subject: Re: [FFmpeg-devel] [PATCH v12 15/15] avcodec/hw_base_encode: add
>avctx pointer for FFHWBaseEncodeContext
>
>On 29/05/2024 00:53, Wu, Tong1 wrote:
&g
>From: ffmpeg-devel On Behalf Of Lynne
>via ffmpeg-devel
>Sent: Wednesday, May 29, 2024 1:08 AM
>To: ffmpeg-devel@ffmpeg.org
>Cc: Lynne
>Subject: Re: [FFmpeg-devel] [PATCH v12 15/15] avcodec/hw_base_encode: add
>avctx pointer for FFHWBaseEncodeContext
>
>On 28/05/2024 17:48, tong1.wu-at-intel
>From: Lynne
>Sent: Monday, May 27, 2024 10:04 AM
>To: Wu, Tong1 ; FFmpeg development discussions and
>patches
>Subject: Re: [FFmpeg-devel] [PATCH v11 07/14] avcodec/vaapi_encode: extract
>the init and close function to base layer
>
>On 27/05/2024 02:35, Wu, Tong1 wrote
>From: ffmpeg-devel On Behalf Of Lynne
>via ffmpeg-devel
>Sent: Saturday, May 25, 2024 10:07 PM
>To: ffmpeg-devel@ffmpeg.org
>Cc: Lynne
>Subject: Re: [FFmpeg-devel] [PATCH v11 07/14] avcodec/vaapi_encode: extract
>the init and close function to base layer
>
>On 25/05/2024 12:30, tong1.wu-at-intel
>-Original Message-
>From: ffmpeg-devel On Behalf Of Lynne
>via ffmpeg-devel
>Sent: Friday, May 24, 2024 12:11 AM
>To: ffmpeg-devel@ffmpeg.org
>Cc: Lynne
>Subject: Re: [FFmpeg-devel] [PATCH v9 01/13] avcodec/vaapi_encode:
>introduce a base layer for vaapi encode
>
>On 20/05/2024 16:52, to
>-Original Message-
>From: ffmpeg-devel On Behalf Of
>Andrew Sayers
>Sent: Wednesday, May 22, 2024 12:32 AM
>To: FFmpeg development discussions and patches de...@ffmpeg.org>
>Subject: Re: [FFmpeg-devel] [PATCH v9 11/13] avutil/hwcontext_d3d12va: add
>Flags for resource creation
>
>(Only re
>Subject: Re: [FFmpeg-devel] [PATCH v8 12/15] avcodec/vaapi_encode: extract a
>free funtion to base layer
>
>On 18/04/2024 09:59, tong1.wu-at-intel@ffmpeg.org wrote:
>> From: Tong Wu
>>
>> Signed-off-by: Tong Wu
>> ---
>> libavcodec/hw_base_encode.c | 11 +++
>> libavcodec/hw_base_en
>-Original Message-
>From: ffmpeg-devel On Behalf Of Oleg
>Tolmatcev
>Sent: Saturday, May 18, 2024 3:39 AM
>To: ffmpeg-devel@ffmpeg.org
>Subject: [FFmpeg-devel] [PATCH] avutil/hwcontext_qsv: fix GCC 14.1 warnings
>
>This patch fixes warnings produced by GCC 14.1 in hwcontext_qsv.c. It
>fix
>-Original Message-
>From: ffmpeg-devel On Behalf Of Mark
>Thompson
>Sent: Wednesday, May 15, 2024 5:06 AM
>To: ffmpeg-devel@ffmpeg.org
>Subject: Re: [FFmpeg-devel] [PATCH v8 11/15] avcodec/vaapi_encode: extract a
>get_recon_format function to base layer
>
>On 18/04/2024 09:59, tong1.wu-at
>-Original Message-
>From: ffmpeg-devel On Behalf Of Mark
>Thompson
>Sent: Wednesday, May 15, 2024 4:56 AM
>To: ffmpeg-devel@ffmpeg.org
>Subject: Re: [FFmpeg-devel] [PATCH v8 06/15] avcodec/vaapi_encode: extract
>the init function to base layer
>
>On 18/04/2024 09:59, tong1.wu-at-intel
>-Original Message-
>From: ffmpeg-devel On Behalf Of Mark
>Thompson
>Sent: Wednesday, May 15, 2024 4:47 AM
>To: ffmpeg-devel@ffmpeg.org
>Subject: Re: [FFmpeg-devel] [PATCH v8 05/15] avcodec/vaapi_encode: move
>the dpb logic from VAAPI to base layer
>
>On 18/04/2024 09:58, tong1.wu-at-intel
>-Original Message-
>From: ffmpeg-devel On Behalf Of Mark
>Thompson
>Sent: Wednesday, May 15, 2024 3:56 AM
>To: ffmpeg-devel@ffmpeg.org
>Subject: Re: [FFmpeg-devel] [PATCH v8 01/15] avcodec/vaapi_encode:
>introduce a base layer for vaapi encode
>
>On 18/04/2024 09:58, tong1.wu-at-intel
>From: Wu, Tong1
>Sent: Thursday, April 18, 2024 4:59 PM
>To: ffmpeg-devel@ffmpeg.org
>Cc: Wu, Tong1
>Subject: [FFmpeg-devel][PATCH v8 14/15] avcodec: add D3D12VA hardware
>HEVC encoder
>
>From: Tong Wu
>
>This implementation is based on D3D12 Video Encoding Spec
Hi,
>From: ffmpeg-devel On Behalf Of Renan
>Lavarec via ffmpeg-devel
>Sent: Monday, April 8, 2024 11:27 PM
>To: ffmpeg-devel@ffmpeg.org
>Cc: Renan Lavarec
>Subject: [FFmpeg-devel] [PATCH] avutil/hwcontext_d3d12va: wait the texture is
>used before to free it.
>
>From: Renan Lavarec 124602499+rlav
>From: ffmpeg-devel On Behalf Of James
>Almer
>Sent: Friday, March 29, 2024 11:18 PM
>To: ffmpeg-devel@ffmpeg.org
>Subject: Re: [FFmpeg-devel] [PATCH v2] avcodec/hevc_ps: fix the problem of
>memcmp losing effectiveness
>
>On 3/29/2024 12:13 PM, tong1.wu-at-intel@ffmpeg.org wrote:
>> From: Tong
>From: ffmpeg-devel On Behalf Of James
>Almer
>Sent: Friday, March 29, 2024 8:46 PM
>To: ffmpeg-devel@ffmpeg.org
>Subject: Re: [FFmpeg-devel] [PATCH] avcodec/hevc_ps: fix the problem of
>memcmp losing effectiveness
>
>On 3/28/2024 10:15 AM, tong1.wu-at-intel@ffmpeg.org wrote:
>> From: Tong Wu
>From: ffmpeg-devel On Behalf Of
>Andreas Rheinhardt
>Sent: Friday, March 29, 2024 10:03 PM
>To: ffmpeg-devel@ffmpeg.org
>Subject: Re: [FFmpeg-devel] [PATCH] avcodec/hevc_ps: fix the problem of
>memcmp losing effectiveness
>
>Mark Thompson:
>> On 28/03/2024 13:15, tong1.wu-at-intel@ffmpeg.org
>From: ffmpeg-devel On Behalf Of
>Hendrik Leppkes
>Sent: Thursday, March 28, 2024 5:43 PM
>To: FFmpeg development discussions and patches de...@ffmpeg.org>
>Subject: Re: [FFmpeg-devel] [PATCH] avcodec/hevc_ps: fix the problem of
>memcmp losing effectiveness
>
>On Thu, Mar 28, 2024 at 10:12 AM
>w
Kindly ping. Is there any more comment on v7?
>-Original Message-
>From: Wu, Tong1
>Sent: Thursday, March 14, 2024 4:15 PM
>To: ffmpeg-devel@ffmpeg.org
>Cc: Wu, Tong1
>Subject: [FFmpeg-devel][PATCH v7 11/12] avcodec: add D3D12VA hardware
>HEVC encoder
>
Hi James,
>From: ffmpeg-devel On Behalf Of James
>Almer
>Sent: Thursday, March 21, 2024 8:29 PM
>To: ffmpeg-devel@ffmpeg.org
>Subject: [FFmpeg-devel] [PATCH] avcodec/hevc_ps: allocate only the required
>HEVCHdrParams within a VPS
>
>Signed-off-by: James Almer
>---
> libavcodec/hevc_ps.c | 14 +
>
>Feb 29, 2024, 06:35 by tong1.wu-at-intel@ffmpeg.org:
>
>> From: Tong Wu
>>
>> Since VAAPI and future D3D12VA implementation may share the same dpb
>> logic and some other functions. A base layer encode context is introduced
>> as vaapi context's base and extract the related funtions to a co
Kindly ping.
Hi Mark, do you have more comments on this patch set?
>Subject: [FFmpeg-devel][PATCH v6 8/9] avcodec: add D3D12VA hardware HEVC
>encoder
>
>From: Tong Wu
>
>This implementation is based on D3D12 Video Encoding Spec:
>https://microsoft.github.io/DirectX-Specs/d3d/D3D12VideoEncoding.
>Subject: Re: [FFmpeg-devel] [PATCH 2/2] avcodec/vaapi_encode_h265: use
>is_reference to fill reference_pic_flag
>
>On Di, 2024-02-27 at 11:48 +0800, tong1.wu-at-intel@ffmpeg.org wrote:
>> From: Tong Wu
>>
>> This codec supports FLAG_B_PICTURE_REFERENCES. We need to fill
>> reference_pic_flag
>-Original Message-
>From: ffmpeg-devel On Behalf Of Mark
>Thompson
>Sent: Friday, February 23, 2024 3:22 AM
>To: ffmpeg-devel@ffmpeg.org
>Subject: Re: [FFmpeg-devel] [PATCH v5 4/9] avcodec/vaapi_encode: extract rc
>parameter configuration to base layer
>
>On
>On 18/02/2024 08:45, tong1.wu-at-intel@ffmpeg.org wrote:
>> From: Tong Wu
>>
>> VAAPI and D3D12VA can share rate control configuration codes. Hence, it
>> can be moved to base layer for simplification.
>>
>> Signed-off-by: Tong Wu
>> ---
>> libavcodec/hw_base_encode.c| 151
Hi Mark. Thanks for your careful review.
>On 18/02/2024 08:45, tong1.wu-at-intel@ffmpeg.org wrote:
>> From: Tong Wu
>>
>> Since VAAPI and future D3D12VA implementation may share the same dpb
>> logic and some other functions. A base layer encode context is introduced
>> as vaapi context's bas
>> From: Tong Wu
>>
>> This implementation is based on D3D12 Video Encoding Spec:
>> https://microsoft.github.io/DirectX-Specs/d3d/D3D12VideoEncoding.html
>>
>> Sample command line for transcoding:
>> ffmpeg.exe -hwaccel d3d12va -hwaccel_output_format d3d12 -i input.mp4
>> -c:v hevc_d3d12va output
>>
>> From: Tong Wu
>>
>> This implementation is based on D3D12 Video Encoding Spec:
>> https://microsoft.github.io/DirectX-Specs/d3d/D3D12VideoEncoding.html
>>
>> Sample command line for transcoding:
>> ffmpeg.exe -hwaccel d3d12va -hwaccel_output_format d3d12 -i input.mp4
>> -c:v hevc_d3d12va out
>From: ffmpeg-devel On Behalf Of Mark
>Thompson
>Sent: Tuesday, January 23, 2024 5:52 AM
>To: ffmpeg-devel@ffmpeg.org
>Subject: Re: [FFmpeg-devel] [PATCH 7/9] avutil/hwcontext_d3d12va: add Flags
>for resource creation
>
>On 22/01/2024 05:57, tong1.wu-at-intel@ffmpeg.org wrote:
>> From: Tong Wu
>From: ffmpeg-devel On Behalf Of Wu
>Jianhua
>Sent: Wednesday, December 27, 2023 9:44 PM
>To: FFmpeg development discussions and patches de...@ffmpeg.org>
>Subject: [FFmpeg-devel] [PATCH v2] avcodec/d3d12va_decode: don't change
>the resource state if the referenced frame is the same as the current
>From: ffmpeg-devel On Behalf Of Wu
>Jianhua
>Sent: Tuesday, December 26, 2023 9:21 PM
>To: FFmpeg development discussions and patches de...@ffmpeg.org>
>Subject: [FFmpeg-devel] [PATCH] avcodec/d3d12va_decode: don't change the
>resource state if the referenced frame is the same as the current fram
>From: ffmpeg-devel On Behalf Of
>Michael Niedermayer
>Sent: Monday, December 25, 2023 7:07 AM
>To: FFmpeg development discussions and patches de...@ffmpeg.org>
>Subject: Re: [FFmpeg-devel] [PATCH v12 2/9] avcodec: add D3D12VA hardware
>accelerated H264 decoding
>
>On Tue, Dec 05, 2023 at 02:46:44
>From: ffmpeg-devel On Behalf Of
>Martin Storsjö
>Sent: Friday, December 22, 2023 4:41 PM
>To: FFmpeg development discussions and patches de...@ffmpeg.org>
>Subject: Re: [FFmpeg-devel] [PATCH 1/2] configure: Remove a redundant check
>for UWP mode
>
>On Fri, 2
>Subject: [FFmpeg-devel] [PATCH 1/2] configure: Remove a redundant check for
>UWP mode
>
>The check for UWP mode was duplicated from right above, in
>d54127c41a81cf2078a3504f78e0e4232cfe11b7.
>
>Also, instead of several lines with "enabled uwp && ...", make one
>"if enabled uwp; then" block.
>---
>-Original Message-
>From: ffmpeg-devel On Behalf Of James
>Almer
>Sent: Thursday, December 21, 2023 8:47 PM
>To: ffmpeg-devel@ffmpeg.org
>Subject: Re: [FFmpeg-devel] [PATCH 3/3] avutil/hwcontext_d3d12va: remove
>unused variables
>
>On 12/21/2023 9:42 AM, Martin Storsjö wrote:
>> On Thu, 2
>
>On Thu, 21 Dec 2023, Tong Wu wrote:
>
>> Signed-off-by: Tong Wu
>> ---
>> libavutil/hwcontext_d3d12va.c | 9 -
>> 1 file changed, 9 deletions(-)
>>
>> diff --git a/libavutil/hwcontext_d3d12va.c b/libavutil/hwcontext_d3d12va.c
>> index 1600d94cb0..4995518dbd 100644
>> --- a/libavutil/hwco
>There are still no public external API users to actually test the API,
>which is concerning. It took months for the Vulkan API to be portable
>enough to work with the major Vulkan users out there. Granted, Vulkan
>is special.
>
>Is there any public test code out there? If not, I'd prefer the API t
>From: ffmpeg-devel On Behalf Of
>Martin Storsjö
>Sent: Thursday, December 21, 2023 5:48 PM
>To: ffmpeg-devel@ffmpeg.org
>Cc: Xiang, Haihao
>Subject: Re: [FFmpeg-devel] [PATCH] d3d12va: Add a missing include for the
>declaration of ff_d3d12va_get_surface_index
>
>On Thu, 21 Dec 2023, Martin Stors
>-Original Message-
>From: ffmpeg-devel On Behalf Of
>Martin Storsjö
>Sent: Thursday, December 21, 2023 5:45 PM
>To: ffmpeg-devel@ffmpeg.org
>Cc: Xiang, Haihao
>Subject: [FFmpeg-devel] [PATCH] d3d12va: Add a missing include for the
>declaration of ff_d3d12va_get_surface_index
>
>This f
>> The implementation is based on:
>> https://learn.microsoft.com/en-us/windows/win32/medfound/direct3d-12-
>video-overview
>>
>> With the Direct3D 12 video decoding support, we can render or process
>> the decoded images by the pixel shaders or compute shaders directly
>> without the extra copy o
Patch set V10 major changes:
1. Put more explanations for event object (jb)
2. Put DXGI_FORMAT to public structure (Lynne)
3. Implemented uploading method (Lynne)
4. Supported dynamic pool for hwcontext_d3d12va. Removed useless index from
every texture. Unbind texture from frames context, giving
>Nov 8, 2023, 02:06 by tong1.wu-at-intel@ffmpeg.org:
>
>> From: Wu Jianhua <> toq...@outlook.com> >
>>
>> Signed-off-by: Wu Jianhua <> toq...@outlook.com> >
>> Signed-off-by: Tong Wu <> tong1...@intel.com> >
>>
>-Original Message-
>From: ffmpeg-devel On Behalf Of Jean-
>Baptiste Kempf
>Sent: Wednesday, November 8, 2023 7:04 PM
>To: fmpeg-devel
>Subject: Re: [FFmpeg-devel] [PATCH v9 1/9] libavutil: add hwcontext_d3d12va
>and AV_PIX_FMT_D3D12
>
>Hello,
>
>On Wed, 8 Nov 2023, at 02:05, Tong Wu w
Since 6.1 release has branched out. Resend this patch set and add this feature
to the next release version.
> configure | 5 +
> doc/APIchanges | 7 +
> libavutil/Makefile | 3 +
> libavutil/hwcontext.c
>Aug 30, 2023, 11:05 by tong1.wu-at-intel@ffmpeg.org:
>
>>
>>
>> >-Original Message-
>> >From: ffmpeg-devel On Behalf Of
>Lynne
>> >Sent: Wednesday, August 30, 2023 4:39 PM
>> >To: FFmpeg development discussions and patches > >de...@ffmpeg.org>
>> >Subject: Re: [FFmpeg-devel] [PATCH v7
>-Original Message-
>From: ffmpeg-devel On Behalf Of Lynne
>Sent: Wednesday, August 30, 2023 4:39 PM
>To: FFmpeg development discussions and patches de...@ffmpeg.org>
>Subject: Re: [FFmpeg-devel] [PATCH v7 1/9] libavutil: add hwcontext_d3d12va
>and AV_PIX_FMT_D3D12
>
>Aug 30, 2023, 04:27
>Aug 29, 2023, 06:15 by tong1.wu-at-intel@ffmpeg.org:
>
>> +
>> +/**
>> + * Specifed by sync=1 when init d3d12va
>> + *
>> + * Execute commands as sync mode
>> + */
>> +int sync;
>>
>
>This is not needed, particularly in the public API.
>
>> + if (download) {
>> +
V7 removed av_d3d12_va_wait_idle from public API
Thanks,
Tong
>-Original Message-
>From: Wu, Tong1
>Sent: Tuesday, August 29, 2023 12:10 PM
>To: ffmpeg-devel@ffmpeg.org
>Cc: Wu Jianhua ; Wu, Tong1
>Subject: [PATCH v7 1/9] libavutil: add hwcontext_d3d12va and
>AV_
>-Original Message-
>From: ffmpeg-devel On Behalf Of Lynne
>Sent: Saturday, August 26, 2023 3:17 AM
>To: FFmpeg development discussions and patches de...@ffmpeg.org>
>Subject: Re: [FFmpeg-devel] [PATCH v6 1/9] libavutil: add hwcontext_d3d12va
>and AV_PIX_FMT_D3D12
>
>Aug 25, 2023, 10:49
V6 major changes
1. the way d3dlibs created, adding a load function. Added dlclose in free
function.
2. Simplified the public sync API by only keeping av_d3d12va_wait_idle.
3. Wrapping data->[0], data[1], data[2] into one single structure.
>Subject: [PATCH v6 1/9] libavutil: add hwcontext_d3d12v
>Aug 4, 2023, 15:50 by tong1.wu-at-intel@ffmpeg.org:
>
>> From: Wu Jianhua
>>
>> Signed-off-by: Wu Jianhua
>> Signed-off-by: Tong Wu
>> ---
>> configure | 5 +
>> doc/APIchanges | 7 +
>> libavutil/Makefile | 3 +
>On Vr, 2023-06-02 at 16:06 +0800, Tong Wu wrote:
>> From: Wu Jianhua
>>
>> The implementation is based on:
>> https://learn.microsoft.com/en-us/windows/win32/medfound/direct3d-12-
>video-overview
>>
>> With the Direct3D 12 video decoding support, we can render or process
>> the decoded images by
>On 25 Apr 2023, at 9:26, Tong Wu wrote:
>
>> When two formats lists cannot be merged, a scale filter is
>> auto-inserted. However, when it comes to hardware map, we have to
>> manually add a hwmap filter to do the conversion. This patch introduces
>> an auto hwmap filter to do the hwmap conversion
Kindly ping
>>Possibility for infinite loops?
>
>>In what cases this helps, have graphs examples to test?
>
>Now we only have scale filter that can be auto inserted. This patch set
>basically gives the potential capability to add more auto filters. An auto
>hwmap filter is introduced for now. It
>
>On Wed, May 31, 2023 at 11:07:15AM +0800, Tong Wu wrote:
>> From: Wu Jianhua
>>
>> The implementation is based on:
>> https://learn.microsoft.com/en-us/windows/win32/medfound/direct3d-12-
>video-overview
>>
>> With the Direct3D 12 video decoding support, we can render or process
>> the decoded
>On Wednesday, May 31, 2023, Tong Wu
>wrote:
>
>> From: Wu Jianhua
>>
>> The implementation is based on:
>> https://learn.microsoft.com/en-us/windows/win32/medfound/
>> direct3d-12-video-overview
>>
>>
>
>> With the Direct3D 12 video decoding support, we can render or process
>> the decoded image
>Possibility for infinite loops?
>In what cases this helps, have graphs examples to test?
Now we only have scale filter that can be auto inserted. This patch set
basically gives the potential capability to add more auto filters. An auto
hwmap filter is introduced for now. It can be beneficia
> [PATCH v2] avcodec: add D3D12VA hardware accelerated H264, HEVC, VP9,
> and AV1 decoding
>
> Patches attached.
>-HWACCEL_D3D11VA2(h264),
>+ HWACCEL_D3D11VA(h264),
This shouldn't be changed. It will block d3d11va h264dec.
>+#endif
>+#if CONFIG_
> On 2/13/2023 11:45 PM, Tong Wu wrote:
> > Add support for VUYX, YUYV422, Y210, XV30, P012, Y212, XV36.
> >
> > The added formats work with qsv acceleration and will not have impact
> > on d3d11va acceleration(-hwaccel d3d11va) since so far these formats
> > are still not supported by using d3d11v
Ping for the patchset. Is there any comment on adding this auto hwmap filter?
Thanks,
Tong
> -Original Message-
> From: Wu, Tong1
> Sent: Monday, July 4, 2022 4:10 PM
> To: ffmpeg-devel@ffmpeg.org
> Cc: Wu, Tong1
> Subject: [PATCH v4 5/5] lavfi/format: add a hwm
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Nicolas George
> Sent: Sunday, July 3, 2022 9:28 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Cc: Wu, Tong1
> Subject: Re: [FFmpeg-devel] [PATCH v3 3/3] avfilter/avfiltergr
> Quoting Wu, Tong1 (2022-07-01 08:51:28)
> > Plus, do you think adding a AV_PIX_FMT_FLAG_HWACCEL check for the
> > input pixel format and change the function name to
> > av_hwdevice_get_type_by_hwaccel_pix_fmt will help?
>
> I'd prefer not to, that name is way too
> > > On Jun 30, 2022, at 7:56 PM, Andreas Rheinhardt
> > wrote:
> > >
> > > "zhilizhao(赵志立)":
> > >>
> > >>
> > >>> On Jun 30, 2022, at 4:43 PM, Anton Khirnov
> wrote:
> > >>>
> > >>> Quoting Tong Wu (2022-06-30 04:45:56)
> > Add a function to get the corresponding AVHWDeviceType from a
>
> > On Jun 30, 2022, at 7:56 PM, Andreas Rheinhardt
> wrote:
> >
> > "zhilizhao(赵志立)":
> >>
> >>
> >>> On Jun 30, 2022, at 4:43 PM, Anton Khirnov wrote:
> >>>
> >>> Quoting Tong Wu (2022-06-30 04:45:56)
> Add a function to get the corresponding AVHWDeviceType from a given
> hardware pix
On Thu, Jun 30, 2022 at 4:47 AM Tong Wu
mailto:tong1.wu-at-intel@ffmpeg.org>>
wrote:
When a derive_device_type is not specified, the hwmap filter should be
able to retrieve AVHWDeviceType from outlink->format and create
corresponding hwdevice context.
Signed-off-by: Tong Wu mailto:tong1...
> > On Jun 29, 2022, at 2:32 PM, Tong Wu
> wrote:
> >
> > When a derive_device_type is not specified, the hwmap filter should be
> > able to retrieve AVHWDeviceType from outlink->format and create
> > corresponding hwdevice context.
> >
> > Signed-off-by: Tong Wu
> > ---
> > libavfilter/vf_hwmap.
> Quoting Wu, Tong1 (2022-06-08 06:47:27)
> > >
> > > Quoting Tong Wu (2022-06-07 11:22:16)
> > > > QSV encoder is able to encode frames with VAAPI or D3D11 pixel
> > > > format directly. This patch adds support for qsv encoder to accept
> >
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of
> > Xiang, Haihao
> > Sent: Thursday, June 9, 2022 8:48 AM
> > To: ffmpeg-devel@ffmpeg.org
> > Cc: Wu, Tong1 ; Chen, Wenbin
> >
> > Subject: Re: [FFmpeg-devel] [PATCH] avcodec/qsv
>
> Quoting Tong Wu (2022-06-07 11:22:16)
> > QSV encoder is able to encode frames with VAAPI or D3D11 pixel format
> > directly. This patch adds support for qsv encoder to accept VAAPI and
> > D3D11 pixel formats as input.
>
> This looks like an ad-hoc hack to me. Encoders should not do these ki
> On Sat, 2022-05-07 at 02:42 +, Soft Works wrote:
> > > -Original Message-
> > > From: ffmpeg-devel On Behalf Of
> > > Xiang, Haihao
> > > Sent: Saturday, May 7, 2022 4:36 AM
> > > To: ffmpeg-devel@ffmpeg.org
> > > Cc: W
> -Original Message-
> From: Soft Works
> Sent: Thursday, May 5, 2022 7:53 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Cc: Wu, Tong1
> Subject: RE: [FFmpeg-devel] [PATCH v3 1/4] avutil/hwcontext_qsv: derive
> QSV
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of
> > Hendrik Leppkes
> > Sent: Sunday, May 1, 2022 5:54 PM
> > To: FFmpeg development discussions and patches > de...@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] [PATCH v2 1/5] avutil/hwcontext_d3d11va:
> > fix the uninitialized te
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of
> Tong
> > Wu
> > Sent: Friday, April 29, 2022 12:45 PM
> > To: ffmpeg-devel@ffmpeg.org
> > Cc: Tong Wu
> > Subject: [FFmpeg-devel] [PATCH v2 3/5] avutil/hwcontext_d3d11va: add a
> > format check for staging texture
> >
> > The
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Hendrik Leppkes
> Sent: Wednesday, April 20, 2022 2:35 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] avutil/hwcontext_d3d11va: enable
> D3D11_RESOURCE_MISC_SHARED for
78 matches
Mail list logo