From 2c4e0598b694b153dc9cbd6172d771c07608aa39 Mon Sep 17 00:00:00 2001 From: diego Date: Sun, 4 Aug 2002 22:13:09 +0000 Subject: Changed all link names from the section number to a sensible label. Section numbers were 2.3.2.1. in the section names and 2.3.2.1 in the TOC. I settled for the former everywhere. "Misc OS" is now called "Ports". Checked all internal links, some of them were falsely pointing to renumbered sections. This should no longer happen. And in case some of you think "This must have been a lot of work!", that does not even begin to describe it... git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@6907 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/video.html | 99 +++++++++++++++++++++++++++++---------------------------- 1 file changed, 50 insertions(+), 49 deletions(-) (limited to 'DOCS/video.html') diff --git a/DOCS/video.html b/DOCS/video.html index 1cc4ccb8da..ac559d81d0 100644 --- a/DOCS/video.html +++ b/DOCS/video.html @@ -10,10 +10,10 @@ -

2.3.1.1 Setting up MTRR

It is VERY recommended to check if the MTRR registers are set up properly, because they can give a big performance boost.

@@ -71,7 +71,7 @@ ram (size=0x2000000) just execute:

stepping 0] doesn't support MTRR, but stepping 12's do ('cat /proc/cpuinfo' to check it').

2.3.1.2. Xv

2.3.1.2 Xv

Under XFree86 4.0.2 or newer, you can use your card's hardware YUV routines using the XVideo extension. This is what the option '-vo xv' uses. Also, @@ -129,20 +129,20 @@ usable with MPlayer.

2.3.1.2.1. 3dfx cards

2.3.1.2.1 3dfx cards

Older 3dfx drivers were known to have problems with XVideo acceleration, it didn't support either YUY2 or YV12, and so. Verify that you have XFree86 version 4.2.0 or greater, it works OK with YV12 and YUY2. Previous versions, including 4.1.0 crashes with YV12! 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.

+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 tdfxfb section!

2.3.1.2.2. S3 cards

2.3.1.2.2 S3 cards

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 @@ -155,7 +155,7 @@ it's faster", it's not sure. Try 2.3.1.2.3 nVidia cards

nVidia isn't a very good choice under Linux (according to nVidia, this is not true).. You'll have to use the @@ -170,7 +170,7 @@ GeForce 2 and 3.

Complain to nVidia.

2.3.1.2.4. ATI cards

2.3.1.2.4 ATI cards

The GATOS driver (which you @@ -182,11 +182,11 @@ n*(fps of the movie) Hz.
Radeon VE - currently only XFree86 CVS has driver for this card, version 4.1.0 doesn't. And no TV out support. Of course with MPlayer you can happily get accelerated display, with or without TV output, and -no libraries or X are needed. Read Vidix section.

VIDIX

2.3.1.2.5. NeoMagic cards

2.3.1.2.5 NeoMagic cards

These cards can be found in many laptops. Unfortunately, the driver in X 4.2.0 can't do Xv, but we have a modified, Xv-capable driver for you. @@ -205,22 +205,22 @@ EndSection

2.3.1.2.6. Trident cards

2.3.1.2.6 Trident cards

If you want to use xv with a trident card, provided that it doesn't work with 4.1.0, try the latest CVS of XFree or wait for XFree 4.2.0. The latest CVS adds support for fullscreen xv support with the Cyberblade XP card.

2.3.1.3. DGA

2.3.1.3 DGA

2.3.1.3.1. Summary

2.3.1.3.1 Summary

This document tries to explain in some words what DGA is in general and what the DGA video output driver for MPlayer can do (and what it can't).

2.3.1.3.2. What is DGA

2.3.1.3.2 What is DGA

DGA is short for Direct Graphics Access and is a means for a program to bypass the X-Server and directly modifying the framebuffer memory. @@ -247,7 +247,7 @@ graphics chip you use and on the implementation of the X server's video driver that controls this chip. So it does not work on every system ...

2.3.1.3.3. Installing DGA support for MPlayer

2.3.1.3.3 Installing DGA support for MPlayer

First make sure X loads the DGA extension, see in /var/log/XFree86.0.log:

@@ -283,7 +283,7 @@ privileges through SUID root MPlayer.
You should also try if the '-vo sdl:dga' option works for you! It's much faster!!!

2.3.1.3.4. Resolution switching

2.3.1.3.4 Resolution switching

The DGA driver allows for switching the resolution of the output signal. This avoids the need for doing (slow) software scaling and at the same @@ -298,14 +298,14 @@ out which modes survive with the X11 log file. It can be found at: /var/log/XFree86.0.log.

See appendix A for some sample modeline definitions.

2.3.1.3.5. DGA & MPlayer

2.3.1.3.5 DGA & MPlayer

DGA is used in two places with MPlayer: The SDL driver can be made to make use of it (-vo sdl:dga) and within the DGA driver (-vo dga). The above said is true for both; in the following sections I'll explain how the DGA driver for MPlayer works.

2.3.1.3.6. Features of the DGA driver

2.3.1.3.6 Features of the DGA driver

The DGA driver is invoked by specifying -vo dga at the command line. The default behavior is to switch to a resolution matching the original @@ -344,7 +344,7 @@ result in a big speed penalty (on my K6-II+ 525 it used an additional 20% of CPU time!) depending on the implementation of DGA for your hardware.

2.3.1.3.7. Speed issues

2.3.1.3.7 Speed issues

Generally spoken, DGA framebuffer access should be at least as fast as using the X11 driver with the additional benefit of getting a fullscreen image. @@ -367,7 +367,7 @@ only half the memory bandwidth of a 32 bit display.

I've seen some AVI files already be replayed on a Pentium MMX 266. AMD K6-2 CPUs might work at 400 MHZ and above.

2.3.1.3.8. Known bugs

2.3.1.3.8 Known bugs

Well, according to some developers of XFree, DGA is quite a beast. They tell you better not to use it. Its implementation is not always flawless @@ -388,7 +388,7 @@ case the DGA driver will crash telling you about a nonsense mode of

OSD only works with doublebuffering enabled.

2.3.1.3.9. Future work

2.3.1.3.9 Future work

use of the new X11 render interface for OSD

2.3.1.3.A. Some modelines

2.3.1.3.A Some modelines

   Section "Modes"
@@ -415,7 +415,7 @@ case the DGA driver will crash telling you about a nonsense mode of
 module.
 
 
-2.3.1.3.B. Bug Reports
+2.3.1.3.B Bug Reports
 
 If you experience troubles with the DGA driver please feel free to file
 a bug report to me (e-mail address below). Please start MPlayer with the
@@ -429,7 +429,7 @@ also help. Thanks!
 Acki (acki@acki-netz.de, www.acki-netz.de)
 
 
-2.3.1.4. SDL
+2.3.1.4 SDL
 
 SDL (Simple Directmedia Layer) is basically a unified video/audio
   interface. Programs that use it know only about SDL, and not about what video
@@ -476,7 +476,7 @@ esd, arts)
 It's bug in SDL, I can't change it (tested with SDL 1.2.1).
 
 
-
2.3.1.5. SVGAlib
+2.3.1.5 SVGAlib
 
 Installation

   You'll have to install svgalib and its development package in order for
@@ -510,7 +510,7 @@ It's bug in SDL, I can't change it (tested with SDL 1.2.1).
 
 
 
-2.3.1.6. Framebuffer output (FBdev)
+2.3.1.6 Framebuffer output (FBdev)
 
 Whether to build the FBdev target is autodetected during ./configure .
 Read the framebuffer documentation in the kernel sources
@@ -556,14 +556,14 @@ isn't supported. You can't use 8bpp (or less) modes.
 
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.
 
-2.3.1.7. Matrox framebuffer (mga_vid)
+2.3.1.7 Matrox framebuffer (mga_vid)
 
 This section is about the Matrox G200/G400/G450/G550 BES (Back-End Scaler)
 support, the mga_vid kernel driver.  It's active developed by me (A'rpi), and
 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:
@@ -608,7 +608,7 @@ you have matroxfb console, or '-vo xmga' under XFree86 3.x.x or 4.x.x.
   change : echo "brightness=120" > /dev/mga_vid
 
 
-2.3.1.8. SiS 6326 framebuffer (sis_vid)
+2.3.1.8 SiS 6326 framebuffer (sis_vid)
 
 SiS 6326 YUV Framebuffer driver -> sis_vid kernel driver
 
@@ -616,13 +616,13 @@ you have matroxfb console, or '-vo xmga' under XFree86 3.x.x or 4.x.x.
 updated after the mga_vid changes, so it's outdated now.  Volunteers
 needed to test it and bring the code up-to-date.
 
-2.3.1.9. 3dfx YUV support (tdfxfb)
+2.3.1.9 3dfx YUV support (tdfxfb)
 
 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 with
 ./configure --enable-tdfxfb
 
-2.3.1.10. OpenGL output
+2.3.1.10 OpenGL output
 
 MPlayer supports displaying movies using OpenGL, but if your
 platform/driver supports xv as should be the case on a PC with Linux, use xv
@@ -639,7 +639,7 @@ supports Rage128. See
 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,
@@ -687,7 +687,8 @@ That isn't autodetected by aalib, but vo_aa tries to find the best mode.
 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 a generic driver for any video
 card which has VESA VBE 2.0 compatible BIOS. Another advantage of this
@@ -726,7 +727,7 @@ at least.)
  - 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).

