Tom Corr wrote:
On Friday 03 March 2006 09:04, Manuel Soriano wrote:
For a while i don't use other viewer than mplayer :
http://www.mplayerhq.hu/design7/dload.html
very easy to configure, compile & using...
I've been trying to build the latest "MPlayer" from CVS as you mentioned. It builds just fine, however, it will not use the Win32Codecs. I've tried the following "configure" lines without any success. It will play some files fine, but "NOT" wmv9 formats.
1 - ./configure --enable-gui
2 - ./configure --enable-gui --with-codecsdir=/usr/local/lib/codecs
3 - ./configure --enable-gui --with-codecsdir=/usr/local/lib/codecs --with-win32libdir=/usr/local/lib/codecs
The first two actually "make" successfully but the last one fails to "make" at all - wine/*.c compile errors. In all three cases i get the message, and in all three cases the /usr/local/lib/codecs directory contained the codecs from the mplayerhq page:
NOTE: Win32 codec DLLs are not supported on your CPU (x86_64) or your operating system (Linux). You may encounter a few files that cannot be played due to missing open source video/audio codec support.
Anyhow, at least for now, I think I'm sticking with the 32bit version of MPlayer since it has no problem with these codecs.
If I missed something obvious with this please let me know. I would love to be able to build mplayer in 64 bit.
I *think* you're fine using the 32-bit version of MPlayer, there are *no* advantages at all to using a 64-bit version of the app in this case, and many disadvantages (codecs not available, for starters). 32-bits apps execute fine under 64-bit SuSE linux, no disadvantages, no inefficiencies, no nothing. Just use the 32-bit & let the good times roll :-). $0.02, no more, no less .... -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton