FS#39926 - [xbmc] VA-API is broken on Intel

Attached to Project: Community Packages
Opened by Scott Silverman (sctyboy) - Thursday, 17 April 2014, 22:12 GMT
Last edited by Ike Devolder (BlackEagle) - Monday, 28 July 2014, 18:55 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Ike Devolder (BlackEagle)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
When VAAPI is enabled in XBMC, and a video that should be hardware accelerated (i.e. h.264) is played, there is no video, only audio. If I disable VAAPI, there is video (but no hardware acceleration).

If I recompile without --enable-external-libraries and --enable-external-ffmpeg then VAAPI works as expected, and hardware acceleration is functional.

Additional info:
* xbmc 12.3-14
* Intel Core i5-4570S (Haswell, Intel HD 4600)


Steps to reproduce:
Enable "Allow hardware acceleration (VAAPI)" in System > Settings > Video > Playback. Play an h.264 or VC-1 encoded video.
This task depends upon

Closed by  Ike Devolder (BlackEagle)
Monday, 28 July 2014, 18:55 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed somewhere in between
Comment by Ike Devolder (BlackEagle) - Sunday, 08 June 2014, 12:36 GMT
still problems ?
Comment by Marc Cousin (cousinm) - Thursday, 24 July 2014, 14:51 GMT
As reported here https://bugs.archlinux.org/task/41324, this seems to have evolved a bit. Now, it hangs at the closing of the video.

Is there a point in enabling external ffmpeg ? (Just asking… I'd like to understand the problem). The XBMC devs insist that this will generate this kind of problems.
Comment by Ike Devolder (BlackEagle) - Monday, 28 July 2014, 09:05 GMT
external ffmpeg was enabled so we would get the latest security fixes as provided by the ffmpeg team, xbmc team is lagging far behind in some cases
Comment by Marc Cousin (cousinm) - Monday, 28 July 2014, 11:30 GMT
Hi, and thanks for the explanation.

The problem wasn't linked to ffmpeg, by the way: http://forum.xbmc.org/showthread.php?tid=200511

(not exactly the problem described here, but the one in #41324)
Comment by Ike Devolder (BlackEagle) - Monday, 28 July 2014, 17:41 GMT
so we can close this ?
Comment by Marc Cousin (cousinm) - Monday, 28 July 2014, 17:55 GMT
I haven't opened this bug. And I don't have the described problem. My bug was closed as being a duplicate of this one, but I still doubt it is the same. So I cannot answer this question.
Comment by Ike Devolder (BlackEagle) - Monday, 28 July 2014, 18:54 GMT
i guess this is fixed too, if i remember correctly one of our devs is using xbmc with intel so i guess it would be fixed by now ;)

Loading...