Package Details: libva-intel-driver-g45-h264 2.4.1-1

Git Clone URL: https://aur.archlinux.org/libva-intel-driver-g45-h264.git (read-only, click to copy)
Package Base: libva-intel-driver-g45-h264
Description: VA-API implementation for Intel G45 with H264 support
Upstream URL: https://bitbucket.org/alium/g45-h264
Licenses: MIT
Conflicts: libva-intel-driver
Provides: libva-intel-driver
Submitter: pedromj
Maintainer: xiota
Last Packager: xiota
Votes: 65
Popularity: 0.025602
First Submitted: 2014-08-04 02:05 (UTC)
Last Updated: 2024-03-05 14:12 (UTC)

Dependencies (5)

Required by (29)

Sources (1)

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 24 Next › Last »

hans0 commented on 2017-04-25 15:14 (UTC) (edited on 2017-04-25 15:25 (UTC) by hans0)

I tried this driver with bomi-git: 720p acceleration works, 1080p stutters (without the patch from @tegularius).

Raziel23 commented on 2017-04-22 15:45 (UTC)

@tegularius: Yes your patch works without patching mpv or ffmpeg. @alium: Please apply the patch from @tegularius.

tegularius commented on 2017-04-22 13:44 (UTC) (edited on 2017-04-22 14:04 (UTC) by tegularius)

Parts of the driver had not been patched for support h264. It seems that the driver support for ironlake is the same as it should be for g4x-devices, so I patched it to return the same surface-attribute-information. Works as far as I can tell. https://gist.github.com/anonymous/e5383bd3c78bf389d124fcecde5a1556

Raziel23 commented on 2017-04-21 17:27 (UTC) (edited on 2017-04-21 19:37 (UTC) by Raziel23)

@tegularius: I dug a little bit about this issue. When mpv is compiled against ffmpeg 3.2.4 it uses an old vaapi infrastructure, which means that vaapi is handled by mpv player. On the other hand when mpv is compiled against ffmpeg 3.3 it uses a new API, which means that vaapi is handled by ffmpeg. They differently handle vaapi. FFmpeg rely on codec/format configuration that is returned by libva-intel-driver-g45-h264. I don't know if this can be fixed in libva-intel-driver-g45-h264 (I looked into a source code but don't have enough knowledge), but there are two other solution that works for me: 1. Use old vaapi infrastructure in mpv when compiled against ffmpeg 3.3. Disclaimer: old vaapi infrastructure maybe removed from mpv in the future. Compile mpv with the following flags: https://gist.github.com/anonymous/3e0daaedc6fcfa1e41365696c79883ba 2. Fix ffmpeg 3.3 with patch which do: if hardware configuration returned by libva-intel-driver-g45-h264 driver doesn't have any relevant format then returns a full set of image formats and check one by one if any format is relevant to decode h264: https://gist.github.com/anonymous/8670b535237f0e650947092586e9446d Use either one solution. I don't know if this can be fixed in libva-intel-driver-g45-h264 package. Edit: Upload patches to gist.

tegularius commented on 2017-04-20 19:45 (UTC) (edited on 2017-04-20 19:46 (UTC) by tegularius)

Sadly doesn't seem to work, mpv says: [vd] Pixel formats supported by decoder: vdpau vaapi_vld yuv420p [vd] Codec profile: Main (0x4d) [ffmpeg/video] h264: Hardware does not offer any usable surface formats. [vd] Pixel formats supported by decoder: vdpau yuv420p [vd] Codec profile: Main (0x4d) [ffmpeg/video] h264: Reinit context to 1280x720, pix_fmt: yuv420p [vd] Falling back to software decoding. vainfo reports: libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: Intel i965 driver for Intel(R) GM45 Express Chipset - 1.8.1 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264Main : VAEntrypointVLD VAProfileH264High : VAEntrypointVLD

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 24 Next › Last »