Re: [FFmpeg-devel] avcodec/vaapi_h264: skip decode if pic has no slices

2019-03-14 Thread Peter F
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"

Re: [FFmpeg-devel] avcodec/vaapi_h264: skip decode if pic has no slices

2019-03-12 Thread Mark Thompson
On 09/03/2019 20:30, Peter F wrote: > 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 veri

Re: [FFmpeg-devel] avcodec/vaapi_h264: skip decode if pic has no slices

2019-03-09 Thread Peter F
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

Re: [FFmpeg-devel] avcodec/vaapi_h264: skip decode if pic has no slices

2019-03-09 Thread Jan Ekström
On Sat, Mar 9, 2019 at 5:49 PM Peter F wrote: > > Resent - layer 8 issue with using a mail client, sorry for the noise: > > 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. > Date: Sa

Re: [FFmpeg-devel] avcodec/vaapi_h264: skip decode if pic has no slices

2019-03-09 Thread Carl Eugen Hoyos
2019-03-09 16:49 GMT+01:00, Peter F : > Resent - layer 8 issue with using a mail client Attachments are fine... Carl Eugen ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] avcodec/vaapi_h264: skip decode if pic has no slices

2019-03-09 Thread Peter F
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 +++

Re: [FFmpeg-devel] avcodec/vaapi_h264: skip decode if pic has no slices

2019-03-09 Thread Peter F
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 wrote: > > > From 816e9156235a5d7d895b09c0235c9f8f1f

Re: [FFmpeg-devel] avcodec/vaapi_h264: skip decode if pic has no slices

2019-03-09 Thread Thomas Xu
should we return AVERROR_INVALIDDATA instead of -1? thanks On Sat, Mar 9, 2019 at 8:25 PM Peter F wrote: > 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

Re: [FFmpeg-devel] avcodec/vaapi_h264: skip decode if pic has no slices

2019-03-09 Thread Peter F
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

Re: [FFmpeg-devel] avcodec/vaapi_h264: skip decode if pic has no slices

2019-03-09 Thread Peter F
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

[FFmpeg-devel] avcodec/vaapi_h264: skip decode if pic has no slices

2019-03-09 Thread Peter F
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_