Yes, that's my sentiment too! I'm afraid my programming days ended with 8-bit 6502s, so writing a patch for mpv is somewhat beyond me! If you manage it, remember to let us know!

In the meantime, someone in the other thread has pointed out QMPlay2, which looks like a viable alternative....

--
Pete

Hey, Pete. I have seen some of your other posts, and can truly empathize with some of the issues you've had with your system, as I have also struggled with my system having its own set of issues.

The patch I was referring to originally is referenced in my original post. My point of view is that if the program works for my needs, then that's all that matters. And there's always someone who has come across the same issues as I in any given program, and there's almost always a workaround or patch. Google is your friend.

Hope this helps.

Re-reading my post, I realise it wasn't as clear as I had intended! I meant if you write a patch in future, please let us know! Sorry for any confusion!

There has been a huge flurry of upgrades in -current recently (new release imminent?), and I would expect this to cause the odd breakage. Usually I manage to work around it, but this time I came unstuck! I still haven't figured out why the MPlayer build script threw a tantrum, but I don't need to any longer, and no doubt it will be picked up by the team in due course. I really don't want to use the vdpau workaround unless I absolutely have to. Its not that I have anything against vdpau - both my other machines use ati gfx and the kernel drivers, and vdpau works fine on them. But using a translation layer from vdpau to vaapi seems like a kludge - however well intended - that I would rather avoid!

Thanks for your help, and to all the other contributors to this, and the other, thread

--
Pete

You're very welcome. It's my contribution. I certainly enjoy using Slackware, and do my best to help others in some small way.

Happy Slacking!

If they'd decided to continue with their FFMPEG fork, then my recommendation would have been to have one MPV SlackBuild that does the following:

1. installs ffmpeg (theirs) into $PKG/usr/lib$LIBDIRSUFFIX/mpv
2. builds mpv against it, using "-Wl,-rpath=/usr/lib/lib$LIBDIRSUFFIX/mpv -L$PKG/usr/lib$LIBDIRSUFFIX/mpv"

This is a fairly standard way of building dependencies into a package.

I did suggest this on the slackbuilds-users mailing list.

That is a really ugly hack as far as package distribution goes, but to be fair there are no good solutions here.

I've actually seen it documented elsewhere, but I'm not going to look for it right now.

(EDIT: example 1, example 2).

I wasn't aware of the helper build script mpv project provides:

https://github.com/mpv-player/mpv-build

It's as easy as this:

It fetches latest ffmpeg and libass from git HEAD and links them statically. There are also options to use release versions instead, see README.

Works flawlessly, just copy the resulting mpv executable where you want.

I have a SlackBuild that uses that to build a proper Slackware package. It currently builds 0.28.

https://github.com/duganchen/my_slac...mpv.SlackBuild

I'd mentioned it in another thread about this issue, but I can't find that thread right now.

I dont have any problem with mpv + ffmeg on the contrary, only hapiness.
I can play any kind of videos (4k, hvec, ts, hdr, 10bits, etc) with hardware off course.

Please do not judge me, i'm just an amateur.
My personal builds
first https://github.com/ericfernandesferreira/audio
second https://github.com/ericfernandesferreira/video

Just a heads up for anyone still using mpv. Nasty remote code execution: CVE-2018-6360

After a lot of prompting and resistance it looks like they've tagged a 0.27.1 and 0.28.1, but it's clear from the comments here that the mpv dev's don't consider security issues their responsibility to patch in anything other than git master, which kind of makes a mockery of tagging releases in the first place.

Anyway, be warned.

2 members found this post helpful.

Just use my SlackBuild to build 0.28.1.

for good luck with version 0.28.2 you need to apply only one fourth patch

(mpv-do-not-fail-with-minor-ffmpeg-updates.patch)

Again: just use my SlackBuild to build 0.28.2. It will build all future versions without needing to be updated.

Doesn't your mpv build pull down and embed it's own copy of ffmpeg? The reason I switched from mplayer to mpv in the first place was that it used the system installed ffmpeg library rather than it's own embedded version.

Now, somewhat ironically, it's easier to get mplayer to use the system library than it is mpv.

1 members found this post helpful.