mpv and ffmpeg - Patch for successful build
4 Attachment(s)
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: Code:
Code:
chown -R root:root . Code:
for i in $CWD/*.patch; do patch -p1 < $i; done Hope this helps! |
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. Code:
mpv() { |
Quote:
|
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! |
Quote:
|
Quote:
|
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. |
Quote:
|
Quote:
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. |
Quote:
|
I'm not seeing much of a problem. They'll obviously delay the 0.28 release until FFMPEG 3.5 is out.
|
Quote:
Code:
env BUILD_OPTS=" --disable-vaapi " ./mpv.SlackBuild |
Quote:
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. |
Quote:
|
All times are GMT -5. The time now is 10:55 PM. |