MPlayer can play Vivo (1.0 and 2.0) videos. The most suitable codec
-for this task is XAnim's H263 decoder codec (it supports fast YV12 output), you
-can call it with the -vc h263xa option. Of course you have to
-compile XAnim codecs support it, for details see the XAnim
-video codecs. If this doesn't work, get the ivvideo.dll DLL
-file (from here),
+for 1.0 files is FFmpeg's H263 decoder, you can use it with the -vc
+ffh263 option (you'll need the newest libavcodec !). For 2.0 files, use
+XAnim's H263 decoder codec (it supports fast YV12 output). You can call it with
+the -vc h263xa option. Of course you have to compile XAnim codecs
+support in, for details see the XAnim video codecs. If
+this doesn't work, get the ivvideo.dll DLL file (from here),
and install it under /usr/lib/win32 or wherever you store the
Win32 codecs. This latter codec doesn't support YV12 nor YUY2 only BGR modes,
thus usable only with the X11 and OpenGL outputs. Discouraged.
ALWAYS browse the output of ./configure , it contains info -about what will be built, and what won't. You may also want to view -config.h and config.mak files.
+ALWAYS browse the output of ./configure, and the
+configure.log file, they contain info about what will be built,
+and what won't. You may also want to view config.h and config.mak files.
Though not mandatory, the fonts should be installed in order to gain OSD, and subtitle functionality. Download mp-arial-iso-8859-*.zip and/or optional @@ -570,13 +569,6 @@
If everything went fine, MPlayer will print a message like LIRC init was successful. -on startup. If an error occurs it will tell you. If it doens't tell you +on startup. If an error occurs it will tell you. If it doesn't tell you anything about LIRC there's no support compiled in. That's it :-)
The application name for MPlayer is - oh wonder - mplayer_lirc. @@ -886,6 +878,13 @@ Anyone has closer info?
+ + +Works. Only has -vo x11 output which is even much slower
+than on Linux, since QNX has only X emulation which is VERY slow.
+No closer info yet.
NOTE: Do *NOT* send bugreports, help & feature requests directly to the authors!
diff -r 1b65a4abf104 -r 7b85ba8c9be5 DOCS/encoding.html --- a/DOCS/encoding.html Tue Nov 20 14:18:17 2001 +0000 +++ b/DOCS/encoding.html Tue Nov 20 14:19:31 2001 +0000 @@ -17,23 +17,23 @@Compiling
lame binary isn't sufficient. BTW: the less optimization
- you use for lame, the better the quality will be. You can test
- quality by running make test after lame's compiling process
- is over. The resulting number should be less than 30. Don't
- panic if it's 400 or so, you shouldn't heard any audible
- quality decrease. Oh, and if your compiler doesn't even run make test ...
- Well, delete that GCC 2.96.lame binary isn't sufficient. BTW: the less optimization
+ you use for lame, the better the quality will be. You can test
+ quality by running make test after lame's compiling process
+ is over. The resulting number should be less than 30. Don't
+ panic if it's 400 or so, you shouldn't heard any audible
+ quality decrease. Oh, and if your compiler doesn't even run make test ...
+ Well, delete that GCC 2.96.
./configure with optional parameters as usual
- (use --enable-tv to include V4L tuner grabbing code), and
- type : make mencoder , then make install .
+ (use --enable-tv to include V4L tuner grabbing code), and
+ type : make mencoder , then make install.Encoding 2-pass DivX4
The name comes from the fact that this method encodes the file twice. -The first encoding (dubbed pass) creates a temporary file with a size -of few megabytes. In the second pass, the output file is created, using the -bitrate data from the temporary file. The resulting file will have much -better image quality. If this is the first time you heard about this, you -should consult some guides available on the Net.
+The first encoding (dubbed pass) creates some temporary files with a +size of few megabytes (do not delete them yet). In the second pass, the output +file is created, using the bitrate data from the temporary file. The resulting +file will have much better image quality. If this is the first time you heard +about this, you should consult some guides available on the Net.This example shows how to encode a DVD to a 2-pass DivX4 AVI. Just two
commands are needed :
diff -r 1b65a4abf104 -r 7b85ba8c9be5 DOCS/formats.html
--- a/DOCS/formats.html Tue Nov 20 14:18:17 2001 +0000
+++ b/DOCS/formats.html Tue Nov 20 14:19:31 2001 +0000
@@ -113,7 +113,7 @@
supported by most of the players. The file format makes it possible to use VBR
audio, but most players expect CBR audio, thus they fail with VBR. VBR is
unusual, and Microsoft's AVI specs only describe CBR audio. I also note, that
-most AVI encoders/multiplexers create bad files if using VBR audio. only 2
+most AVI encoders/multiplexers create bad files if using VBR audio. Only 2
exception (known by me): NaNDub and MEncoder.
These are from Macintosh. Usually have extensions of .QT or .MOV . Note that since the MPEG4 Group chose QuickTime as the recommended file format -for MPEG4, their .MOV files come with .MPG or .MP4 extension.
+for MPEG4, their .MOV files come with .MPG or .MP4 extension (interesting +that in these files the video stream is a real .MPG file. With the +-dumpvideo option you can even extract it.).
Codecs: any codecs allowed, both CBR and VBR. Note: most new mov files use Sorenson video and QDesign Music audio. These formats are completely diff -r 1b65a4abf104 -r 7b85ba8c9be5 DOCS/video.html --- a/DOCS/video.html Tue Nov 20 14:18:17 2001 +0000 +++ b/DOCS/video.html Tue Nov 20 14:19:31 2001 +0000 @@ -9,39 +9,86 @@
General:
1.1.7: supports software scaling1.1.8: supports Xvideo (hardware scaling/fullscreen)1.2.0: supports AAlib (-vo aa is very recommended, see below!)Card specific:
Card specific:
Special:
Special:
NOTE: check the following subsections for details and requirements!
@@ -176,10 +223,10 @@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.. sell it.
-NOTE: Savage4 has a slow YV12 image displaying capability (it needs +
NOTE: Savage cards have a slow YV12 image displaying capability (it needs to do YV12->YUY2 conversion, because the Savage hardware can't display YV12). So when this documentation says at some point "this has YV12 output use this, -it's faster", you shouldn't. Stick to YUY2.
+it's faster", it's not sure. Try. @@ -201,11 +248,10 @@ disabling VSYNC somehow, or set refresh rate to n*(fps of the movie) Hz.What's status of ATI's tv-out chips under Linux:
Fortunately, owners of fast enough CPUs (Duron, Celeron2 and better) can watch @@ -923,7 +973,7 @@
- +Check this URL.