SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I rebuilt it this morning on Slackware-current with no problems. I used the Slackbuild from 14.0, changing that line also. It would seem that something is wrong with libmpdemux, so I would start there. That said, I'm no expert.
Well in order to have libmp3lame suppport in mencoder, you will have to recompile MPlayer in the presence of an installed lame package...
MPlayer itself does not come with lame libraries. The same holds true for a lot of other useful libraries. All that the MPlayer.SlackBuild does when you define USE_PATENTS=YES is remove the explicit "disable" configurations for patent-encumbered codecs so that these codecs can be included... if they are found in your filesystem at compiletime. Which is not the same as enabling those in the default build.
This is something I have never clarified before because I never actually checked mencoder's capabilities. I never use it.
I will probably build a new MPlayer package with lame as a dependency.
Ok i download Mplayer from that link but that package is not build with libmp3lame support
MEncoder has not been actively developed for a long, long time and it is probably past time that it should be removed from the MPlayer source (as indeed it has been from the MPlayer2 fork). You would be pleasantly surprised by the far superior results from a recent copy of FFmpeg I suspect...
This is true that libmp3lame is often used with MEncoder, for example: http://quadpoint.org/projects/simplerip/. On the other hand MEncoder will try to continue its work, even if this library is not installed, meaning that it should print a warning and switch automatically to any other available way of decoding.