From 8613b3bb62f14d5eacece2c4793f744c3fefd876 Mon Sep 17 00:00:00 2001
From: gabucino
You may need to include log, configuration or sample files in your bug
report. If some of them are quite big then it is better to upload them to our
diff --git a/DOCS/codecs.html b/DOCS/codecs.html
index 17b2793a58..27e064f157 100644
--- a/DOCS/codecs.html
+++ b/DOCS/codecs.html
@@ -198,7 +198,7 @@
have filenames like these: vid_cvid.xa, vid_h263.xa, vid_iv50.xa
.
-
XAnim is video codec family xanim, so you may want to use the -vfm xanim
+
XAnim is video codec family xanim
, so you may want to use the -vfm xanim
option to tell MPlayer to use them if possible.
Tested codecs include: Indeo 3.2, 4.1, 5.0, CVID, diff --git a/DOCS/encoding.html b/DOCS/encoding.html index d6d9c7bb46..09167cb285 100644 --- a/DOCS/encoding.html +++ b/DOCS/encoding.html @@ -160,12 +160,12 @@
As a side-effect of fixing broken AVI files, MEncoder can be used to fix the - result of appending 2 (or more) AVI files:
+As a side-effect, the broken AVI fixer function enables MEncoder to append + 2 (or more) AVI files:
Command: cat 1.avi 2.avi | mencoder -noidx -ovc copy -oac copy -o output.avi -
Note: This expects 1.avi and 2.avi to use the same codecs, resolution, +
Note: This expects 1.avi
and 2.avi
to use the same codecs, resolution,
stream rate etc, and at least 1.avi must not be broken. You may need to fix
your input AVI files first, as described above.
-ao sdl
)[1]: the number of applications that are able to use the + device at the same time.
+Feedback to this document is welcome. Please tell us how MPlayer and your sound card(s) worked together.
diff --git a/DOCS/video.html b/DOCS/video.html index f64a69b1d3..69aaa1e7fa 100644 --- a/DOCS/video.html +++ b/DOCS/video.html @@ -220,13 +220,13 @@This section 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).
-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. @@ -253,7 +253,7 @@ driver that controls this chip. So it does not work on every system.
-First make sure X loads the DGA extension, see in /var/log/XFree86.0.log:
@@ -290,7 +290,7 @@ much faster. -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 time @@ -322,7 +322,7 @@ -
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 @@ -330,7 +330,7 @@ driver for MPlayer works.
-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 @@ -369,7 +369,7 @@ CPU time!) depending on the implementation of DGA for your hardware.
-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. @@ -394,7 +394,7 @@ CPUs might work at 400 MHZ and above.
-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 @@ -460,7 +460,7 @@
W/S
You'll have to install svgalib and its development package in order for MPlayer build its SVGAlib driver (autodetected, but can be forced), and don't forget to edit /etc/vga/libvga.config to suit your card & monitor.
-Be sure not to use the -fs option, since it toggles the usage of the software
scaler, and it's slow. If you really need it, use the -sws 4
option which will produce bad quality, but is somewhat faster.
SVGAlib incorporates EGAlib, and MPlayer has the possibility to display any movie in 16 colors, thus usable in the following sets:
@@ -725,7 +725,7 @@ (I guess that TV-out frequently is standalone head or standalone output at least.) -Don't use this driver with GCC 2.96! It won't work!
--vo vesa:opts
VIDIX is the abbreviation for VIDeo Interface for *niX. It was designed and introduced as an interface for fast user-space drivers @@ -835,7 +835,7 @@ team in graphics mode switching). I.e. main goal of this interface is to maximize the speed of video playback.
--vo xvidix
When VIDIX is used as subdevice (-vo vesa:vidix
) then
video mode configuration is performed by video output device
@@ -905,11 +905,12 @@ Indeed it doesn't matter which video output driver is used with VIDIX.
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.Then compile and install as usual.
-Hardware decoding (playing standard MPEG1/2 files) can be done with this command:
@@ -1087,7 +1088,7 @@ for 3:4 TV: -vop lavc,expand=-1:576:-1:-1:1,scale=-1:0,dvbscale for 16:9 TV: -vop lavc,expand=-1:576:-1:-1:1,scale=-1:0,dvbscale=1024 -If you have questions or want to hear feature announcements and take part in discussions on this subject, join our @@ -1117,7 +1118,7 @@ for 16:9 TV: -vop lavc,expand=-1:576:-1:-1:1,scale=-1:0,dvbscale=1024 Linux site. Configure should detect your card automatically, compilation should go without problems.
--vo dxr3:prebuf:sync:norm=x:<device>
overlay
activates the overlay instead of TVOut. It requires
@@ -1398,12 +1399,12 @@ for 16:9 TV: -vop lavc,expand=-1:576:-1:-1:1,scale=-1:0,dvbscale=1024
Currently ATI doesn't want to support any of its TV-out chips under Linux, because of their licensed Macrovision technology.
-