Solved AMD VAAPI regression for Leia 18.5
#1
I use Kodi since many years on both Windows and Linux.
On Windows all is ok with dxva2
Last week,on Linux Mint i've upgraded from Kodi 17.6 to 18.5.
I had cleaned all 17.6 instances, and install 18.5 properly from ppa, installation was perfect.
I appreciate new funtionality as drm support etc.
But I have a big regression for vaapi , it was working perfect for 17.6
The defaut vaapi-bob gives picture compressed on half top screen, vaapi adaptive works but crappy image when movings and normal bob crashes kodi!
My hardware is AMD radeon HD 8570 and mesa is up to date , taken from ppa:oibaf/graphics-drivers
I have no problems with VLC on same Linux partition
What can i give you to made progresses on that issue ?
Reply
#2
Nothing - we did not change anything in VAAPI and 18.x since more than nearly 1 year. Seems you hit yet another AMD driver regression.

Start with your backtrace and file a bug with upstream mesa.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#3
Looks like your issue: https://gitlab.freedesktop.org/mesa/mesa/issues/2454
While at it, check out this issue as well: https://gitlab.freedesktop.org/mesa/mesa/issues/1304 - good for some background knowledge
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#4
Hum...
I have no AMD regression, because no change made on mesa side between 17.6 and 18.5 testing (2 hours max interval)
And my Mint updates on the machine are not set  as automatic.
I have tested on Vlc, it used same drivers and i think same deinterlace method, perhaps you can confirm...

avcodec info: Using G3DVL VDPAU Driver Shared Library version 1.0 for hardware decoding
main debug: resized to 1058x598
main debug: VoutDisplayEvent 'resize' 1058x598
vdpau_display debug: picture date corrupt: delay of 1056780 us
main debug: Detected interlaced video
main debug: deinterlace -1, mode bob, is_needed 1
main debug: Adding 'deinterlace' as static
main debug: looking for video filter module matching "deinterlace,chain": 50 candidates
main debug: using video filter module "vdpau_deinterlace"
main debug: Filter 'deinterlace' (0x7f1a8c354280) appended to chain

Before sending a bug to mesa, i need to understand why it is working for Vlc and not for Kodi.

I would not have ping - pong problems between mesa and kodi teams  Smile

I know the AMD is difficult support on linux machines, it's the fault firstly of the manufacturer but i think AMD is third base installed machines after Intel and Nvidia
Reply
#5
Okay - then let's wait ...

without a Debug Log and without your crashlog chances are 0 that you get help.

Between kodi 17 and kodi 18 vaapi's 2.0 export surface was integrated into kodi and the old vaapi meethod deprecated. Why: before that hevc 10 bit for example did not work on AMD at all. Now that new standard path was broken in mesa.

Two possibilities for you:

a) Downgrade to 17.6
b) Wait until the bug I linked is fixed
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#6
No problem to provide you a kodi.log.
What would be the best for you :
- normal log or debug log ?
- start directly to crash by editing guisettings.xml and force , as example 6 (bob) for interlacemethod before launch kodi ?
- start with  my default vaapi adaptive method (23), and switch deinterlace to obtain crash via gui when playing ?
Reply
#7
@yol  Could you take a look, please. I could reproduce. It seems the picture size is halfed when doing bobbing, which it should not be. (VAAPI-MADI is fine)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#8
At the moment I cannot say much more than that it worked for me when I implemented it. I can take a look at it when I'm back at my desktop machine with an AMD GPU next week-ish. @enigma7 can you make an issue report at GitHub in the meantime? Two debug logs showing a) normal playback with bob and wrong image and b) the crash (in any variation). Also, please test another player with VAAPI (the VLC log you showed uses VDPAU).
Reply
#9
@yol
Thanks for answer:
I've forced vlc video output to opengl (it was at vdpau) and now i have VAAPI output ... and same problem (image compressed half top screen, and every second complete screen for approx 0.1 seconds).
Here is the partial  log :

avcodec info: Using Mesa Gallium driver 20.0.0-devel for AMD OLAND (DRM 2.50.0, 4.15.0-72-generic, LLVM 9.0.1) for hardware decoding
main debug: Detected interlaced video
main debug: deinterlace -1, mode bob, is_needed 1
main debug: Adding 'deinterlace' as static
main debug: looking for video filter module matching "deinterlace,chain": 50 candidates
vaapi_filters debug: using bob deinterlace method
main debug: using video filter module "vaapi_filters"
main debug: Filter 'deinterlace' (0x7f11d89e7ad0) appended to chain
vaapi_filters error: vaRenderPicture: invalid VASurfaceID
vaapi_filters error: vaRenderPicture: invalid VASurfaceID

