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.
Thanks for pointing that out, it works ! I didn't realize there is a new version from you, so I in fact was compiling from the older version from 13.1. Yeah, the latest version of ffmpeg is superb, I will be exciting trying a lot of nice features from them then.
One thing I would like to know that, I did put in
in your ffmpeg.SlackBuild this time before compile, since I recall the compiled version will not support xvid and vorbis conversion if I don't do that last time. So is that two needed this time in order to convert source into xvid and vorbis output ?
And just curious that, for all the codec needed in this while compiling, can they being stored in some place in the disk so that it could be shared with xine, vlc, or mplayer as well ? As I found out we need to have collecting them separately for different player while compiling, so is there already some way to store them centralize at some library folder and shared together among all the players ? As it's really redundant needing to find the codec differently for different players and sometime one can play certain file format while the other can't play another. I just scared I'm using some outdated way to build my mplayer, xine..etc. So if anybody already have some way to download once all the codec and shared with other players on the fly, I will be grateful to know that, thanks. (Please forgive me if this question sound silly as I basically don't know much about how all the player works with the codec thingy)
I never had issues with encoding to vorbis and xvid so I have no idea if that would require "--enable-libvorbis --enable-libxvid". Basically ffmpeg has its own internal vorbis and xvid implementation so it does not have to rely on these external libraries. But you may prove me wrong if you can give me an URL which shows that these additional options are needed (in which case I would add them to my script of course).
In the meantime, ffmpeg does show encoding support for vorbis as well as xvid (xvid is a variant of mpeg4):
$ ffmpeg -codecs 2>/dev/null | egrep -i "(vorbis|mpeg4)"
DEVSDT mpeg4 MPEG-4 part 2
DEVSD msmpeg4 MPEG-4 part 2 Microsoft variant version 3
D VSD msmpeg4v1 MPEG-4 part 2 Microsoft variant version 1
DEVSD msmpeg4v2 MPEG-4 part 2 Microsoft variant version 2
DEA vorbis Vorbis
Encoding xvid video uses these parameters if you use the mpeg4 codec instead of libxvid:
ffmpeg -vcodec mpeg4 -vtag xvid
. There are some discussions on the internet about quality differences, I"d like to hear everyone's opinions on this!
The ffmpeg package installs shared libraries into your computer which can be used by other programs. However, programs like xine, mplayer and others each have their own copy of an ffmpeg version that the developers thought was most compatible to their own code, so it will not always be easy to compile these media players against a system-ffmpeg (but it is possible!).