Skip to Content.
Sympa Menu

baslinux - Re: [BL] MPlayer 1.0pre7try2

baslinux AT lists.ibiblio.org

Subject: Baslinux mailing list

List archive

Chronological Thread  
  • From: sindi keesan <keesan AT sdf.lonestar.org>
  • To: baslinux AT lists.ibiblio.org
  • Subject: Re: [BL] MPlayer 1.0pre7try2
  • Date: Thu, 23 Feb 2006 22:55:50 +0000 (UTC)

On Wed, 22 Feb 2006, David Moberg wrote:

There is a new mplayer binary available at my geocities site.

Please list the URL when you tell us about a new binary.

Sorry. Subject to change, the URL is:

http://us.share.geocities.com/davidjmoberg/mplayer-new.tgz


This is a new package, not just the binary.

Using 3c59x (3com PCI) I was unable to ifconfig down in order to remove the eth0 which was using IRQ5 on the computer without DVD player, so I had to insmod sb at IRQ10, which was free (SCSI had 9, eth0 had 5). Mplayer old played wav files there perfectly with ao=oss in /root/.config/mplayer.
I used to play DVDs on it. S3 Trio3D video card, Xvesa or vesa.

On the other computer, which now has the DVD drive, I also now have the jumpered AWE32 card, which is IRQ 10 and DMA 3 and DMA16 6, and I had to change the settings when I insmodded sb for it.

Play plays wav files on both.

The DVD drive is now in a computer with Matrox Millenium VESA 2.0 card.
It does not play DVDs with old or new mplayer in vesa mode. (It also crashes in vesafb mode if you load any video mode other than default, but works with matroxfb).

framebuffer (-vo vesa) produces a scrambled picture with several copies of the same image side by side and lines through them.

XVesa (-vo x11) works with both players.

The old mplayer does not do svgalib. The new one does.
Matrox does not work too well with no chipset specified in libvga.config (it exits to odd colors but you can switch VTs, and I think chipset VESA may crash it to the point you need to reboot, I forget though).
So I had specified chipset xfbdev, which works better for zgv.
For Mplayer it produces a single image, which blinks continuosly. So I set it back to chipset unspecified and Mplayer now displays properly.

On the old computer I had /root/.mplayer/config set to
ao=oss
vo=vesa

These worked the same as CLI -ao oss -vo vesa with Trio3D card.

On the new computer I can specify -ao oss and -vo svga CLI, but the config file does not work. I get a message about Audio: no sound if I use just the config file, and video looks first for X11 and then eventually finds svgalib. x11 is the default, I think. So I need to specify both on command line. I made a script. Is Matrox causing this problem somehow?
The config file works on one computer and not on the other.

One time when I did not specify -vo, it put a message on the screen about the monitor being out of scan range and I can no longer user either of my VGA terminals (I have two MGA terminals left working). Matrox is odd. Maybe it tried to use some format that displays at very high resolution? This is my best monitor, which goes to 85Hz HorizSync, but the card probably can display even more.

I had not tried Mplayer with dvds on this computer, using the old package. Did the new package somehow affect the setup so that even the old binary won't look at the config file? I installed the whole package, not just the binary. This is a puzzle.

Anyway, the Matrox can be made to work with Mplayer on this 600MHz machine with a jumpered sound card.

David, thanks for the svgalib support for use with Matrox cards (which also work with Xvesa but probably slower). I cannot compare quality of vesa and svgalib because the Matrox won't do vesa.




Archive powered by MHonArc 2.6.24.

Top of Page