Open ilikenwf opened 8 months ago
ffmpeg log shows some inputs wrong sending to media driver. According to your description, it always decodes well with native bitstream, but only fails with online inputstream, so please check if application sends incompleted bitstream data to media driver.
Capture the libva trace log for both native bitstream and online bitstream firstly, then we can have some initial analysis: mkdir -p /home/trace export LIBVA_TRACE=/home/trace/file export LIBVA_TRACE_BUFDATA=1
If possible, use debug version media driver and capture some driver logs as well. mkdir -p /data/driver_dump put bellow config in /etc/igfx_user_feature_next.txt
[config] Codec Message Tags=7 DDI Message Tags=7 Message HLT Enabled=1 Message HLT Output Directory=/data/driver_dump Message Print Enabled=1 Mhw Message Tags=4 Mos Message Tags=4 [report]
Auto Created VSMGWL-72137 for further analysis.
Sorry, I haven't had a chance to test this.
Which component impacted?
Decode
Is it regression? Good in old configuration?
None
What happened?
In Linux, using Kodi, who uses VAAPI and ffmpeg for hardware video decoding, I attempt to play an HDR youtube video - any of them will do. This issue looks possibly similar to #629.
Interestingly, if I use yt-dlp or youtube-dl to download the HDR webm, it then plays properly. I have attempted to get help from the kodi devs and their inputstream.adaptive people, however they have not been able to assist me in determining this issue. See:
https://github.com/xbmc/xbmc/issues/23957 https://github.com/xbmc/inputstream.adaptive/issues/1410
Additionally, if I turn off VAAPI acceleration, thus using CPU/Software decoding, the video plays back properly.
The end result is:
What's the usage scenario when you are seeing the problem?
Playback
What impacted?
No response
Debug Information
I am using the -git head of libva, gmmlib, and media-driver.
The card is a sparkle A380 - ls /dev/dri renders
by-path card0 renderD128
03:00.0 VGA compatible controller [0300]: Intel Corporation DG2 [Arc A380] [8086:56a5] (rev 05)
Do you want to contribute a patch to fix the issue?
None