On Sun, Mar 26, 2017 at 12:35:54PM +0200, Marton Balint wrote:
[...]
> > - there is a FATE "test" with the expressive purpose of catching
> > instances where the copyright header says "Libav" instead of
> > "FFmpeg" after new files are added from Libav merges. One has to
> > wonder why this is d
On Sun, 26 Mar 2017, wm4 wrote:
On Sat, 25 Mar 2017 21:33:50 -0300
James Almer wrote:
On 3/25/2017 9:23 PM, Michael Niedermayer wrote:
> On Sat, Mar 18, 2017 at 09:56:04AM +0100, wm4 wrote:
>> From: Anton Khirnov
>>
>> Certain hardware decoding APIs are not guaranteed to be thread-safe, s
On Sat, 25 Mar 2017 21:33:50 -0300
James Almer wrote:
> On 3/25/2017 9:23 PM, Michael Niedermayer wrote:
> > On Sat, Mar 18, 2017 at 09:56:04AM +0100, wm4 wrote:
> >> From: Anton Khirnov
> >>
> >> Certain hardware decoding APIs are not guaranteed to be thread-safe, so
> >> having the user acce
On 3/25/2017 9:23 PM, Michael Niedermayer wrote:
> On Sat, Mar 18, 2017 at 09:56:04AM +0100, wm4 wrote:
>> From: Anton Khirnov
>>
>> Certain hardware decoding APIs are not guaranteed to be thread-safe, so
>> having the user access decoded hardware surfaces while the decoder is
>> running in anothe
On Sat, Mar 18, 2017 at 09:56:04AM +0100, wm4 wrote:
> From: Anton Khirnov
>
> Certain hardware decoding APIs are not guaranteed to be thread-safe, so
> having the user access decoded hardware surfaces while the decoder is
> running in another thread can cause failures (this is mainly known to
>
On Mon, Mar 20, 2017 at 06:43:50AM +0100, wm4 wrote:
> On Sun, 19 Mar 2017 02:30:11 +0100
> Michael Niedermayer wrote:
>
> > On Sat, Mar 18, 2017 at 09:56:04AM +0100, wm4 wrote:
> > > From: Anton Khirnov
> > >
> > > Certain hardware decoding APIs are not guaranteed to be thread-safe, so
> > > h
On Sun, 19 Mar 2017 02:30:11 +0100
Michael Niedermayer wrote:
> On Sat, Mar 18, 2017 at 09:56:04AM +0100, wm4 wrote:
> > From: Anton Khirnov
> >
> > Certain hardware decoding APIs are not guaranteed to be thread-safe, so
> > having the user access decoded hardware surfaces while the decoder is
On Sat, Mar 18, 2017 at 09:56:04AM +0100, wm4 wrote:
> From: Anton Khirnov
>
> Certain hardware decoding APIs are not guaranteed to be thread-safe, so
> having the user access decoded hardware surfaces while the decoder is
> running in another thread can cause failures (this is mainly known to
>
From: Anton Khirnov
Certain hardware decoding APIs are not guaranteed to be thread-safe, so
having the user access decoded hardware surfaces while the decoder is
running in another thread can cause failures (this is mainly known to
happen with DXVA2).
For such hwaccels, only allow the decoding t
