[SOLVED] -current, ffmpeg and restricted multimedia libraries

Gerard Lally · 08-10-2018, 06:34 PM

I'm about to install -current again.

How do users handle ffmpeg, now that it is included by default? Eric's ffmpeg (and VLC, I believe) is unencumbered by patent constraints, and includes codecs available at SlackBuilds. Do users who are allowed to do so install Eric's build, after removing the stock ffmpeg? If so, are the codecs included in Eric's ffmpeg available system-wide? Do users need to re-build stock packages (Mplayer, perhaps) to take advantage of the expanded set?

dugan · 08-10-2018, 07:25 PM

I actually just dealt with this recently.

Use the -current SlackBuild. Keep the source and version. But change the BUILD as needed, and set any needed feature overrides in the environment. For example:

Code:

X264=yes BUILD=1dc ./ffmpeg.SlackBuild

That will build FFMPEG with more encoders while still remaining safely ABI-compatible with your installed software.

RadicalDreamer · 08-11-2018, 03:31 AM

I use the Official FFMPEG Slackware build on one computer and the other I build my own based on my edited Official FFMPEG Slackbuild and the source code. I build QMPlay2 from source for its CUDA goodness and its my main video player. I also build vlc from source. Xine, mplayer I use the official builds. I usually use those to watch something real quick. I think you can get away with just using the official FFMPEG Slackware build just fine.

Gerard Lally · 08-11-2018, 03:38 AM

Quote:

Originally Posted by dugan

I actually just dealt with this recently.

Use the -current SlackBuild. Keep the source and version. But change the BUILD as needed, and set any needed feature overrides in the environment. For example:

Code:

X264=yes BUILD=1dc ./ffmpeg.SlackBuild

That will build FFMPEG with more encoders while still remaining safely ABI-compatible with your installed software.

That sounds straightforward. I'll go with that. Thank you.

chrisretusn · 08-11-2018, 03:48 AM

I use the slackpkg+ add-on to manage these things.

I normally use Alien Bob's SlackBuild script for ffmpeg. If that happens to fail and I can't finger it out or don't want to mess with trying; I just download the non-restricted package. Either way, the packages are added to my personal repository and then installed using slackpkg.

I do this with Slackware packages I have recompiled too. Example; this machine uses a compiled version (using a modified stock Slackware cups.SlackBuild) of cups that supports avahi. That over rides the cups that comes with Slackware as that package is placed in my personal repository. The add-on slackpkg+ make this possible. My other machines do not use this modified package so it does require an entry in blacklist to exclude that package so the cups that comes with Slackware will be installed.

Slackpkg+ is an awesome tool! So is slackpkg!