FFMPEG updates require MPV recompile.

Dreyeth · 2016-11-26 16:56:44

ffmpeg library versions:
   libavutil       55.34.100
   libavcodec      57.64.100 (runtime 57.64.101)
   libavformat     57.56.100
   libswscale      4.2.100
   libavfilter     6.65.100
   libswresample   2.3.100
ffmpeg version: 3.2.1

mpv was compiled against a different version of FFmpeg/Libav than the shared
library it is linked against. This is most likely a broken build and could
result in misbehavior and crashes.

mpv does not support this configuration and will not run - rebuild mpv instead.

Now that a new version of FFMPEG got shipped out the version of MPV in the package repositories
has been compiled against a older version and won't have any of it.

I've been reading the MPV documentation and there is a few things they set the program to insist
on a recompile for if they're updated and MPV was compiled against a older software version.

Well anyway time to go recompile MPV and watch some Bleach on the console with my second monitor. >:)

klaus · 2016-11-26 17:37:44

For this case in particular you could've just downgraded the package using the previous version located in your pacman cache, this way you can avoid rebuilding and still use the previous version that was working correctly. Not to mention whenever you update your system again you can always check to see if mpv was upgraded too and avoid this issue, I think this was an oversight but I might be wrong.

To find the cached versions for ffmpeg:

ls /var/cache/pacman/pkg | grep ffmpeg

To downgrade the package:

pacman -U /var/cache/pacman/pkg/ffmpeg-1:<version, etc or tab complete>

Possibly more details on the wiki: https://wiki.archlinux.org/index.php/Do … g_packages

Edit: a bit more clarification.

Last edited by klaus (2016-11-26 17:41:09)

whoops · 2016-11-26 19:11:54

Or you can just

yaourt -Sb --noconfirm mpv

which took about 3 minutes and now mpv works again.

( Yes, there are many reasons to dislike yaourt, but for rebuilding from ABS it's just great. I use it frequently when something like this happens or when I need debug symbols... because it's just so convenient. Also I use it to recompile my kernel when I'm cold. Which is bad. Don't do that. Works though in a small room. But it's bad. )

jasonwryan · 2016-11-26 19:19:37

Or, rather than workarounds, someone could do something useful and open a bug report...

# edit: https://bugs.archlinux.org/task/51964

klaus · 2016-11-26 19:56:11

jasonwryan wrote:

Or, rather than workarounds, someone could do something useful and open a bug report...

I don't really like my answer but it brings me back to my question (well, it wasn't phrased like one but still), wasn't this just an oversight on the build process for ffmpeg, not rebuilding mpv and pushing it to the repos along with it? This is an honest question, not trying to be snarky. I haven't used mpv today yet, but waiting for a proper rebuild and holding back on the ffmpeg upgrade is what I would do if it had affected me.

jasonwryan · 2016-11-26 19:58:04

Yes, it was an oversight. Opening a bug report would draw it to the dev's attention (as a rule, they don't read threads here).

jasonwryan · 2016-11-26 22:07:23

Fixed in 1:0.22.0-2

Arch Linux

#1 2016-11-26 16:56:44

FFMPEG updates require MPV recompile.

#2 2016-11-26 17:37:44

Re: FFMPEG updates require MPV recompile.

#3 2016-11-26 19:11:54

Re: FFMPEG updates require MPV recompile.

#4 2016-11-26 19:19:37

Re: FFMPEG updates require MPV recompile.

#5 2016-11-26 19:56:11

Re: FFMPEG updates require MPV recompile.

#6 2016-11-26 19:58:04

Re: FFMPEG updates require MPV recompile.

#7 2016-11-26 22:07:23

Re: FFMPEG updates require MPV recompile.

Board footer