On Sat, Jun 20, 2015 at 01:19:29PM +0200, Sebastien Zwickert wrote:
> The pixel buffer base address is never unlocked this causes
> a bug with some pixel format types that are produced natively
> by the hardware decoder: the first buffer was always used.
> Unlock the pixel buffer base address fixes
On Mon, Jun 22, 2015 at 03:31:43PM +0200, Clément Bœsch wrote:
> On Sat, Jun 20, 2015 at 05:12:47PM +0200, Clément Bœsch wrote:
> > On Sat, Jun 20, 2015 at 04:25:55PM +0200, Michael Niedermayer wrote:
> > > On Sat, Jun 20, 2015 at 01:19:29PM +0200, Sebastien Zwickert wrote:
> > > > The pixel buffer
On Sat, Jun 20, 2015 at 05:12:47PM +0200, Clément Bœsch wrote:
> On Sat, Jun 20, 2015 at 04:25:55PM +0200, Michael Niedermayer wrote:
> > On Sat, Jun 20, 2015 at 01:19:29PM +0200, Sebastien Zwickert wrote:
> > > The pixel buffer base address is never unlocked this causes
> > > a bug with some pixel
On Sat, Jun 20, 2015 at 04:25:55PM +0200, Michael Niedermayer wrote:
> On Sat, Jun 20, 2015 at 01:19:29PM +0200, Sebastien Zwickert wrote:
> > The pixel buffer base address is never unlocked this causes
> > a bug with some pixel format types that are produced natively
> > by the hardware decoder: t
On Sat, Jun 20, 2015 at 01:19:29PM +0200, Sebastien Zwickert wrote:
> The pixel buffer base address is never unlocked this causes
> a bug with some pixel format types that are produced natively
> by the hardware decoder: the first buffer was always used.
> Unlock the pixel buffer base address fixes
The pixel buffer base address is never unlocked this causes
a bug with some pixel format types that are produced natively
by the hardware decoder: the first buffer was always used.
Unlock the pixel buffer base address fixes the issue.
---
ffmpeg_vda.c | 2 ++
1 file changed, 2 insertions(+)
diff
