Be sure to read the VIVO audio codec section too!
- @@ -217,8 +215,10 @@ -AKA VivoSiren. Currently this isn't supported, but when it will, it will use
-the vivog723.acm file. Download from
+
The audio codec used in VIVO files depends on whether it's a VIVO/1.0 or
+VIVO/2.0 file. VIVO/1.0 files have g.723 audio, and VIVO/2.0 files
+have Vivo Siren. Currently none of them is supported, but you can
+grab the g.723 codec from
here,
then copy it into the /usr/lib/win32 directory, or respectively.
You see, a codec isn't equal to a file format.
Video codecs are: MPEG1, MPEG2, DivX, Indeo5, 3ivx.
-Video formats are: MPG, VOB, AVI, ASF.
+Video formats are: MPG, AVI, ASF.
In theory, you can happily put an OpenDivX video and MP3 audio @@ -45,25 +45,30 @@
- +
-vcd option to play the VideoCD.In MPEG files, series of frames are grouped together, and are independent +from the other groups. What this means is you can cut/join an MPEG file with +standard file-tools (like dd, cut), and it remains completely functional.
+One important feature for MPGs is that they have a field to describe the aspect ratio of the video stream within. For example SVCDs have 480x480 resolution video, and in the header that field is set to 4:3, so it's played at 640x480. AVI files don't have this field, so one has to -scale it during encoding.
+rescale it during encoding. @@ -78,26 +83,74 @@ NOTE : DV cameras can create two types of AVI format, one is the usual and playable, the other is neither. +There are two kinds of AVI files: +
-ni option).MPlayer supports 2 kind of timing for AVI files: +
Any audio and video codec is allowed, but note that VBR audio isn't well +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 +exception (known by me): NaNDub and MEncoder.
+ -ASF is a new very undocumented fileformat from M$, and WMV is its -successor. They are very commercial, and anyone who writes an opensource -parser for them, soon meets certain doom. While creating the parser, it -was obvious to see how bulky, shit, and unusable they are. Not if anybody -would expect something else from M$. +
ASF (active streaming format) comes from Microsoft. They developed two +variants of ASF, v1.0 and v2.0. v1.0 is used by their media tools (windows +media player and windows media encoder) and is very secret. v2.0 is published +and patented :). Of course they differ, there is no compatibility at all (it's +just another legal game). MPlayer supports only v1.0, as nobody has ever seen +v2.0 files :) . Note, that .ASF files nowdays come with the extension .WMA or +.WMV.
- + + +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.
-They are Apple's formats. Not much to say, basically well designed, -multipurpose, streamable, many features etc. Kinda hard to find documentation, -but we think the parser is perfect. +
Codecs: any codecs allowed, both CBR and VBR. Note: most new mov files use +Sorenson video and QDesign Music audio. These formats are completely +secret, and only Apple's quicktime player is able to play these files (on +win/mac only).
+ -MPlayer happily demuxes VIVO file formats. This code is new, and -is possibly buggy, no seeking yet. See the VIVO video codec +
MPlayer happily demuxes VIVO file formats. The format's big +disadvantage is that it has no index block, nor fixed packetsize or sync bytes, +and most files lack even keyframes, so forget seeking!
+ +VIVO/1.0 files' video codec is standard h.263 . The VIVO/2.0 files' +video codec is a modified, nonstandard h.263 . Audio is the same, +it may be g.723 (standard), or Vivo Siren .
+ +See the VIVO video codec and VIVO audio codec sections for installation instructions.
diff -r 1a710f130a7f -r 72c750bbc249 DOCS/tech/formats.txt --- a/DOCS/tech/formats.txt Tue Nov 13 13:17:12 2001 +0000 +++ b/DOCS/tech/formats.txt Tue Nov 13 13:17:46 2001 +0000 @@ -59,8 +59,8 @@ Headers: AVI files has a mandatory header at the begin of the file, describing video parameters (resolution, fps) and codecs. Optionally they have an INDEX block at the end of the file. It's optional, but - most files has such block, because it REQUIRES for seeking. - Btw usually it can be rebuild from file content, mplayer does it with + most files has such block, because it's REQUIRED for seeking. + Btw usually it can be rebuilt from file content, mplayer does it with the -idx switch. Mplayer can recreate broken index blocks using -forceidx. As AVI files needs index for random access, broken files with no index are usually unplayable. @@ -97,7 +97,7 @@ - QuickTime / MOV files: They come from Mac users, usually with .mov or .qt extension, but as - MPEG Group choose quicktime as recommended file format for MPEG4, + MPEG Group chose quicktime as recommended file format for MPEG4, sometimes you meet quicktime files with .mpg or .mp4 extension. At first look, it's a mixture of ASF and AVI. diff -r 1a710f130a7f -r 72c750bbc249 DOCS/video.html --- a/DOCS/video.html Tue Nov 13 13:17:12 2001 +0000 +++ b/DOCS/video.html Tue Nov 13 13:17:46 2001 +0000 @@ -170,11 +170,18 @@OR, try the NEW -vo tdfxfb driver! See the 2.3.1.9 section!
+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 to do all kind of conversions, possibly a driver issue). So when +this documentation says at some point "this has YV12 output use this, it's +faster", you shouldn't. Stick to YUY2.
+ +nVidia isn't a very good choice under Linux.. You'll have to use the