As of today's update, mpv failed to build with ffmpeg. I Googled for a solution, and found some patches on Arch Linux's site (NOTE: patches are attached to this post. Download into the mpv directory and rename the files to remove .txt extension) which fixed the problem for me. I slightly modified the mpv.SlackBuild to automatically apply the patches before configuring and building.

After the line that says: But before: I inserted three blank lines, arrowed up 2, and inserted this line to apply the patches: mpv built successfully, and I am now watching videos with it, after the slackpkg update.

Hope this helps!

Attached Files

	0001-opengl-backend-support-multiple-backends.patch.txt (11.0 KB, 109 views)
	0002-vaapi-Use-libva2-message-callbacks.patch.txt (3.0 KB, 163 views)
	0003-demux_lavf-return-AVERROR_EOF-on-file-end.patch.txt (931 Bytes, 56 views)
	mpv-do-not-fail-with-minor-ffmpeg-updates.patch.txt (1,021 Bytes, 89 views)

Its kind of silly to patch software that was intentionally broken out of the developer's personal spite. You're just going to get an unsupported build and a ton of pain when mpv upstream breaks it again.

Edit: Also for those you are missing the ytdl support built into mpv. This can be used with mplayer.

2 members found this post helpful.

I don't use mpv because of politics. I use it because it works well for my needs, and I patched it so I can continue using it. I concern myself mainly with technical issues.

I was just looking at the github issue this morning. Apparently this is already fixed in mpv's git master, and the next release should be fine.

https://github.com/mpv-player/mpv/issues/5081

Personally, I was just going to rebuild it without libva support.

I just tried building it and of those patches just the vaapi-Use-libva2-message-callbacks.patch seems actually needed for the new va stuff on current.
BTW, thanks for reporting this!

You're very welcome! I didn't know if all of them were needed or not; however, it does no harm, and I'm inclined to leave them in for my personal system.

I don't know when the next release is going to be, and I don't have much experience with building from git; I just used the method I was most familiar with, and it worked. However, I look forward to the next release with anticipation.

mpv git head already includes the fixes for the new va libraries, but it won't build against ffmpeg 3.4 (something to do with using a libav api that hasn't be ported to ffmpeg yet.). it will build against ffmpeg head (3.5-dev) so when ffmpeg 3.5 is released that issue should resolve itself (unless anything else breaks in the mean time.).

The last official release of mpv, v0.27.0, will build against ffmpeg 3.4 but it doesn't have the fixes for the new va library versions, so it fails to build on current as of today's update.

This is the situation we currently find ourselves in.


An alternative to patching is using "git checkout -f f36d152eb7" to checkout a revision of mpv that has the vaapi changes, but still works with ffmpeg-3.4, and building from that until such time as 3.5 is out and slackware has moved to it. @marrowsuck deserves the credit for finding that.

1 members found this post helpful.

just to clarify, mpv-0.27.0 builds fine against ffmpeg-3.4 on today's current with just this patch.

1 members found this post helpful.

but v0.28 most likely wont. The revision marrowsuck identified is 302 changesets ahead of v0.27.0 and I think will be as uptodate as you'll be able to get without using ffmpeg 3.5 or the ffmpeg-mpv fork (which I don't like the idea of).

Both approaches appear to be valid. Use either the git revision listed above, or 0.27 and the patch, and you should be fine for now.

This is not politics, a better description is pointless self sabotage that is being imposed on the users. If you want to deal with unfriendly projects go for it. I just want people who come to this thread to better understand why this issue exists.

1 members found this post helpful.

I'm not seeing much of a problem. They'll obviously delay the 0.28 release until FFMPEG 3.5 is out.

Yah that worked.

That's a perfectly good workaround for me, as I'm using the proprietary NVidia drivers.

Or it may be broken again when ffmpeg-3.5 is out. Mpv developers apparently has no respect for other projects and people shouldn't expect them to support ffmpeg anymore. It would be nice if they did, but I won't hold my breath for wm4 to rectify the damage caused by his tantrum or to not have another one.

In case the point was not clear, mpv works fine with ffmpeg-3.4 except for the fact that wm4 intentionally broke it because of personal issues. If it happened once it could happen again and users have only a few choices.

1. Play along.
2. Go through tedious efforts to undo the damage as its done.
3. Find an alternative.
4. Fork mpv.

In case my point was not clear, let me restate it. Personal developer issues (Read: politics) are not my concern. I use mpv because it meets my needs. If it breaks again in the future, I will again find a patch to fix it (which is not tedious, IMO) and move on.

1 members found this post helpful.