Quoting Lynne (2020-02-02 18:23:43)
> Jan 22, 2020, 16:44 by an...@khirnov.net:
>
> > Quoting Lynne (2020-01-21 21:52:52)
> >
> >> Jan 21, 2020, 18:22 by an...@khirnov.net:
> >> >> Its size too? Didn't know that.
> >> >> I do think its a good idea to be able to append fields to it, so I've
> >>
Jan 22, 2020, 16:44 by an...@khirnov.net:
> Quoting Lynne (2020-01-21 21:52:52)
>
>> Jan 21, 2020, 18:22 by an...@khirnov.net:
>> >> Its size too? Didn't know that.
>> >> I do think its a good idea to be able to append fields to it, so I've
>> >> added a av_vk_frame_alloc() function. I've
Jan 21, 2020, 23:03 by s...@jkqxz.net:
> On 10/01/2020 21:05, Lynne wrote:
>
>> From 04c1836f89d89dcdc892cef66ee82afbcfda9f2d Mon Sep 17 00:00:00 2001
>> From: Lynne
>> Date: Sun, 27 Oct 2019 14:44:00 +
>> Subject: [PATCH 4/9] lavfi: add Vulkan filtering framework
>>
>> This commit adds a
On 1/22/20, Anton Khirnov wrote:
> Quoting Lynne (2020-01-21 21:52:52)
>> Jan 21, 2020, 18:22 by an...@khirnov.net:
>> >> Its size too? Didn't know that.
>> >> I do think its a good idea to be able to append fields to it, so I've
>> >> added a av_vk_frame_alloc() function. I've followed what
>>
Quoting Lynne (2020-01-21 21:52:52)
> Jan 21, 2020, 18:22 by an...@khirnov.net:
> >> Its size too? Didn't know that.
> >> I do think its a good idea to be able to append fields to it, so I've
> >> added a av_vk_frame_alloc() function. I've followed what
> >> av_frame_alloc is called, though I'm
On 10/01/2020 21:05, Lynne wrote:
> From 1e3a50fbe4399f76c0ab0f62bf6d6c65b8565db4 Mon Sep 17 00:00:00 2001
> From: Lynne
> Date: Sun, 27 Oct 2019 14:47:18 +
> Subject: [PATCH 7/9] lavfi: add an avgblur_vulkan filter
>
> This commit adds a fast avgblur Vulkan filter.
> This will reset Intel
On 19/01/2020 13:11, Lynne wrote:
> Jan 18, 2020, 20:23 by s...@jkqxz.net:
>
>> On 10/01/2020 21:05, Lynne wrote:
>>
>> The CUDA parts look like they could be split off into a separate commit?
>> (It's already huge.)
>>
>
> I don't really want broken commits or commits with dead code.
On 19/01/2020 16:41, Philip Langdale wrote:
> On Sat, 18 Jan 2020 20:27:12 +
> Mark Thompson wrote:
>
>> On 10/01/2020 21:05, Lynne wrote:
>>> This is modelled as a transfer, as we have today, but where both
>>> the src and the dst are hardware frames with hw contexts. We need
>>> to be
On 10/01/2020 21:05, Lynne wrote:
> From 04c1836f89d89dcdc892cef66ee82afbcfda9f2d Mon Sep 17 00:00:00 2001
> From: Lynne
> Date: Sun, 27 Oct 2019 14:44:00 +
> Subject: [PATCH 4/9] lavfi: add Vulkan filtering framework
>
> This commit adds a Vulkan filtering infrastructure for libavfilter.
>
On 19/01/2020 16:51, Philip Langdale wrote:
> On Sat, 18 Jan 2020 20:23:00 +
> Mark Thompson wrote:
>
>>> typedef struct AVHWDeviceInternal AVHWDeviceInternal;
>>> diff --git a/libavutil/hwcontext_cuda.c b/libavutil/hwcontext_cuda.c
>>> index 30611b1912..18abb87bbd 100644
>>> ---
Jan 21, 2020, 18:22 by an...@khirnov.net:
> Quoting Lynne (2020-01-21 18:51:22)
>
>> Jan 21, 2020, 12:08 by an...@khirnov.net:
>>
>> > Quoting Lynne (2020-01-10 22:05:21)
>> >
>> >> /**
>> >> * Activated physical device
>> >> */
>> >> VkDevice act_dev;
>> >>
>> >
>> > Where is this
Quoting Lynne (2020-01-21 18:51:22)
> Jan 21, 2020, 12:08 by an...@khirnov.net:
>
> > Quoting Lynne (2020-01-10 22:05:21)
> >
> >> /**
> >> * Activated physical device
> >> */
> >> VkDevice act_dev;
> >>
> >
> > Where is this 'activated' terminology from? From what I can see, the
> > spec
Jan 21, 2020, 12:08 by an...@khirnov.net:
> Quoting Lynne (2020-01-10 22:05:21)
>
>> /**
>> * Activated physical device
>> */
>> VkDevice act_dev;
>>
>
> Where is this 'activated' terminology from? From what I can see, the
> spec calls this a 'logical' device. Would be nice to be consistent
Quoting Lynne (2020-01-10 22:05:21)
> commit d5f1bbc61fab452803443511b1241931169359b7
> Author: Lynne
> Date: Wed Aug 28 21:58:10 2019 +0100
>
> lavu: add Vulkan hwcontext code
>
> This commit adds the necessary code to initialize and use a Vulkan device
> within the hwcontext
On Sat, 18 Jan 2020 20:23:00 +
Mark Thompson wrote:
> > typedef struct AVHWDeviceInternal AVHWDeviceInternal;
> > diff --git a/libavutil/hwcontext_cuda.c b/libavutil/hwcontext_cuda.c
> > index 30611b1912..18abb87bbd 100644
> > --- a/libavutil/hwcontext_cuda.c
> > +++
On Sat, 18 Jan 2020 20:27:12 +
Mark Thompson wrote:
> On 10/01/2020 21:05, Lynne wrote:
> > This is modelled as a transfer, as we have today, but where both
> > the src and the dst are hardware frames with hw contexts. We need
> > to be careful to ensure the contexts are compatible -
Jan 18, 2020, 20:23 by s...@jkqxz.net:
> On 10/01/2020 21:05, Lynne wrote:
>
> The CUDA parts look like they could be split off into a separate commit?
> (It's already huge.)
>
I don't really want broken commits or commits with dead code.
>>
>> diff --git a/configure b/configure
>> index
On 10/01/2020 21:05, Lynne wrote:
> From d5f1bbc61fab452803443511b1241931169359b7 Mon Sep 17 00:00:00 2001
> From: Lynne
> Date: Wed, 28 Aug 2019 21:58:10 +0100
> Subject: [PATCH 2/9] lavu: add Vulkan hwcontext code
>
> This commit adds the necessary code to initialize and use a Vulkan device
>
On 10/01/2020 21:05, Lynne wrote:
> From e2d18e03e3a5fa8ef82159c68212b720198a9b91 Mon Sep 17 00:00:00 2001
> From: Philip Langdale
> Date: Wed, 23 Oct 2019 18:11:37 -0700
> Subject: [PATCH 3/9] lavfi/vf_hwupload: Add support for HW -> HW transfers
>
> As we find ourselves wanting a way to
On 10/01/2020 21:05, Lynne wrote:
> From 2fefb0b7ff760f2fb019751da8c37cfd0578ef00 Mon Sep 17 00:00:00 2001
> From: Philip Langdale
> Date: Wed, 23 Oct 2019 18:01:52 -0700
> Subject: [PATCH 1/9] lavu/hwcontext: Add support for HW -> HW transfers
>
> We are beginning to consider scenarios where a
On Fri, 10 Jan 2020 22:05:21 +0100 (CET)
Lynne wrote:
> Patches attached
> Also pushed to https://github.com/cyanreg/FFmpeg/ master branch
> because they're 9 and they add about 7000 lines. Filtering won't work
> without a recent glslang version since they moved a header and broke
> API because
21 matches
Mail list logo
