From 4d3acbafa39309d2128411545bd6f8bece783cd1 Mon Sep 17 00:00:00 2001 From: torinthiel Date: Mon, 13 Nov 2006 10:47:38 +0000 Subject: [cosmetics] - fix end-tag not being in the same column as start-tag - some more indentation fixes - blank lines added/removed for consistency and visual markup - visual separation of sect* tags git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@20878 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/xml/en/video.xml | 274 +++++++++++++++++++++++++++++++------------------- 1 file changed, 170 insertions(+), 104 deletions(-) (limited to 'DOCS/xml/en/video.xml') diff --git a/DOCS/xml/en/video.xml b/DOCS/xml/en/video.xml index 3ca42856b9..b047b05a20 100644 --- a/DOCS/xml/en/video.xml +++ b/DOCS/xml/en/video.xml @@ -35,8 +35,8 @@ base address. You have 3 ways to find it: (--) SVGA: PCI: Matrox MGA G400 AGP rev 4, Memory @ 0xd8000000, 0xd4000000 (--) SVGA: Linear framebuffer at 0xD8000000 - + --> + from /proc/pci (use lspci -v command): @@ -44,11 +44,11 @@ base address. You have 3 ways to find it: 01:00.0 VGA compatible controller: Matrox Graphics, Inc.: Unknown device 0525 Memory at d8000000 (32-bit, prefetchable) - + from mga_vid kernel driver messages (use dmesg): mga_mem_base = d8000000 - + @@ -85,8 +85,13 @@ stepping 0) CPUs don't have MTRRs, but stepping 12 does + + + + Video outputs for traditional video cards + Xv @@ -104,10 +109,10 @@ In order to make this work, be sure to check the following: You have to use XFree86 4.0.2 or newer (former versions don't have XVideo) - + Your card actually supports hardware acceleration (modern cards do) - + X loads the XVideo extension, it's something like this: (II) Loading extension XVideo @@ -117,7 +122,7 @@ In order to make this work, be sure to check the following: always loaded, and doesn't mean that the card's XVideo support is loaded! - + Your card has Xv support under Linux. To check, try xvinfo, it is the part of the XFree86 distribution. It @@ -149,7 +154,7 @@ screen #0 --> It must support YUY2 packed, and YV12 planar pixel formats to be usable with MPlayer. - + And finally, check if MPlayer was compiled with 'xv' support. Do a mplayer -vo help | grep xv . @@ -157,10 +162,11 @@ screen #0 xv X11/Xv - + + 3dfx cards @@ -190,6 +196,7 @@ S3 Savage3D's should work fine, but for Savage4, use XFree86 version 4.0.3 or greater (in case of image problems, try 16bpp). As for S3 Virge: there is xv support, but the card itself is very slow, so you better sell it. + There is now a native framebuffer driver for S3 Virge cards similiar to tdfxfb. Set up your framebuffer (e.g. append @@ -288,6 +295,7 @@ EndSection SVGAlib @@ -657,7 +664,8 @@ somewhat faster. -EGA (4BPP) SUPPORT + +EGA (4BPP) SUPPORT SVGAlib incorporates EGAlib, and MPlayer has the possibility to display any movie in 16 colors, thus usable in the following @@ -668,10 +676,10 @@ sets: EGA card with EGA monitor: 320x200x4bpp, 640x200x4bpp, 640x350x4bpp - + EGA card with CGA monitor: 320x200x4bpp, 640x200x4bpp - + @@ -710,6 +718,7 @@ filter, see the man page for exact parameters. + Framebuffer output (FBdev) @@ -738,19 +747,19 @@ The FBdev output takes some additional parameters above the others: specify the framebuffer device to use (default: /dev/fb0) - + mode name to use (according to /etc/fb.modes) - + config file of modes (default: /etc/fb.modes) - + @@ -759,7 +768,7 @@ The FBdev output takes some additional parameters above the others: important values, see example.conf - + @@ -779,11 +788,11 @@ mplayer -vm -fbmode name_of_mode filenam format matches the video mode's pixel format. Pay attention to the bpp value, fbdev driver tries to use the current, or if you specify the option, then that. - + option isn't supported (use ). You can't use 8bpp (or less) modes. - + You possibly want to turn the cursor off: echo -e '\033[?25l' @@ -795,7 +804,7 @@ mplayer -vm -fbmode name_of_mode filenam echo -e '\033[?25h' or setterm -cursor on - + @@ -807,6 +816,7 @@ framebuffer, and don't ask for it, since it's not an + Matrox framebuffer (mga_vid) @@ -833,13 +843,13 @@ This is Linux only! On non-Linux (tested on FreeBSD) systems, you can use cd drivers make - + Then create /dev/mga_vid device: mknod /dev/mga_vid c 178 0 and load the driver with insmod mga_vid.o - + You should verify the memory size detection using the dmesg command. If it's bad, use the @@ -847,7 +857,7 @@ make 3Dfx YUV support + This driver uses the kernel's tdfx framebuffer driver to play movies with YUV acceleration. You'll need a kernel with tdfxfb support, and recompile @@ -895,6 +907,7 @@ with + OpenGL output @@ -930,9 +943,9 @@ least on nVidia): export __GL_SYNC_TO_VBLANK=1 - + AAlib - text mode displaying @@ -957,28 +970,28 @@ You can use some keys in the AA Window to change rendering options: 1 decrease contrast - + 2 increase contrast - + 3 decrease brightness - + 4 increase brightness - + 5 switch fast rendering on/off - + 6 set dithering mode (none, error distribution, Floyd Steinberg) - + 7 invert image - + 8 toggles between aa and MPlayer control - + @@ -989,7 +1002,7 @@ You can use some keys in the AA Window to change rendering options: change OSD color - + @@ -1003,7 +1016,7 @@ You can use some keys in the AA Window to change rendering options: 3 (bold font), 4 (reverse), 5 (special). - + @@ -1014,25 +1027,25 @@ important: Set recommended aa driver (X11, curses, Linux). - + Use all 256 characters. - + Use eight bit ASCII. - + Prints out all aalib options. - + @@ -1062,6 +1075,7 @@ tuning issues. + <systemitem class="library">libcaca</systemitem> - Color ASCII Art library @@ -1089,10 +1103,10 @@ will be built. the following: 16 available colors for character output (256 color pairs) - + color image dithering - + @@ -1100,7 +1114,7 @@ will be built. following limitations: no support for brightness, contrast, gamma - + @@ -1115,13 +1129,13 @@ You can use some keys in the caca window to change rendering options: d Toggle libcaca dithering methods. - + a Toggle libcaca antialiasing. - + b Toggle libcaca background. - + @@ -1132,19 +1146,19 @@ You can use some keys in the caca window to change rendering options: Set recommended caca driver. e.g. ncurses, slang, x11. - + Specifies the number of rows and columns. e.g. 128x50. - + Specifies the font to use. e.g. fixed, nexus. - + @@ -1155,6 +1169,7 @@ enough to render all frames. + VESA - output to VESA BIOS @@ -1197,22 +1212,22 @@ at least.) 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 (actually in vm86 mode). - + You can use VIDIX with it, thus getting accelerated video display and TV output at the same time! @@ -1224,20 +1239,20 @@ at least.) (config file, or command line) you will get the highest possible refresh rate. (Using General Timing Formula). To enable this feature you have to specify all your monitor options. - + DISADVANTAGES It works only on x86 systems. - + It can be used only by root. - + Currently it's available only for Linux. - + @@ -1257,7 +1272,7 @@ It won't work! double buffering via the option. Note: you may omit these parameters to enable autodetection of dga mode. - + @@ -1272,28 +1287,29 @@ It won't work! utility from the Mandrake/Mandriva distribution for example. (Hint: The same utility is used for localization of 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+F<x>) 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. - + + X11 @@ -1323,7 +1339,7 @@ modelines, and insert them into your XF86Config. If you have XFree86 4.x.x: use the option. It will change to a resolution your movie fits in. If it doesn't: - + With XFree86 3.x.x: you have to cycle through available resolutions with the @@ -1331,7 +1347,7 @@ modelines, and insert them into your XF86Config. and Ctrl+Alt+minus keys. - + @@ -1342,6 +1358,7 @@ video modes. + VIDIX @@ -1378,8 +1395,9 @@ main goal of this interface is to maximize the speed of video playback. in the device section. You should set this to the amount of memory installed on your card minus 4MB. If you have less than 8MB of video ram, you can use the option "XaaNoPixmapCache" in the screen section instead. - - + + + There is a console VIDIX driver: . 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 @@ -1397,13 +1415,14 @@ main goal of this interface is to maximize the speed of video playback. On the other hand, should give you a video running in the "background", though this depends on the colorkey functionality to work right. - + + You can use VIDIX subdevice which was applied to several video output drivers, such as: (Linux only) and . - + @@ -1416,12 +1435,12 @@ Indeed it doesn't matter which video output driver is used with Video card should be in graphics mode (except nVidia cards with the output driver). - + MPlayer's video output driver should know active video mode and be able to tell to VIDIX subdevice some video characteristics of server. - + @@ -1437,14 +1456,13 @@ least for ATI's card). As for , currently it recognizes the following options: . + Also you can specify VIDIX's driver directly as third subargument in command line: - mplayer -vo xvidix:mga_vid.so -fs -zoom -double file.avi or mplayer -vo vesa:vidix:radeon_vid.so -fs -zoom -double -bpp 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 computer). You should do that @@ -1468,33 +1486,35 @@ Alternatively, you can use a special kernel module, like this: download a version made by Alex especially for usage with MPlayer (it doesn't need the svgalib source to compile) from here. - + Compile the module in the svgalib_helper directory (it can be found inside the svgalib-1.9.17/kernel/ directory if you've downloaded the source from the svgalib site) and insmod it. - + To create the necessary devices in the /dev directory, do a make device in the svgalib_helper dir, as root. - + Move the svgalib_helper directory to mplayer/main/libdha/svgalib_helper. - + Required if you download the source from the svgalib site: Remove the comment before the CFLAGS line containing "svgalib_helper" string from the libdha/Makefile. - + Recompile and install libdha. - + + ATI cards + Currently most ATI cards are supported natively, from Mach64 to the newest Radeons. @@ -1507,8 +1527,10 @@ the VIDIX system autoprobe all available drivers. + Matrox cards + Matrox G200, G400, G450 and G550 have been reported to work. @@ -1519,8 +1541,10 @@ The driver supports video equalizers and should be nearly as fast as the + Trident cards + There is a driver available for the Trident Cyberblade/i1 chipset, which can be found on VIA Epia motherboards. @@ -1532,14 +1556,17 @@ The driver was written and is maintained by + 3DLabs cards + Although there is a driver for the 3DLabs GLINT R3 and Permedia3 chips, no one has tested it, so reports are welcome. + nVidia cards @@ -1550,11 +1577,12 @@ has tested it, so reports are welcome. video output, as the following example shows: mplayer -vo cvidix example.avi - + SiS cards + This is very experimental code, just like nvidia_vid. @@ -1570,8 +1598,11 @@ Reports awaited! + + DirectFB +
"DirectFB is a graphics library which was designed with embedded systems in mind. It offers maximum hardware accelerated performance at a minimum @@ -1595,8 +1626,11 @@ be done by the subdevice method, e.g.: + + DirectFB/Matrox (dfbmga) + Please read the main DirectFB section for general information. @@ -1626,11 +1660,16 @@ patch from the URL above). Porting the CRTC2 code to + + + + MPEG decoders DVB output and input + MPlayer supports cards with the Siemens DVB chipset from vendors like Siemens, Technotrend, Galaxis or Hauppauge. The latest DVB @@ -1878,8 +1917,11 @@ decompression). + + DXR2 + MPlayer supports hardware accelerated playback with the Creative DXR2 card. @@ -1918,8 +1960,11 @@ the colorkey settings you should be able to get acceptable results. Please see the man page for available options. + + DXR3/Hollywood+ + MPlayer supports hardware accelerated playback with the Creative DXR3 and Sigma Designs Hollywood Plus cards. These cards @@ -2038,9 +2083,12 @@ it must be used to specify the DXR3's output instead of a sound card. - + + + + Other visualization hardware @@ -2139,8 +2187,11 @@ to finish and THEN stop XawTV. + + Blinkenlights + This driver is capable of playback using the Blinkenlights UDP protocol. If you don't know what Blinkenlights @@ -2156,6 +2207,10 @@ action at 00:07:50. + + + + TV-out support @@ -2190,11 +2245,12 @@ for Matrox G450/G550 TV-out instructions, please see the next section! and has Macrovision copy protection enabled (you can "workaround" Macrovision using this perl script). - + Framebuffer - + + Using the matroxfb modules in the 2.4 kernels. 2.2 kernels don't have the TVout feature in them, thus unusable for this. You have to enable ALL matroxfb-specific feature during compilation @@ -2208,23 +2264,23 @@ for Matrox G450/G550 TV-out instructions, please see the next section! ./compile.sh. Install TVout/matroxset/matroxset somewhere into your PATH. - + If you don't have fbset installed, put TVout/fbset/fbset somewhere into your PATH. - + If you don't have con2fb installed, put TVout/con2fb/con2fb somewhere into your PATH. - + Then enter into the TVout/ directory in the MPlayer source, and execute ./modules as root. Your text-mode console will enter into framebuffer mode (no way back!). - + Next, EDIT and run the ./matroxtv script. This will present you to a very simple menu. Press 2 and @@ -2233,7 +2289,7 @@ for Matrox G450/G550 TV-out instructions, please see the next section! picture has some weird stripes on it, the script wasn't able to set the resolution correctly (to 640x512 by default). Try other resolutions from the menu and/or experiment with fbset. - + Yoh. Next task is to make the cursor on tty1 (or whatever) to disappear, and turn off screen blanking. Execute the following @@ -2253,7 +2309,7 @@ setterm -blank 0 + Matrox G450/G550 cards + TV output support for these cards has only been recently introduced, and is not yet in the mainstream kernel. Currently the mga_vid @@ -2327,6 +2386,7 @@ The necessary kernel patch and the detailed HOWTO is downloadable from + ATI cards @@ -2344,21 +2404,21 @@ because of their licensed Macrovision technology. ATI Mach64: supported by GATOS. - + ASIC Radeon VIVO: supported by GATOS. - + Radeon and Rage128: supported by MPlayer! Check VESA driver and VIDIX sections. - + Rage Mobility P/M, Radeon, Rage 128, Mobility M3/M4: supported by atitvout. - + @@ -2373,9 +2433,11 @@ itself only once during POST procedure. + nVidia + First, you MUST download the closed-source drivers from . I will not describe the installation and configuration process because it does not cover @@ -2412,8 +2474,11 @@ Of course the important thing is the TwinView part. + + NeoMagic + The NeoMagic chip is found in a variety of laptops, some of them are equipped with a simple analog TV encoder, some have a more advanced one. @@ -2438,8 +2503,9 @@ with a simple analog TV encoder, some have a more advanced one. half your laptop's LCD screen. To switch to TV hit Fn+F5 three times. Tested on a Tecra 8000, 2.6.15 kernel with vesafb, ALSA v1.0.10. - - + + + Chrontel 70xx encoder chip: Found in IBM Thinkpad 390E and possibly other Thinkpads or notebooks. -- cgit v1.2.3