- - You can use Vidix with it, thus getting accelerated video display
+ - You can use VIDIX with it, thus getting accelerated video display
 AND TV output at the same time! (recommended for ATI cards)
 
 
@@ -768,7 +769,7 @@ 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
@@ -783,7 +784,7 @@ handy, but you need powerful CPU to use software scaling. Don't use the
 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
+It's very simple. See the DGA section's modelines, and
 insert them into your XF86Config.
 
   If you have XFree86 4.x.x - use the -vm option. It will
@@ -797,7 +798,7 @@ drivers can't use low pixelclocks that are needed for low resolution
 video modes.
 
 
-2.3.1.14. Vidix
+2.3.1.14 VIDIX
 
 WHAT IS VIDIX?
 
@@ -886,7 +887,7 @@ recognize :vidix subdevice.
 VIDEO EQUALIZER
 
 
-  This is a video equalizer implemented especially for Vidix. You can use
+  This is a video equalizer implemented especially for VIDIX. You can use
   it either with 1-8 keys as described in the man page, or
   by command line arguments. MPlayer recognizes the
   following options :
@@ -932,7 +933,7 @@ recognize :vidix subdevice.
 
 
 
-2.3.1.15. Zr
+2.3.1.15 Zr
 
 This is a display-driver (-vo zr) for a number of MJPEG
 capture/playback cards (tested for DC10+ and Buz, and it should work for the
@@ -965,7 +966,7 @@ Some remarks:
 
 
 
-2.3.1.16. DVB
+2.3.1.16 DVB
 
 MPlayer supports cards with the Siemens DVB chipset from vendors like
 Siemens, Technotrend, Galaxis or Hauppauge.  The latest DVB drivers are
@@ -1067,7 +1068,7 @@ non-25fps movies and realtime transcoding between MPEG2 and MPEG4 (partial
 decompression).
 
 
-2.3.1.17. DXR3
+2.3.1.17 DXR3
 
 MPlayer supports hardware accelerated playback with the Creative DXR3
 and Sigma Designs Hollywood Plus cards.
@@ -1133,9 +1134,9 @@ a second or two. At this time, the only workaround is to use
 -vc mpeg12 when viewing DVDs with subtitles.
 
 
-
2.3.1.A. TV-out support
+2.3.1.A TV-out support
 
-2.3.1.A.1. Matrox G400 cards
+2.3.1.A.1 Matrox G400 cards
 
 Under Linux you have 2 methods to get G400 TV out working :
 
@@ -1205,7 +1206,7 @@ a second or two. At this time, the only workaround is to use
 
 
 
-2.3.1.A.2. ATI cards
+2.3.1.A.2 ATI cards
 
 
 PREAMBLE

@@ -1218,13 +1219,13 @@ 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
+Check VESA driver and VIDIX
 sections.
 
 
 
-  On other cards, just use the VESA driver, without
-  Vidix. Powerful CPU is needed, though.
+  On other cards, just use the VESA driver, without
+  VIDIX. Powerful CPU is needed, though.
 
 
 Only thing you need to do - have TV connector plugged in before
@@ -1233,7 +1234,7 @@ sections.
 

 
 
-2.3.1.A.3. Voodoo 3
+2.3.1.A.3 Voodoo 3
 
 
 Check this URL.
-- 
cgit v1.2.3