How do you compile MPlayer with H.264 Support?

ComputerGreek · 02-24-2008, 07:10 PM

So how come the moderators who have written books on mplayer never help.

I guess they are not here to help at all.

Daws · 02-26-2008, 07:57 AM

I agree with andrew, svn is the way foward, if only to save bandwidth. I've used x264 now and again, it fairly easy to get up and running. I'd normally proceed as follows:

Code:

svn co svn://svn.videolan.org/x264/trunk x264
cd x264
./configure --prefix=/usr/local --enable-shared
## personally I wouldn't use --enable-gtk, its not necessary for mplayer
make
[as root]make install

I use nasm myself, If you can use an assembler you definitely should, it will make a difference. No need to strip anything, it's all done automatically.

mplayer's configure script should detect x264 automatically. If it can't find /usr/local/include/x264.h then you have bigger problems

Now onto more interesting topics:

Quote:

Yeah, there are hundreds of instances of "Linux" people sabotaging Linux software, in particular, video and music software.

Usually, they (indirectly) work for the RIAA, MPAA, etc.

That's a pretty heavy accusation. Do you really believe that videolan, the people who bring us libdvdcss, libdca, x264 etc and other groups are being sabotaged from the inside by the powers that be? It sounds a bit silly to me. Or do you have some reliable sources?

Secondly:

Quote:

So how come the moderators who have written books on mplayer never help.

I guess they are not here to help at all.

No need for smartass comments. It's not going to endear you to anyone here.

ComputerGreek · 02-26-2008, 08:51 AM

How much for me to fix the "mistakes" in the faac and x264 source?

ComputerGreek · 02-28-2008, 04:22 PM

Everyone has given up on this?

ComputerGreek · 03-03-2008, 08:56 AM

Quote:

Originally Posted by Daws

I agree with andrew, svn is the way foward, if only to save bandwidth. I've used x264 now and again, it fairly easy to get up and running.

I agree that generally svn is better because it gives you very recent code. However, the x264 source is packaged daily, so....

Quote:

Originally Posted by Daws

That's a pretty heavy accusation.

It also true. There are many people working very hard to make the code the best they can and many working very hard to make it unusable for the majority.

Take a look at the history of the NTFS kernel driver as an example.

Take a look at MingW.

Take a look at bootsplash.org

Take a look at the general state of Linux docs.

ComputerGreek · 03-04-2008, 06:03 PM

Quote:

Originally Posted by Daws

No need for smartass comments. It's not going to endear you to anyone here.

The smartass comments came second. The ignoring of any thread I have a say in came first.

ComputerGreek · 03-08-2008, 07:31 AM

Does anyone know anything about the apparent crippling of avc and H264?

ComputerGreek · 03-22-2008, 12:58 AM

Quote:

Originally Posted by ComputerGreek

Does anyone know anything about the apparent crippling of avc and H264?

Anything at all about it would help.

dina3e · 03-22-2008, 05:51 AM

Quote:

Originally Posted by ComputerGreek

By the way, the --disable-nls does not work.

I miss-typed the command line as:

./configure --enable-shared --enable-gtkl --disable-nls

This caused GTK to be disabled, which gave me the idea that the --disable-nls option had worked.

Thus it compiled, but without GTK.

The moral is: if your version of gettext contains xgettext, then use the --enable-gtk option. Otherwise, upgrade gettext or just use

./configure --enable-shared

i have done succesful install the player
thank u....