[Mplayer-cvslog] CVS: main/DOCS documentation.html,1.180,1.181 video.html,1.55,1.56

[Nick Kurshev]

Hello, Winner!

On Wed, 16 Jan 2002 18:12:22 +0100 you wrote:

> Update of /cvsroot/mplayer/main/DOCS
> In directory mplayer:/var/tmp.root/cvs-serv17133
> 
> Modified Files:
> 	documentation.html video.html 
> Log Message:
> Added (sigh, reHTMLized;)) Nick's VIDIX patch
> 
> 
[snip]
> +<P><B><I>USAGE METHODS</I></B></P>
> +
> +<P>When VIDIX is used as <b>subdevice</b> (<CODE>-vo vesa:xvidix</CODE>) then
                                                             ^
typo - should be -vo vesa:vidix

> +  video mode configuration is performed by video output device
> +  (<b>vo_server</b> in short). Therefore you can pass into command line of
> +  <B>MPlayer</B> the same keys as for vo_server. In addition it understands
> +  <CODE>-double</CODE> key as globally visible parameter. (I recommend using
> +  this key with VIDIX at least for ATI's card).<BR>
> +  As for <CODE>-vo xvidix</CODE> : currently it recognizes the following
> +  options: <CODE>-fs -zoom -x -y</CODE>.<BR>
> +</P>
> +
> +<P>Also you can specify VIDIX's driver directly as third subargument in command
> +  line :<BR>
> +  <BR>
> +  &nbsp;&nbsp;<code>mplayer -vo xvidix:mga_vid.so -fs -zoom -double
> +    file.avi</code><BR>
> +  or<BR>
> +  &nbsp;&nbsp;<code>mplayer -vo vesa:vidix:radeon_vid.so -fs -zoom -double -bpp
> +    32 file.avi</code><BR>
> +  <BR>
> +  But it's dangerous, and you shouldn't do that. In this case given driver will
> +  be forced and result is unpredictable (it may <b>freeze</b> your
> +  computer). 
Please add also: 
+You should do that only if driver doesn't recognize your card
+but you are sure that driver will work correctly with your card. Please tell
+about it to developers.

> + The Right Way is to use VIDIX without arguments to enable driver
> +  autodetection.
[snip]

Best regards! Nick