# HG changeset patch # User diego # Date 1024161141 0 # Node ID d0d74f9d8d4a60171b3dd8155525e22519e7f48e # Parent 80fe8f43616be2bbdd5686894030ab6db36438b9 Background now set by CSS, added doctype and charset. Properly closed all tags, removed bogus

-tags around block elements and put

outside , the other way around is incorrect. Fixed some typos, uppercased all tags, removed some -tags for better readability on the screen. diff -r 80fe8f43616b -r d0d74f9d8d4a DOCS/video.html --- a/DOCS/video.html Sat Jun 15 10:08:33 2002 +0000 +++ b/DOCS/video.html Sat Jun 15 17:12:21 2002 +0000 @@ -1,10 +1,12 @@ + + - +

2.3.1. Video output devices

@@ -30,7 +32,7 @@ address. You have 3 ways to find it:

-

Then let's find the memory size. This is very easy, just convert video ram size to hexadecimal, or use this table:

- - - - - - + + + + + +
  1 MB0x100000
2 MB0x200000
4 MB0x400000
8 MB0x800000
16 MB0x1000000
32 MB0x2000000
  1 MB0x100000
2 MB0x200000
4 MB0x400000
8 MB0x800000
16 MB0x1000000
32 MB0x2000000
@@ -74,12 +76,12 @@ using the XVideo extension. This is what the option '-vo xv' uses. Also, this is driver supports adjusting brightness/contrast/hue/etc (unless you use the old, slow DirectShow DivX codec, which supports it everywhere), see the -manpage.

+man page.

In order to make this work, be sure to check the following:

-

2.3.1.2.1. 3dfx cards

@@ -134,7 +137,7 @@ If you experience strange effects using -vo xv, try SDL (it has XVideo too) and see if it helps. Check the SDL section for details.

-

OR, try the NEW -vo tdfxfb driver! See the 2.3.1.9 +

OR, try the NEW -vo tdfxfb driver! See the 2.3.1.9 section!

@@ -162,13 +165,13 @@

As far as I know the latest XFree86 driver contains XVideo support for Geforce 2 and 3.

-

+

Riva128 cards don't have XVideo support even with the nvidia driver :( +Complain to NVidia.

2.3.1.2.4. ATI cards

-

+

2.3.1.2.5. NeoMagic cards

@@ -333,7 +335,7 @@ In the meantime the other buffer in memory will be filled again with new video data.

-Doublebuffering may be switched on by using the option -double and may be +

Doublebuffering may be switched on by using the option -double and may be disabled with -nodouble. Current default option is to disable doublebuffering. When using the DGA driver, onscreen display (OSD) only works with doublebuffering enabled. However, enabling doublebuffering may @@ -370,25 +372,27 @@ tell you better not to use it. Its implementation is not always flawless with every chipset driver for XFree out there.

-

2.3.1.3.9. Future work

-

+

2.3.1.3.A. Some modelines

@@ -449,27 +453,27 @@ -

- - - - - +

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
+ + + + + - + - - - + + + -

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

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)

+

KNOWN BUGS:

-

2.3.1.5. SVGAlib

@@ -496,21 +500,22 @@

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

    mplayer -vm -fbmode (NameOfMode) filename

-

NOTE: FBdev video mode changing _does not work_ with the VESA framebuffer, and don't ask for it, since it's not an MPlayer limitation.

@@ -534,7 +539,7 @@ it has hardware VSYNC support with triple buffering. It works on both framebuffer console and under X.

-

WARNING: on non-Linux systems, use Vidix for +

WARNING: on non-Linux systems, use Vidix for mga_vid !!!

To use it, you first have to compile mga_vid.o:

@@ -610,38 +615,38 @@ http://dri.sourceforge.net for download and installation instructions.

-

2.3.1.11. AAlib - text mode displaying

+

2.3.1.11. AAlib - text mode displaying

AAlib is a library for displaying graphics in text mode, using powerful ASCII renderer. There are LOTS of programs already supporting it, like Doom, 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)
+ + + + + + + + + - + - - - + + + - + - - - - -

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:

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)

-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:

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 (using aalib on X), and it's least CPU intensive on standard, @@ -657,18 +662,17 @@ See http://aa-project.sourceforge.net/tune/ for further tuning issues.