so before opening a tiket on github, i have 2 more questions:
1- why diden't i have problem with Kodi 17.6 and same settings , same mesa driver revision ?
2- Why should Kodi not use vdpau whith is completly compatible whit AMD cards?

Otherwise for kodi.log i presume you would have complete log via system , logging, enable debug logging ?
should i add component-specifc logs?
Reply
#10
(2020-02-02, 22:52)enigma7 Wrote: 1- why diden't i have problem with Kodi 17.6 and same settings , same mesa driver revision ?
That will probably use VDPAU (you can go back and check the logs if you want), so it is not affected by the problem
(2020-02-02, 22:52)enigma7 Wrote: I've forced vlc video output to opengl (it was at vdpau) and now i have VAAPI output ... and same problem (image compressed half top screen, and every second complete screen for approx 0.1 seconds).
Maybe you could try mpv with vaapi hardware acceleration? That is pretty much the reference in my books.
(2020-02-02, 22:52)enigma7 Wrote: 2- Why should Kodi not use vdpau whith is completly compatible whit AMD cards?
VDPAU is pretty much dead and does not work with Wayland. If you want and are on X11, you can try to start with the environment variable KODI_GL_INTERFACE set to GLX.
(2020-02-02, 22:52)enigma7 Wrote: Otherwise for kodi.log i presume you would have complete log via system , logging, enable debug logging ?

Yes
(2020-02-02, 22:52)enigma7 Wrote: should i add component-specifc logs

Not add this point, no
Reply
#11
here is the log for mpv and recording from same channel, bot i'm not familiar with mpv and switches

mpv ./_RADIOFRECCIA_HD_02.ts
Playing: ./_RADIOFRECCIA_HD_02.ts
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: SPS unavailable in decode_picture_timing
[ffmpeg/video] h264: non-existing PPS 0 referenced
[ffmpeg/video] h264: decode_slice_header error
[ffmpeg/video] h264: no frame!
[ffmpeg/video] h264: mmco: unref short failure
[ffmpeg/video] h264: mmco: unref short failure
[ffmpeg/video] h264: number of reference frames (0+5) exceeds max (4; probably corrupt input), discarding one
[ffmpeg/demuxer] mpegts: PES packet size mismatch
 (+) Video --vid=1 (h264 1920x1080 25.000fps)
 (+) Audio --aid=1 --alang=ita (mp2 2ch 48000Hz)
VO does not support requested hardware decoder, or loading it failed.
[ffmpeg/video] h264: co located POCs unavailable
AO: [pulse] 48000Hz stereo 2ch s16
[ffmpeg/video] h264: reference picture missing during reorder
[ffmpeg/video] h264: reference picture missing during reorder
[ffmpeg/video] h264: reference picture missing during reorder
[ffmpeg/video] h264: reference picture missing during reorder
[ffmpeg/video] h264: Missing reference picture, default is 65682
[ffmpeg/video] h264: Missing reference picture, default is 65682
[ffmpeg/video] h264: Missing reference picture, default is 65682
[ffmpeg/video] h264: Missing reference picture, default is 65682
[ffmpeg/video] h264: reference picture missing during reorder
[ffmpeg/video] h264: reference picture missing during reorder
[ffmpeg/video] h264: Missing reference picture, default is 65700
[ffmpeg/video] h264: Missing reference picture, default is 65700
[ffmpeg/video] h264: Missing reference picture, default is 65700
[ffmpeg/video] h264: mmco: unref short failure
[ffmpeg/video] h264: mmco: unref short failure
[ffmpeg/video] h264: mmco: unref short failure
VO: [opengl] 1920x1080 yuv420p
AV: 00:00:06 / 00:03:09 (3%) A-V:  0.000


Exiting... (Quit)
Reply
#12
image was perfect
Reply
#13
and i have no gui setting under mint for mpv player, you must dag the file in the window .... lol
Reply
#14
I have post ticket Video rendering regression from 17.6 to 18.5 and AMD radeon HD 8570, linux platform #17314
Reply
#15
I think you have to do mpv --hwdec=vaapi
Reply

Logout Mark Read Team Forum Stats Members Help
AMD VAAPI regression for Leia 18.50