Hi,
Am Do., 11. Apr. 2019 um 00:50 Uhr schrieb Hendrik Leppkes
:
>
> On Thu, Apr 11, 2019 at 12:39 AM Lukas Rusak wrote:
> >
> > This will allow applications to properly init the decoder in
> > cases where a hardware decoder is tried first and and software
> > decoder is tried after by calling th
Hi Mark,
Am Mi., 13. März 2019 um 02:00 Uhr schrieb Mark Thompson :
[..]
> >>> Date: Sat, 26 Jan 2019 19:48:35 +0100
> >>> Subject: [PATCH] avcodec/vaapi_h264: skip decode if pic has no slices
> >>
> >> Something along the lines of "avcodec/vaapi_h264: skip decoding if no
> >> slices were provided"
Thank you very much for your reply.
Am Sa., 9. März 2019 um 21:09 Uhr schrieb Jan Ekström :
> > From 386c94489a86bb747b6531f727843cf259a24f5d Mon Sep 17 00:00:00 2001
> > From: xbmc
> Is this author field meant to not have an actual name in it? Just verifying.
It can stay as is. The original aut
Resent - layer 8 issue with using a mail client, sorry for the noise:
From 386c94489a86bb747b6531f727843cf259a24f5d Mon Sep 17 00:00:00 2001
From: xbmc
Date: Sat, 26 Jan 2019 19:48:35 +0100
Subject: [PATCH] avcodec/vaapi_h264: skip decode if pic has no slices
---
libavcodec/vaapi_h264.c | 5 +++
Yes, that makes sense. Thank you very much.
Attached you find the updated version.
Am Sa., 9. März 2019 um 16:32 Uhr schrieb Thomas Xu :
>
> should we return AVERROR_INVALIDDATA instead of -1?
> thanks
>
> On Sat, Mar 9, 2019 at 8:25 PM Peter F wr
From 816e9156235a5d7d895b09c0235c9f8f1f7703e7 Mon Sep 17 00:00:00 2001
From: xbmc
Date: Sat, 26 Jan 2019 19:48:35 +0100
Subject: [PATCH] avcodec/vaapi_h264: skip decode if pic has no slices
---
libavcodec/vaapi_h264.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/libavcodec/vaapi_h264
lices == 0) {
+ret = -1;
+goto finish;
+}
+
ret = ff_vaapi_decode_issue(avctx, pic);
if (ret < 0)
goto finish;
--
2.19.1
Am Sa., 9. März 2019 um 12:46 Uhr schrieb Peter F :
>
> Fixes / workarounds: https://bugs.freedesktop.org/show_bug.cgi?id=105368
> [
Fixes / workarounds: https://bugs.freedesktop.org/show_bug.cgi?id=105368
[1]in ffmpeg
This bug hits several AMD VAAPI users, especially those using h264 channels
via DVB-X: https://github.com/xbmc/xbmc/issues/15704
Typical backtrace in ffmpeg code, which fits the description in [1]:
#0 __memset_