-

2.3.1.12. VESA - output to VESA BIOS

+

2.3.1.12. VESA - output to VESA BIOS

-This driver was designed and introduced as generic driver for any video +This driver was designed and introduced as generic driver for any video card which has VESA VBE 2.0 compatible BIOS. But exists still one reason of developing of this driver - it's multiple troubles with displaying movie on TV.
-VESA BIOS EXTENSION (VBE) Version 3.0 Date: September 16, 1998 (Page 70) +VESA BIOS EXTENSION (VBE) Version 3.0 Date: September 16, 1998 (Page 70) says:

-

- -Dual-Controller Designs
+

+Dual-Controller Designs
VBE 3.0 supports the dual-controller design by assuming that since both controllers are typically provided by the same OEM, under control of a single BIOS ROM on the same graphics card, it is possible to hide the fact @@ -679,74 +683,71 @@ information of both controllers, including the combined list of available modes. When the application selects a mode, the appropriate controller is activated. Each of the remaining VBE functions then operates on the active controller. -
-

+

-So you have chances to get working TV-out by using this driver.
+So you have chances to get working TV-out by using this driver.
(I guess that TV-out frequently is standalone head or standalone output at least.)

-What are pluses:
- - You have chances to watch movies if Linux even doesn't know your video hardware.
+What are pluses:
+ - You have chances to watch movies if Linux even doesn't know your video hardware.
- You don't need to have installed any graphics' related things on your Linux (like X11 (aka XFree86), fbdev and so on). This driver can be run from -text-mode.
- - You have chances to get working TV-out. (It's known at least for ATI's cards).
- - This driver calls int 10h handler thus it's not an emulator - it -calls real things of real BIOS in real-mode. (Finely - +text-mode.
+ - You have chances to get working TV-out. (It's known at least for ATI's cards).
+ - This driver calls int 10h handler thus it's not an emulator - it +calls real things of real BIOS in real-mode. (Finely - in vm86 mode).
- - Most important :) You can watch DVD at 320x200 if you don't have a powerful CPU.
+ - Most important :) You can watch DVD at 320x200 if you don't have a powerful CPU.

