From 988e72ebc32f7e0c8252f111d25ff67645329152 Mon Sep 17 00:00:00 2001 From: gabucino Date: Thu, 7 Mar 2002 17:55:34 +0000 Subject: HTML: different font handling - idea from new hp dezign ocassional misc fixes git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@4983 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/video.html | 208 +++++++++++++++----------------------------------------- 1 file changed, 56 insertions(+), 152 deletions(-) (limited to 'DOCS/video.html') diff --git a/DOCS/video.html b/DOCS/video.html index fed0a59220..a0cd131aff 100644 --- a/DOCS/video.html +++ b/DOCS/video.html @@ -1,114 +1,18 @@ - - - -

2.3.1. Video output devices

+ + + - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

General:

  x11  X11 with optional SHM - extension
xvX11 using overlays with the Xvideo extension - (hardware YUV & scaling)
glOpenGL renderer, so far works only with: -
  • all cards with Utah-GLX -
  • Matrox cards with X/DRI >=4.0.3 -
  • Radeon with X/DRI CVS
gl2OpenGL renderer, multiple textures version
dgaX11 DGA extension
fbdevOutput to general framebuffers
svgaOutput to SVGAlib
sdl -  1.1.7: supports software scaling
-  1.1.8: supports Xvideo (hardware scaling/fullscreen)
-  1.2.0: supports AAlib (-vo aa is very recommended, see below!)
ggisimilar to SDL
aatextmode rendering with AAlib
vesaOutput to VESA BIOS.
vidixVIDeo Interface for *niX (this entry is not a - real driver, but an explanation of VIDIX)
xvidixVIDIX in X window
directfbDirect Framebuffer Device

Card specific:

  mga  Matrox G200/G400 hardware - YUV overlay via the mga_vid device
xmgaMatrox G200/G400 overlay (mga_vid) in X11 - window
-(Xv emulation on X 3.3.x!)
syncfbMatrox G400 YUV support on framebuffer (obsoleted, use - mga/xmga)
3dfxVoodoo3/Banshee hardware YUV (/dev/3dfx) support (not yet tested, maybe - broken)
tdfxfbVoodoo3/Banshee hardware YUV support on tdfx - framebuffer (works!)
zrDisplaying on ZR360[56]7 based - MJPEG boards (DC10(+), LML33, Buz)

Special:

  png  PNG files output (use -z switch to set - compression)
pgmPGM files output (for testing purposes or ffmpeg encoding)
md5MD5sum output (for MPEG conformance tests)
nullNull output (for speed tests/benchmarking)
+ -

NOTE: check the following subsections for details and requirements!

+

2.3.1. Video output devices

2.3.1.1. Setting up MTRR

@@ -537,19 +441,19 @@ also help. Thanks!

- - - + + - - + + - + - - - + + +

There are several commandline switches for SDL:

  -vo sdl:name   -specifies sdl video driver to use (ie. aalib, dga, x11)
-ao sdl:namespecifies sdl audio driver to use (ie. dsp, +

There are several commandline switches for SDL:

  -vo sdl:name   +specifies sdl video driver to use (ie. aalib, dga, x11)
-ao sdl:namespecifies sdl audio driver to use (ie. dsp, esd, arts)
-noxvdisables Xvideo hardware acceleration
-forcexvtries to force Xvideo acceleration
-noxvdisables Xvideo hardware acceleration
-forcexvtries to force Xvideo acceleration

SDL Keys:

SDL Keys:

Ftoggles fullscreen/windowed mode
Ccycles available fullscreen modes
W/Smappings for * and / (mixer control)
Ftoggles fullscreen/windowed mode
Ccycles available fullscreen modes
W/Smappings for * and / (mixer control)

@@ -584,13 +488,13 @@ whatever. And don't forget to register your UniVBE ;))

The FBdev output takes some additional parameters above the others:

- - - - - - + + + + + +
  -fb   -specify the framebuffer device to use (/dev/fb0)
-fbmodemode name to use (according to /etc/fb.modes)
-fbmodeconfig config file of modes (default /etc/fb.modes)
-monitor_hfreqIMPORTANT values, see example.conf
-monitor_vfreq
-monitor_dotclock
  -fb   +specify the framebuffer device to use (/dev/fb0)
-fbmodemode name to use (according to /etc/fb.modes)
-fbmodeconfig config file of modes (default /etc/fb.modes)
-monitor_hfreqIMPORTANT values, see example.conf
-monitor_vfreq
-monitor_dotclock

If you want to change to a specific mode, then use

@@ -700,29 +604,29 @@ Quake, etc. MPlayer contains a very usable driver for it. If ./configure detects aalib installed, the aalib libvo driver will be built.

- - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - - - + + + +

You can use some keys in the AA Window to change rendering options:

  1  decrease contrast
2increase contrast
3decrease brightness
4increase brightness
5switch fast rendering on/off
6set dithering mode (none, error distribution, floyd steinberg)
7invert image
atoggles between aa and mplayer control)

The following command line options can be used:

-aaosdcolor=Vchange osd color
-aasubcolor=Vchange subtitle color

where V can be: (0/normal, 1/dark, 2/bold, 3/boldfont, 4/reverse, 5/special)

AAlib itselves provides a large sum of options. +

You can use some keys in the AA Window to change rendering options:

  1  decrease contrast
2increase contrast
3decrease brightness
4increase brightness
5switch fast rendering on/off
6set dithering mode (none, error distribution, floyd steinberg)
7invert image
atoggles between aa and mplayer control)

The following command line options can be used:

-aaosdcolor=Vchange osd color
-aasubcolor=Vchange subtitle color

where V can be: (0/normal, 1/dark, 2/bold, 3/boldfont, 4/reverse, 5/special)

AAlib itselves provides a large sum of options. Here are some important:

-aadriverset recommended aa driver (X11, curses, linux)
-aaextendeduse all 256 characters
-aaeightuse eight bit ascii
-aahelpprints out all aalib options
-aadriverset recommended aa driver (X11, curses, linux)
-aaextendeduse all 256 characters
-aaeightuse eight bit ascii
-aahelpprints out all aalib options

NOTE: the rendering is very CPU intensive, especially when using AA-on-X @@ -799,14 +703,14 @@ in vm86 mode).

- - - - - - - - + + + + + + + +

These switches of command line currently are available for VESA:

  -vo vesa:optscurrently recognized: dga to force dga mode and nodga to disable dga mode. Note: you may omit these parameters to enable autodetect of dga mode. (In the future also will specify mode parameters such as refresh rate, interlacing, doublescan and so on. Samples: i43, 85, d100)
-screenw, -screenh, -bppforce userdefined mode
-x, -yset userdefined prescaling
-zoomenables userdefined prescaling
-fsscales image to fullscreen
-fs -zoomscales userdefined prescaling to fullscreen
-doubleenables double buffering mode. (Available only in DGA mode). Should be slower of single buffering, but has no flickering effects.

These switches of command line currently are available for VESA:

  -vo vesa:optscurrently recognized: dga to force dga mode and nodga to disable dga mode. Note: you may omit these parameters to enable autodetect of dga mode. (In the future also will specify mode parameters such as refresh rate, interlacing, doublescan and so on. Samples: i43, 85, d100)
-screenw, -screenh, -bppforce userdefined mode
-x, -yset userdefined prescaling
-zoomenables userdefined prescaling
-fsscales image to fullscreen
-fs -zoomscales userdefined prescaling to fullscreen
-doubleenables double buffering mode. (Available only in DGA mode). Should be slower of single buffering, but has no flickering effects.

-- cgit v1.2.3