On Mon, Oct 26, 2015 at 1:49 AM, Ronald S. Bultje wrote:
> Hi,
>
> On Sun, Oct 25, 2015 at 5:55 PM, Hendrik Leppkes
> wrote:
>
>> On Fri, Oct 23, 2015 at 1:54 PM, Hendrik Leppkes
>> wrote:
>> > HWAccels with frame threads are fundamentally flawed in avcodecs current
>> > design, and there are se
Hi,
On Sun, Oct 25, 2015 at 5:55 PM, Hendrik Leppkes
wrote:
> On Fri, Oct 23, 2015 at 1:54 PM, Hendrik Leppkes
> wrote:
> > HWAccels with frame threads are fundamentally flawed in avcodecs current
> > design, and there are several known problems ranging from image
> corruption
> > to driver cra
On Fri, Oct 23, 2015 at 1:54 PM, Hendrik Leppkes wrote:
> HWAccels with frame threads are fundamentally flawed in avcodecs current
> design, and there are several known problems ranging from image corruption
> to driver crashes.
>
> These problems come down to two design problems in the interactio
On 2015-10-23 13:54, Hendrik Leppkes wrote:
> The only reason the combination of frame threads and HWAccel was
> considered useful is to allow a seamless fallback to multi-threaded
> software decoding if the HWAccel is not available, however the issues
> outlined above far outweight this.
On Fri, 23 Oct 2015 13:54:25 +0200
Hendrik Leppkes wrote:
> HWAccels with frame threads are fundamentally flawed in avcodecs current
> design, and there are several known problems ranging from image corruption
> to driver crashes.
>
> These problems come down to two design problems in the intera
HWAccels with frame threads are fundamentally flawed in avcodecs current
design, and there are several known problems ranging from image corruption
to driver crashes.
These problems come down to two design problems in the interaction of
threads and HWAccel decoding:
(1)
While avcodec prevents par