-What are minuses:
- - It works only on x86 systems.
- - It's the slowest driver from all the available ones for MPlayer.
- (But only if your card doesn't support DGA mode - otherwise this - driver is comparable by speed with -vo dga and -vo fbdev ones.
+What are minuses:
+ - It works only on x86 systems.
+ - It's the slowest driver from all the available ones for MPlayer.
+ (But only if your card doesn't support DGA mode - otherwise this + driver is comparable by speed with -vo dga and -vo fbdev ones.
- - It can be used only by ROOT.
- - Currently it's available only for Linux.
- - It doesn't use any hardware accelerations (like YUV overlay or hw scaling).
+ - It can be used only by ROOT.
+ - Currently it's available only for Linux.
+ - It doesn't use any hardware accelerations (like YUV overlay or hw scaling).

Don't use this driver with GCC 2.96 ! It won't work !

-

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

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.
-

-Known problems and workaround:
- - If you have installed NLS font on your Linux box and run VESA driver -from text-mode then after terminating mplayer you will have ROM font loaded instead -of national. You can load national font again by using setsysfont utility -from for example Mandrake distribution.
-(Hint: The same utility is used for localizating fbdev).
- - Some Linux graphics drivers don't update active BIOS mode in DOS memory. So if you have such -problem - always use VESA driver only from text-mode. Otherwise text-mode (#03) will be -activated anyway and you will need restart your computer.
- - Often after terminating VESA driver you get black screen. To return your screen -to original state - simply switch to other console (by pressing Alt-Fx) then switch -to your previous console by the same way.
- - To get working TV-out you need have plugged tv-connector in before booting +Known problems and workaround:
+ - If you have installed NLS font on your Linux box and run VESA driver +from text-mode then after terminating mplayer you will have ROM font loaded instead +of national. You can load national font again by using setsysfont utility +from for example Mandrake distribution.
+(Hint: The same utility is used for localizating fbdev).
+ - Some Linux graphics drivers don't update active BIOS mode in DOS memory. So if you have such +problem - always use VESA driver only from text-mode. Otherwise text-mode (#03) will be +activated anyway and you will need restart your computer.
+ - Often after terminating VESA driver you get black screen. To return your screen +to original state - simply switch to other console (by pressing Alt-Fx) then switch +to your previous console by the same way.
+ - To get working TV-out you need have plugged tv-connector in before booting your PC since video BIOS initializes itself only once during POST procedure.

-

2.3.1.13. X11

+

2.3.1.13. X11

Avoid if possible. Outputs to X11 (uses shared memory extension), with no hardware acceleration at all. Supports (MMX/3DNow/SSE accelerated, but still @@ -761,8 +762,8 @@ SDL driver's software output+scaler, it has worse image quality !

Software scaling is very slow, you better try changing video modes instead. -It's very simple. See the DGA section's modelines, and -insert them into your XF86Config. +It's very simple. See the DGA section's modelines, and +insert them into your XF86Config.

-If you can't find the modes you inserted, browse XFree86's output. Some +

If you can't find the modes you inserted, browse XFree86's output. Some drivers can't use low pixelclocks that are needed for low resolution video modes.

@@ -782,27 +783,29 @@

2.3.1.15. VIDIX

-

WHAT IS VIDIX

+

WHAT IS VIDIX?

-

VIDIX is the abbreviation for VIDeo Interface for - *niX.
+

VIDIX is the abbreviation for VIDeo Interface for + *niX.
VIDIX was designed and introduced as an interface for fast user-space drivers - providing DGA everywhere where it's possible (unlike X11). I - hope that these drivers will be as portable as X11 (not only on - *nix).
- What is it: + providing DGA everywhere where it's possible (unlike X11). I + hope that these drivers will be as portable as X11 (not only on + *nix).
+ What it is:

+ +

I can tell you in bold capital letters :
- VIDIX PROVIDES DIRECT GRAPHICS ACCESS TO BES YUV MEMORY. + VIDIX PROVIDES DIRECT GRAPHICS ACCESS TO BES YUV MEMORY.

-

Well (it's in my todo) - implement DGA to MPEG2 decoder.

+

Well (it's in my todo) - implement DGA to MPEG2 decoder.

This interface was designed as an attempt to fit existing video acceleration interfaces (known as mga_vid, mga_yuv, radeon_vid) into a fixed scheme. It @@ -817,37 +820,37 @@ the future, if some number of volunteers will be found.

-

USAGE

+

USAGE

-

+

+Indeed it doesn't matter which video output driver is used with VIDIX. -

REQUIREMENTS

+

REQUIREMENTS

-

-

  • video card should be in graphics mode (I write should simply + +I hope that probably every video output driver of MPlayer will +recognize :vidix subdevice. -

    USAGE METHODS

    +

    USAGE METHODS

    -

    When VIDIX is used as subdevice (-vo vesa:vidix) then +

    When VIDIX is used as subdevice (-vo vesa:vidix) then video mode configuration is performed by video output device - (vo_server in short). Therefore you can pass into command line of + (vo_server in short). Therefore you can pass into command line of MPlayer the same keys as for vo_server. In addition it understands -double key as globally visible parameter. (I recommend using this key with VIDIX at least for ATI's card).
    @@ -865,7 +868,7 @@ 32 file.avi

    But it's dangerous, and you shouldn't do that. In this case given driver will - be forced and result is unpredictable (it may freeze your + be forced and result is unpredictable (it may freeze your computer). You should do that ONLY if you are absolutely sure it will work, and MPlayer doesn't do it automatically. Please tell about it to the developers. The Right Way is to use VIDIX without arguments to enable driver @@ -879,16 +882,16 @@ where X11 does.

    -

    And the last WARNING: (un)fortunately you MUST have - ROOT privileges to use VIDIX due to direct hardware access. At least - set the suid bit on the MPlayer excecutable. +

    And the last WARNING: (un)fortunately you MUST have + ROOT privileges to use VIDIX due to direct hardware access. At least + set the suid bit on the MPlayer excecutable.

    -

    VIDEO EQUALIZER

    +

    VIDEO EQUALIZER

    This is a video equalizer implemented especially for Vidix. You can use - it either with 1-8 keys as described in the manpage, or + it either with 1-8 keys as described in the man page, or by command line arguments. MPlayer recognizes the following options :

    @@ -942,7 +945,7 @@ you must get it working first. Then recompile MPlayer with --enable-zr.

    -

    Some remarks: +Some remarks:

    -

    @@ -972,7 +974,6 @@

    IMPORTANT: Only Matrox G400DH/G400MAX has TV-out support under Linux, others (G450, G550) has NOT!

    -

    -

    2.3.1.A.2. ATI cards

    -A few word about ATI's TV-out:
    +A few word about ATI's TV-out:
    Currently ATI doesn't want to support any of its TV-out chips under Linux. Below is official answer from ATI Inc.:

    - -
    > Hello! -
    > -
    > On your pages you wrote that you support linux developers. -
    > Currently I participate with mplayer project (www.mplayerhq.hu) -
    > I'm interesting with enabling TV-out on Radeon VE chips during -
    > movie playback. I would be glad to add this feature to radeonfb driver -
    > (which can be found in CVS tree of mplayer project at main/drivers/radeon). -
    > Do I have a chance to get any official technical documenation? -
    -
    We will not provide TV out related documents due to macrovision concerns. -
    Also mpeg2 decoding is something that we MAY consider in the future but not -
    at this current time. This is again due to proprietary and 3rd party -
    information. + +
    > Hello! +
    > +
    > On your pages you wrote that you support linux developers. +
    > Currently I participate with mplayer project (www.mplayerhq.hu) +
    > I'm interesting with enabling TV-out on Radeon VE chips during +
    > movie playback. I would be glad to add this feature to radeonfb driver +
    > (which can be found in CVS tree of mplayer project at main/drivers/radeon). +
    > Do I have a chance to get any official technical documenation? +
    +
    We will not provide TV out related documents due to macrovision concerns. +
    Also mpeg2 decoding is something that we MAY consider in the future but not +
    at this current time. This is again due to proprietary and 3rd party +
    information.

    @@ -1077,38 +1076,40 @@ hackers will be able to disable copy protection on their chips. Therefore we have no chance to get working TV-out on ATI.

    -

    What's status of ATI's tv-out chips under Linux: -

  • ATI Mach64 has ImpacTV which is supported by gatos. -
  • ASIC Radeon VIVO has Rage Theatre which is supported by gatos. -
  • Radeon VE and Rage PRO LT have ImpacTV2+ which is not supported under Linux. +What's status of ATI's tv-out chips under Linux: +

    -Fortunately, owners of fast enough CPUs (Duron, Celeron2 and better) can watch -movies on their TV through VESA drivers. +Fortunately, owners of fast enough CPUs (Duron, Celeron2 and better) can watch +movies on their TV through VESA drivers.

    -I should say good words to ATI Inc. too:
    -they produce top quality BIOSes. +I should say good words to ATI Inc. too:
    +they produce top quality BIOSes.

    -VESA drivers don't use any hardware acceleration but it simulates -DGA through 64K window, which is configured through 32-bit mode -functions of BIOS. ATI cards have enough fast video memory (DIMM or DDR +VESA drivers don't use any hardware acceleration but it simulates +DGA through 64K window, which is configured through 32-bit mode +functions of BIOS. ATI cards have enough fast video memory (DIMM or DDR chips with 64 - 128-bit access) so it's not bottleneck for them. There are no limitations on which video mode can be displayed on your TV (like on other -cards) so you can use any video mode on your TV (from -320x200 up to 1024x768).
    -From other side (it's known at least for Radeons) there is DGA +cards) so you can use any video mode on your TV (from +320x200 up to 1024x768).
    +From other side (it's known at least for Radeons) there is DGA mode which is detected automatically and in this case you'll get comparable -with -vo dga and -vo fbdev drivers speed.
    -Only thing you need to do - have TV connector plugged in before booting your -PC since video BIOS initializes itself only once during POST procedure. +with -vo dga and -vo fbdev drivers speed.
    +Only thing you need to do - have TV connector plugged in before booting your +PC since video BIOS initializes itself only once during POST procedure.