Mercurial > mplayer.hg
changeset 11067:2340e006992f
updated Vidix section to reflect newest developments
author | gabucino |
---|---|
date | Thu, 09 Oct 2003 22:24:07 +0000 |
parents | e16982ed6708 |
children | f33f908ae085 |
files | DOCS/xml/en/video.xml |
diffstat | 1 files changed, 10 insertions(+), 5 deletions(-) [+] |
line wrap: on
line diff
--- a/DOCS/xml/en/video.xml Thu Oct 09 22:20:31 2003 +0000 +++ b/DOCS/xml/en/video.xml Thu Oct 09 22:24:07 2003 +0000 @@ -1325,6 +1325,14 @@ the option "XaaNoPixmapCache" in the screen section instead. </simpara></listitem> <listitem><simpara> + There is a console vidix driver: <option>-vo cvidix</option>. + This requires a working and initialized framebuffer for most cards (or else + you'll just mess up the screen), and you'll have a similar effect as with + <option>-vo mga</option> or <option>-vo fbdev</option>. nVidia cards however + are able to output truly graphical video on a real text console. See the + <link linkend="vidix-nvidia">nvidia_vid section</link> for more information. + </simpara></listitem> +<listitem><simpara> You can use VIDIX subdevice which was applied to several video output drivers, such as: <option>-vo vesa:vidix</option> (<emphasis role="bold">Linux only</emphasis>) and @@ -1340,11 +1348,8 @@ <itemizedlist spacing="compact"> <title>REQUIREMENTS</title> <listitem><simpara> - Video card should be in graphics mode (I write <emphasis role="bold">should</emphasis> - simply because I tested it in text mode - it works but has awful output ;) Use - AAlib for that). - <emphasis role="bold">Note</emphasis>: Everyone can try this trick by commenting out mode - switching in vo_vesa driver. + Video card should be in graphics mode (except nVidia cards with the + <option>-vo cvidix</option> output driver). </simpara></listitem> <listitem><simpara> <application>MPlayer</application>'s video output driver should know