Welcome!
Important information
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities

News
-- Introducing our new Website
-- MX Linux on social media: here

Current releases
-- MX-18.1 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.4 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

MX 17 Repository: The FFMpeg thread

Post Reply
User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 18411
Joined: Fri Dec 15, 2006 8:07 pm

MX 17 Repository: The FFMpeg thread

#1

Post by Stevo » Wed Dec 19, 2018 3:22 pm

Astute update watchers may have noticed an upgrade to the 3.3.4 ffmpeg and libav* libraries shipped with MX 17/18 come down the pipe into main. This turned out to be necessary because of our newly upgraded libva* libraries (va-api hardware decoding and encoding, mainly for Intel GPUs) required that ffmpeg needed to be rebuilt against them instead of the stock Stretch versions; otherwise va-api was broken.

I also fixed the ffmpeg 4.0.3 in MX 17 testing the same way. I've found that QMPlay2 is the easiest program to test if va-api hardware decoding is working on your machine; just switch between the FFMpeg decoder and FFMpeg VA-API decoder at the top of the Decoders Priority in Playback Settings, and try and play some 4K video, like the Elysium movie trailer. (Intel GPU users need to install i965-va-driver, also just updated to support newer hardware; maybe we should include this on the ISO) CPU use can then be monitored in Conky or in "top", among many other options.

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 18411
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX 17 Repository: The FFMpeg thread

#2

Post by Stevo » Tue Jan 08, 2019 7:24 pm

I just backported FFMpeg 4.1 to support Handbrake 1.2.0 package builds. At first, after installing Handbrake from my local repo, it threw a va-api error:

Code: Select all

/usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so has no function __vaDriverInit_0_32
but that error went away after I also upgraded libavcodec-extra, and now Handbrake seems to have hardware-accelerated transcoding using my Intel GPU! Woot!

So for those that are having trouble with va-api encoding with our standard ffmpeg, perhaps installing libavcodec-extra will fix that.

The new packages should be in the test repo soon. FFMpeg 4.1 upgrades smoothly over 4.0.3, and won't affect older libav* packages, such as libavcodec57.

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 18411
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX 17 Repository: The FFMpeg thread

#3

Post by Stevo » Wed Jan 09, 2019 4:10 pm

4.1 is now in the test repo. Remember that you have to disable "hide libs and dev packages" in the MX Package installer if you want libavcodec-extra to be available, which may allow va-api hardware encoding to work (needs testing).

Post Reply

Return to “Package Requests/Status - MX 17/18”