On 28/06/17 15:06, wm4 wrote:
> On Wed, 28 Jun 2017 13:51:26 +0100
> Mark Thompson <s...@jkqxz.net> wrote:
>
>> On 28/06/17 12:13, wm4 wrote:
>>> On Tue, 27 Jun 2017 22:50:54 +0100
>>> Mark Thompson <s...@jkqxz.net> wrote:
>>>
>>>> ---
>>>> libavutil/hwcontext_d3d11va.c | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/libavutil/hwcontext_d3d11va.c b/libavutil/hwcontext_d3d11va.c
>>>> index 75f78d866..543f90d6c 100644
>>>> --- a/libavutil/hwcontext_d3d11va.c
>>>> +++ b/libavutil/hwcontext_d3d11va.c
>>>> @@ -227,7 +227,7 @@ static int d3d11va_frames_init(AVHWFramesContext *ctx)
>>>> .ArraySize = ctx->initial_pool_size,
>>>> .Usage = D3D11_USAGE_DEFAULT,
>>>> .BindFlags = hwctx->BindFlags,
>>>> - .MiscFlags = hwctx->MiscFlags,
>>>> + .MiscFlags = hwctx->MiscFlags | D3D11_RESOURCE_MISC_SHARED,
>>>> };
>>>>
>>>> if (hwctx->texture) {
>>>
>>> So what does test-only mean?
>>
>> "I'm not going to apply this hack, but it's useful for testing other stuff
>> in the series"
>
> Doesn't this imply it's somehow needed to use that other stuff?
If you use avconv, then yes with the current code. That doesn't mean we should
be making a library change like this now - some future magic negotiation stuff
might be able to tell you that this flag needs to be set, and if you make your
own D3D11 textures then you can supply whatever flags you like.
_______________________________________________
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel
