Package Details: intel-media-sdk 1:2019.2.1-4

Git Clone URL: (read-only)
Package Base: intel-media-sdk
Description: API to access hardware-accelerated video decode, encode and filtering on Intel platforms with integrated graphics
Upstream URL:
Keywords: hwaccel intel libmfx media mediasdk mfx qsv quicksync quicksyncvideo sdk video
Licenses: MIT
Provides: libmfx
Submitter: dbermond
Maintainer: dbermond
Last Packager: dbermond
Votes: 24
Popularity: 0.030367
First Submitted: 2016-01-09 17:17
Last Updated: 2019-09-18 21:37

Latest Comments

1 2 3 Next › Last »

dbermond commented on 2019-09-18 21:39

Forgot the checksums. Fixed :)

adsun commented on 2019-09-18 19:43

checksums for intel-media-sdk.conf need to be updated

oddworld commented on 2019-09-18 18:27


Thank you. Works perfectly now. I really appreciate the quick turnaround and all of your support.

dbermond commented on 2019-09-18 17:48

@Raansu @oddworld fixed.

oddworld commented on 2019-09-17 14:01

Similar error. The path ...lib64 does not exist. However, "lib" does exist.

intel-media-sdk/pkg/intel-media-sdk/opt/intel/mediasdk/lib64 (does not exist)

intel-media-sdk/pkg/intel-media-sdk/opt/intel/mediasdk/lib (does exist)

Raansu commented on 2019-09-17 03:23

I'm getting this error. Is this an issue with the package or the AUR helper pikaur?

ln: failed to create symbolic link '/home/<USER>/.cache/pikaur/build/intel-media-sdk/pkg/intel-media-sdk/opt/intel/mediasdk/lib64/' : No such file or directory

francoism90 commented on 2019-07-26 07:23

@dbermond Probably because the path of isn't whitelisted in the profile.

dbermond commented on 2019-07-25 21:41

@francoism90 I cannot see how firejail could cause such an issue with ffmpeg for you.

francoism90 commented on 2019-07-25 17:03

@dbermond Thanks for your suggestion, will test and push them asap. :)

However sorry for all the noise! It turns out the latest firejail update did cause this issue. I'll check what's causing it.

dbermond commented on 2019-07-24 20:38

@francoism90 You should use only this package with ffmpeg-qsv, as it provides the dispatcher library (libmfx) and the plugins.

No need to add libmfx to depends, otherwise ffmpeg may link against the wrong file, as your output is suggesting. You need to remove it from depends and rebuild ffmpeg against this package, in the say way it's done with ffmpeg-full.

Offtopic: by the way, you don't need to add opencl drivers to the optdepends of ffmpeg-qsv PKGBUILD. You only need to add ocl-icd to depends, and it will automatically request the user to install the desired opencl driver. The same logic applies to libva drivers (except that the user should install a vaapi driver by himself), and there is no need for libva-utils. Also, the package should conflict only with ffmpeg, as the the other ffmpeg packages provides ffmpeg.