Re: [FFmpeg-devel] [PATCH 2/2] avutil/hwcontext_d3d12va: added resource Flags support to command line

From: Dmitrii Ovchinnikov <ovchinnikov.dmitrii-at-gmail.com@ffmpeg.org>
To: Wu Jianhua <toqsxw@outlook.com>
Cc: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] avutil/hwcontext_d3d12va: added resource Flags support to command line
Date: Thu, 12 Jun 2025 01:28:13 +0200
Message-ID: <CADXbNkSyeK0EjiPnVSMHV+GGTFKnW3SWpgYNg1V99KLLXt12fA@mail.gmail.com> (raw)
In-Reply-To: <OS7P286MB5498625B7DDF4C1C82BCDEE8CA61A@OS7P286MB5498.JPNP286.PROD.OUTLOOK.COM>

>> We should set these flags in d3d12va_frames_init
>> instead of referencing device->flags directly
Sorry, I didn't fully understand this part.

Is it actually possible to pass the required flags to
the frames context without using the device context?

Or perhaps you meant something like this:
1) Add a D3D12_HEAP_FLAGS heap_flags field to AVD3D12VAFramesContext
2) Set both heap_flags and flags inside d3d12va_frames_init,
   after validating the format,
while still passing the property through the device context?

>> it seemed that the options uav_resource=1,render_target_resource=1,
>> shared_resource=1 are too long.

Maybe we could shorten the word resource to res?
Something like this: uav_res shared_res render_targ_res(rt_res)

Sincerely, Ovchinnikov D.A.
_______________________________________________
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".