November 2006 - MPlayer-DOCS - lists.mplayerhq.hu

r20900 - trunk/DOCS/man/en/mplayer.1
by reimar 14 Nov '06

14 Nov '06

Author: reimar Date: Mon Nov 13 22:06:00 2006 New Revision: 20900 Modified: trunk/DOCS/man/en/mplayer.1 Log: Missing : in -vf expand ar example Modified: trunk/DOCS/man/en/mplayer.1 ============================================================================== --- trunk/DOCS/man/en/mplayer.1 (original) +++ trunk/DOCS/man/en/mplayer.1 Mon Nov 13 22:06:00 2006 @@ -5006,7 +5006,7 @@ .I EXAMPLE: .PD 0 .RSs -.IP expand=800::::4/3 +.IP expand=800:::::4/3 Expands to 800x600, unless the source is higher resolution, in which case it expands to fill a 4/3 aspect. .RE

3 2

A few issues about video.xml
by Torinthiel 13 Nov '06

13 Nov '06

Right now just sections "8.1. Setting up MTRR" and "8.2. Video outputs for traditional video cards", as I've only read those and have enough questions not to postpone it until I finish syncing Polish video.xml around line 25: I did this from XFree 4.x.x , Is the space before coma intentional? Ic could be, not to meld with version number, but I don't like the look of this. A few places where there's an inconsistent indentation of start tag vs end tag: (end tags line numbers only): 39, 47, 51, 1260, 1275, 1282, 1288, 1293, 1326, 1334, 1381, 1406 and a lot more. Around lines 1382--1400 it's a bit different, as it's like: <listitem><simpara> </simpara> <simpara> </simpara></listitem> I'd change it to <listitem> <simpara> </simpara> <simpara> </simpara> </listitem> Line 45: one stray EOL in <screen>, resulting in an ugly HTML rendering. Usually fixed with commenting the EOL. Line 77: I've never seen a shell redirection operator >|. It appears to work, but > or >> (probably >) is more conventional. Line 96: The '' around <option> are IMHO redundant, <option> already makes it stick out of text, both in XML and in HTML. Line 97: Missing period after etc? A quick grep shows that it's usually <example>list, another, etc.</example>, but not everywhere. Line 168-169: <quote>Older 3dfx drivers were known to have problems with XVideo acceleration, it didn't support either YUY2 or YV12, and so.</quote> I don't get the "end so" part at all. And it's the very first sentence of a section. Pretty much inconsistent spelling of 'xv' vs 'Xv' in whole file (same xv as in -vo xv). Which one should it be? Line 195-196: (e.g. append "<option>vga=792 video=vesa:mtrr</option>" to your kernel) s/kernel/kernel parameters/ or something similar. Kernel is a binary, it's not wise to append text to it. Line 548: "Using a depth of 24 bit is even a good idea if ..." Wouldn't it be better "Using a depth of 24 bit is a good idea even if..."? It sound better to me. Line 931: <command>export $__GL_SYNC_TO_VBLANK=1</command> I don't like $ in variable name. And neither does my bash. Lines 1330 and 1332: It's <keycap>Ctrl</keycap>+<keycap>Alt</keycap>+<keycap>plus</keycap> there (about swithing resolution in X) while in line 579 it's <keycap>Ctrl</keycap>+<keycap>Alt</keycap>+<keycap>Keypad +</keycap> I prefer this version. Lines 1458 and 1480 (at least): root (as a user name) is not within <systemitem class="username"> tags. There are some other places before with root, but not as a user name (either as root privilages or SUID root) so these ones don't qualify IMHO. Probably some others later as well, haven't yet examined. Line 1531: Missing period at end of sentence. I'll do this if I have a green light, hopefully in a sane number of commits. And expect some more when I finish with this file ;) PS Am I the only one to actually read and complain about the doc's I'm translating? Or am I just being too pedantic? Torinthiel -- Waclaw "Torinthiel" Schiller GG#: 3073512 torinthiel(at)megapolis(dot)pl gpg: 0906A2CE fpr: EE3E DFB4 C4D6 E22E 8999 D714 7CEB CDDC 0906 A2CE "No classmates may be used during this examination"

2 2

r20879 - trunk/DOCS/xml/en/video.xml
by torinthiel 13 Nov '06

13 Nov '06

Author: torinthiel Date: Mon Nov 13 12:02:30 2006 New Revision: 20879 Modified: trunk/DOCS/xml/en/video.xml Log: [small fixes] - punctuation - improve markup of <screen> - fix odd '>|' as a shell redirection operator - sentence order - key names Modified: trunk/DOCS/xml/en/video.xml ============================================================================== --- trunk/DOCS/xml/en/video.xml (original) +++ trunk/DOCS/xml/en/video.xml Mon Nov 13 12:02:30 2006 @@ -22,7 +22,7 @@ <para> It's right, shows my Matrox G400 with 16MB memory. I did this from -XFree 4.x.x , which sets up MTRR registers automatically. +XFree 4.x.x, which sets up MTRR registers automatically. </para> <para> @@ -42,8 +42,8 @@ command): <screen> 01:00.0 VGA compatible controller: Matrox Graphics, Inc.: Unknown device 0525 -Memory at d8000000 (32-bit, prefetchable) - </screen> +Memory at d8000000 (32-bit, prefetchable)</screen> </para></listitem> <listitem><para> from mga_vid kernel driver messages (use <command>dmesg</command>): @@ -74,7 +74,7 @@ For example, for the Matrox card above (<literal>base=0xd8000000</literal>) with 32MB ram (<literal>size=0x2000000</literal>) just execute: <screen> -echo "base=0xd8000000 size=0x2000000 type=write-combining" >| /proc/mtrr +echo "base=0xd8000000 size=0x2000000 type=write-combining" > /proc/mtrr </screen> </para> @@ -98,8 +98,8 @@ <para> 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 -'<option>-vo xv</option>' uses. Also, this driver supports adjusting -brightness/contrast/hue/etc (unless you use the old, slow DirectShow DivX +<option>-vo xv</option> uses. Also, this driver supports adjusting +brightness/contrast/hue/etc. (unless you use the old, slow DirectShow DivX codec, which supports it everywhere), see the man page. </para> @@ -552,7 +552,7 @@ </para> <para> -Using a depth of 24 bit is even a good idea if your card natively just supports +Using a depth of 24 bit is a good idea even if your card natively just supports 32 bit depth since it transfers 25% less data compared to the 32/32 mode. </para> @@ -1343,9 +1343,9 @@ <listitem><simpara> With XFree86 3.x.x: you have to cycle through available resolutions with the - <keycap>Ctrl</keycap>+<keycap>Alt</keycap>+<keycap>plus</keycap> + <keycap>Ctrl</keycap>+<keycap>Alt</keycap>+<keycap>Keypad +</keycap> and - <keycap>Ctrl</keycap>+<keycap>Alt</keycap>+<keycap>minus</keycap> + <keycap>Ctrl</keycap>+<keycap>Alt</keycap>+<keycap>Keypad -</keycap> keys. </simpara></listitem> </itemizedlist> @@ -1715,7 +1715,7 @@ NTSC. You <emphasis role="bold">must</emphasis> rescale for other heights by adding <option>scale=width:height</option> with the width and height you want to the <option>-vf</option> option. DVB cards accept various widths, like 720, 704, -640, 512, 480, 352 etc and do hardware scaling in horizontal direction, so you +640, 512, 480, 352 etc. and do hardware scaling in horizontal direction, so you do not need to scale horizontally in most cases. For a 512x384 (aspect 4:3) MPEG-4 (DivX) try: </para>

1 0

XviD -> Xvid
by mail＠kraymer.de 13 Nov '06

13 Nov '06

The Xvid team changed the official name to "Xvid", removing the capitalized "D" (see xvid.org) This patch replaces all occurences of "XviD" in the xml docs and the man page. If noone objects, I'll commit this weekend. Sebastian

3 3

r20876 - in trunk/DOCS: man/en/mplayer.1 xml/en/codecs.xml xml/en/encoding-guide.xml xml/en/faq.xml xml/en/mencoder.xml
by kraymer 13 Nov '06

13 Nov '06

Author: kraymer Date: Mon Nov 13 09:53:20 2006 New Revision: 20876 Modified: trunk/DOCS/man/en/mplayer.1 trunk/DOCS/xml/en/codecs.xml trunk/DOCS/xml/en/encoding-guide.xml trunk/DOCS/xml/en/faq.xml trunk/DOCS/xml/en/mencoder.xml Log: rename: XviD -> Xvid Modified: trunk/DOCS/man/en/mplayer.1 ============================================================================== --- trunk/DOCS/man/en/mplayer.1 (original) +++ trunk/DOCS/man/en/mplayer.1 Mon Nov 13 09:53:20 2006 @@ -174,7 +174,7 @@ (MPlayer's Movie Encoder) is a simple movie encoder, designed to encode MPlayer-playable movies (see above) to other MPlayer-playable formats (see below). -It encodes to MPEG-4 (DivX/XviD), one of the libavcodec codecs and +It encodes to MPEG-4 (DivX/Xvid), one of the libavcodec codecs and PCM/\:MP3/\:VBRMP3 audio in 1, 2 or 3 passes. Furthermore it has stream copying abilities, a powerful filter system (crop, expand, flip, postprocess, rotate, scale, noise, RGB/\:YUV conversion) and @@ -3951,7 +3951,7 @@ .br 2 (msmpeg4v3): some old lavc generated msmpeg4v3 files (no autodetection) .br -4 (mpeg4): XviD interlacing bug (autodetected if fourcc==XVIX) +4 (mpeg4): Xvid interlacing bug (autodetected if fourcc==XVIX) .br 8 (mpeg4): UMP4 (autodetected if fourcc==UMP4) .br @@ -3959,7 +3959,7 @@ .br 32 (mpeg4): illegal vlc bug (autodetected per fourcc) .br -64 (mpeg4): XviD and DivX qpel bug (autodetected per fourcc/\:version) +64 (mpeg4): Xvid and DivX qpel bug (autodetected per fourcc/\:version) .br 128 (mpeg4): old standard qpel (autodetected per fourcc/\:version) .br @@ -4272,13 +4272,13 @@ . .TP .B \-xvidopts <option1:option2:...> -Specify additional parameters when decoding with XviD. +Specify additional parameters when decoding with Xvid. .br .I NOTE: -Since libavcodec is faster than XviD you might want to use the libavcodec +Since libavcodec is faster than Xvid you might want to use the libavcodec postprocessing filter (\-vf pp) and decoder (\-vfm ffmpeg) instead. .sp 1 -XviD's internal postprocessing filters: +Xvid's internal postprocessing filters: .PD 0 .RSs .IPs deblock-chroma (also see \-vf pp) @@ -7499,8 +7499,8 @@ .IPs 0 Use internal lavc ratecontrol (default). .IPs 1 -Use XviD ratecontrol (experimental; requires MEncoder to be compiled -with support for XviD 1.1 or higher). +Use Xvid ratecontrol (experimental; requires MEncoder to be compiled +with support for Xvid 1.1 or higher). .RE .PD 1 . @@ -8440,7 +8440,7 @@ .B bitrate=<value> (CBR or two pass mode) Sets the bitrate to be used in kbits/\:second if <16000 or in bits/\:second if >16000. -If <value> is negative, XviD will use its absolute value as the target size +If <value> is negative, Xvid will use its absolute value as the target size (in kBytes) of the video and compute the associated bitrate automagically (default: 687 kbits/s). . @@ -8502,7 +8502,7 @@ This might give better compression, but slows down encoding. .br .I WARNING: -As of XviD-1.0.x, this option is no longer available separately, and its +As of Xvid-1.0.x, this option is no longer available separately, and its functionality is included in the me_quality option. When me_quality > 4, 4mv is activated. . @@ -8516,9 +8516,9 @@ .B rc_averaging_period=<value> Real CBR is hard to achieve. Depending on the video material, bitrate can be variable, and hard to predict. -Therefore XviD uses an averaging period for which it guarantees a given +Therefore Xvid uses an averaging period for which it guarantees a given amount of bits (minus a small variation). -This settings expresses the "number of frames" for which XviD averages +This settings expresses the "number of frames" for which Xvid averages bitrate and tries to achieve CBR. . .TP @@ -8532,7 +8532,7 @@ two pass mode: min & max quantizer for I/P-frames (default: 2\-31/\:2\-31) .br .I WARNING: -As of XviD-1.0.x, this option is replaced by the +As of Xvid-1.0.x, this option is replaced by the [min|max]_[i|p|b]quant options. . .TP @@ -8551,7 +8551,7 @@ When using custom matrices, MPEG must be used. .br .I WARNING: -As of XviD-1.0.x, this option is replaced by the quant_type option. +As of Xvid-1.0.x, this option is replaced by the quant_type option. . .TP .B mod_quant @@ -8560,10 +8560,10 @@ .br .I WARNING: This will generate an illegal bitstream, and most likely not be decodable -by any MPEG-4 decoder besides libavcodec or XviD. +by any MPEG-4 decoder besides libavcodec or Xvid. .br .I WARNING: -As of XviD-1.0.x, this option is no longer available. +As of Xvid-1.0.x, this option is no longer available. . .TP .B keyframe_boost=<0\-1000> (two pass mode only) @@ -8596,11 +8596,11 @@ This seems to be mandatory only for old versions of DivX's decoder. .br .I WARNING: -As of XviD-1.0.x, this option is replaced by the closed_gop option. +As of Xvid-1.0.x, this option is replaced by the closed_gop option. . .TP .B (no)grayscale -Make XviD discard chroma planes so the encoded video is grayscale only. +Make Xvid discard chroma planes so the encoded video is grayscale only. Note that this does not speed up encoding, it just prevents chroma data from being written in the last stage of encoding. . @@ -8613,7 +8613,7 @@ .PP .sp 1 The following options are only available with the latest stable -releases of XviD 1.0.x (api4). +releases of Xvid 1.0.x (api4). . .TP .B (no)packed @@ -8626,7 +8626,7 @@ .br .I WARNING: This will generate an illegal bitstream, and will not be -decodable by ISO-MPEG-4 decoders except DivX/\:libavcodec/\:XviD. +decodable by ISO-MPEG-4 decoders except DivX/\:libavcodec/\:Xvid. .br .I WARNING: This will also store a fake DivX version in the file so the bug @@ -8655,7 +8655,7 @@ . .TP .B (no)closed_gop -This option tells XviD to close every GOP (Group Of Pictures bounded +This option tells Xvid to close every GOP (Group Of Pictures bounded by two I-frames), which makes GOPs independent from each other. This just implies that the last frame of the GOP is either a P-frame or a N-frame but not a B-frame. @@ -8688,7 +8688,7 @@ . .TP .B (no)gmc -Enable Global Motion Compensation, which makes XviD generate special +Enable Global Motion Compensation, which makes Xvid generate special frames (GMC-frames) which are well suited for Pan/\:Zoom/\:Rotating images. Whether or not the use of this option will save bits is highly dependent on the source material. @@ -8705,7 +8705,7 @@ .TP .B (no)cartoon Activate this if your encoded sequence is an anime/\:cartoon. -It modifies some XviD internal thresholds so XviD takes better decisions on +It modifies some Xvid internal thresholds so Xvid takes better decisions on frame types and motion vectors for flat looking cartoons. . .TP @@ -8747,7 +8747,7 @@ The motion search algorithm is based on a search in the usual color domain and tries to find a motion vector that minimizes the difference between the reference frame and the encoded frame. -With this setting activated, XviD will also use the frequency domain (DCT) +With this setting activated, Xvid will also use the frequency domain (DCT) to search for a motion vector that minimizes not only the spatial difference but also the encoding length of the block. Fastest to slowest: @@ -8813,7 +8813,7 @@ . .TP .B curve_compression_high=<0\-100> -This setting allows XviD to take a certain percentage of bits away from +This setting allows Xvid to take a certain percentage of bits away from high bitrate scenes and give them back to the bit reservoir. You could also use this if you have a clip with so many bits allocated to high-bitrate scenes that the low(er)-bitrate scenes start to look bad @@ -8821,7 +8821,7 @@ . .TP .B curve_compression_low=<0\-100> -This setting allows XviD to give a certain percentage of extra bits to the +This setting allows Xvid to give a certain percentage of extra bits to the low bitrate scenes, taking a few bits from the entire clip. This might come in handy if you have a few low-bitrate scenes that are still blocky (default: 0). @@ -8868,9 +8868,9 @@ care of the video container overhead. This small but (mostly) constant overhead can cause the target file size to be exceeded. -XviD allows users to set the amount of overhead per frame the +Xvid allows users to set the amount of overhead per frame the container generates (give only an average per frame). -0 has a special meaning, it lets XviD use its own default values +0 has a special meaning, it lets Xvid use its own default values (default: 24 \- AVI average overhead). . .TP @@ -8920,7 +8920,7 @@ .RS .I NOTE: These profiles should be used in conjunction with an appropriate \-ffourcc. -Generally DX50 is applicable, as some players do not recognize XviD but +Generally DX50 is applicable, as some players do not recognize Xvid but most recognize DivX. .RE . @@ -8990,7 +8990,7 @@ . .PP .sp 1 -The following option is only available in XviD 1.1.x. +The following option is only available in Xvid 1.1.x. . .TP .B bvhq=<0|1> @@ -9002,7 +9002,7 @@ . .PP .sp 1 -The following option is only available in the CVS version of XviD. +The following option is only available in the CVS version of Xvid. . .TP .B threads=<0\-n> Modified: trunk/DOCS/xml/en/codecs.xml ============================================================================== --- trunk/DOCS/xml/en/codecs.xml (original) +++ trunk/DOCS/xml/en/codecs.xml Mon Nov 13 09:53:20 2006 @@ -109,10 +109,10 @@ <sect2 id="xvid"> -<title>XviD</title> +<title>Xvid</title> <para> -<ulink url="http://www.xvid.org">XviD</ulink> is a free software MPEG-4 ASP +<ulink url="http://www.xvid.org">Xvid</ulink> is a free software MPEG-4 ASP compliant video codec, which features two pass encoding and full MPEG-4 ASP support, making it a lot more efficient than the well-known DivX codec. It yields very good video quality and good performance due to CPU @@ -122,24 +122,24 @@ It began as a forked development of the OpenDivX codec. This happened when ProjectMayo changed OpenDivX to closed source DivX4, and the non-ProjectMayo people working on OpenDivX got angry, -then started XviD. So both projects have the same origin. +then started Xvid. So both projects have the same origin. </para> <para> -Note that XviD is not necessary to decode XviD-encoded video. +Note that Xvid is not necessary to decode Xvid-encoded video. <systemitem class="library">libavcodec</systemitem> is used by default as it offers better speed. </para> <procedure> -<title>Installing <systemitem class="library">XviD</systemitem></title> +<title>Installing <systemitem class="library">Xvid</systemitem></title> <para> Like most open source software, it is available in two flavors: <ulink url="http://www.xvid.org/downloads.html">official releases</ulink> and the CVS version. The CVS version is usually stable enough to use, as most of the time it features fixes for bugs that exist in releases. - Here is what to do to make <systemitem class="library">XviD</systemitem> + Here is what to do to make <systemitem class="library">Xvid</systemitem> CVS work with <application>MEncoder</application> (you need at least <application>autoconf</application> 2.50, <application>automake</application> and <application>libtool</application>): Modified: trunk/DOCS/xml/en/encoding-guide.xml ============================================================================== --- trunk/DOCS/xml/en/encoding-guide.xml (original) +++ trunk/DOCS/xml/en/encoding-guide.xml Mon Nov 13 09:53:20 2006 @@ -309,7 +309,7 @@ <para> Most codecs which support ABR encode only support two pass encode while some others such as <systemitem class="library">x264</systemitem>, - <systemitem class="library">XviD</systemitem> + <systemitem class="library">Xvid</systemitem> and <systemitem class="library">libavcodec</systemitem> support multipass, which slightly improves quality at each pass, yet this improvement is no longer measurable nor noticeable after the @@ -1089,7 +1089,7 @@ In order to raise the CQ, typically you would downscale the movie given that the bitrate is computed in function of the target size and the length of the movie, which are constant. - With MPEG-4 ASP codecs such as <systemitem class="library">XviD</systemitem> + With MPEG-4 ASP codecs such as <systemitem class="library">Xvid</systemitem> and <systemitem class="library">libavcodec</systemitem>, a CQ below 0.18 usually results in a pretty blocky picture, because there are not enough bits to code the information of each macroblock. (MPEG4, like @@ -1101,7 +1101,7 @@ More advanced encoding options such as those listed here for <link linkend="menc-feat-mpeg4-lavc-example-settings"><systemitem class="library">libavcodec</systemitem></link> and -<link linkend="menc-feat-xvid-example-settings"><systemitem class="library">XviD</systemitem></link> +<link linkend="menc-feat-xvid-example-settings"><systemitem class="library">Xvid</systemitem></link> should make it possible to get the same quality with CQ ranging from 0.18 to 0.20 for a 1 CD rip, and 0.24 to 0.26 for a 2 CD rip. With MPEG-4 ASP codecs such as <systemitem class="library">x264</systemitem>, @@ -1379,7 +1379,7 @@ when choosing MPEG-4 AVC codecs like <systemitem class="library">x264</systemitem> instead of MPEG-4 ASP codecs such as <systemitem class="library">libavcodec</systemitem> MPEG-4 or - <systemitem class="library">XviD</systemitem>. + <systemitem class="library">Xvid</systemitem>. (Advanced codec developers may be interested in reading Michael Niedermayer's opinion on "<ulink url="http://guru.multimedia.cx/?p=10">why MPEG4-ASP sucks</ulink>".) @@ -1404,7 +1404,7 @@ As a result, most only support MPEG-1 (like VCD, XVCD and KVCD), MPEG-2 (like DVD, SVCD and KVCD) and MPEG-4 ASP (like DivX, <systemitem class="library">libavcodec</systemitem>'s LMP4 and - <systemitem class="library">XviD</systemitem>) + <systemitem class="library">Xvid</systemitem>) (Beware: Usually, not all MPEG-4 ASP features are supported). Please refer to the technical specs of your player (if they are available), or google around for more information. @@ -1414,7 +1414,7 @@ <emphasis role="bold">Best quality per encoding time</emphasis>: Codecs that have been around for some time (such as <systemitem class="library">libavcodec</systemitem> MPEG-4 and - <systemitem class="library">XviD</systemitem>) are usually heavily + <systemitem class="library">Xvid</systemitem>) are usually heavily optimized with all kinds of smart algorithms and SIMD assembly code. That is why they tend to yield the best quality per encoding time ratio. However, they may have some very advanced options that, if enabled, @@ -1432,7 +1432,7 @@ <systemitem class="library">libavcodec</systemitem> MPEG-4 does allow that, but speed gains are limited, and there is a slight negative effect on picture quality. - <systemitem class="library">XviD</systemitem>'s multi-threaded encoding, + <systemitem class="library">Xvid</systemitem>'s multi-threaded encoding, activated by the <option>threads</option> option, can be used to boost encoding speed — by about 40-60% in typical cases — with little if any picture degradation. @@ -1445,7 +1445,7 @@ <emphasis role="bold">Personal taste</emphasis>: This is where it gets almost irrational: For the same reason that some hung on to DivX 3 for years when newer codecs were already doing wonders, - some folks will prefer <systemitem class="library">XviD</systemitem> + some folks will prefer <systemitem class="library">Xvid</systemitem> or <systemitem class="library">libavcodec</systemitem> MPEG-4 over <systemitem class="library">x264</systemitem>. </para> @@ -2383,7 +2383,7 @@ H.263+ </entry></row> <row><entry>mpeg4</entry><entry> - ISO standard MPEG-4 (DivX, XviD compatible) + ISO standard MPEG-4 (DivX, Xvid compatible) </entry></row> <row><entry>msmpeg4</entry><entry> pre-standard MPEG-4 variant by MS, v3 (AKA DivX3) @@ -2913,10 +2913,10 @@ <sect1 id="menc-feat-xvid"> -<title>Encoding with the <systemitem class="library">XviD</systemitem> +<title>Encoding with the <systemitem class="library">Xvid</systemitem> codec</title> <para> - <systemitem class="library">XviD</systemitem> is a free library for + <systemitem class="library">Xvid</systemitem> is a free library for encoding MPEG-4 ASP video streams. Before starting to encode, you need to <link linkend="xvid"> set up <application>MEncoder</application> to support it</link>. @@ -2935,19 +2935,19 @@ <para> Please begin by reviewing the - <systemitem class="library">XviD</systemitem> section of + <systemitem class="library">Xvid</systemitem> section of <application>MPlayer</application>'s man page. This section is intended to be a supplement to the man page. </para> <para> - The XviD default settings are already a good tradeoff between + The Xvid default settings are already a good tradeoff between speed and quality, therefore you can safely stick to them if the following section puzzles you. </para> </sect2> <sect2 id="menc-feat-xvid-encoding-options"> -<title>Encoding options of <systemitem class="library">XviD</systemitem></title> +<title>Encoding options of <systemitem class="library">Xvid</systemitem></title> <itemizedlist> <listitem><para> @@ -3105,7 +3105,7 @@ encoding (as well as decoding). Therefore, you should only use it when you have turned <option>vhq</option> to the maximum. - <systemitem class="library">XviD</systemitem>'s GMC is more + <systemitem class="library">Xvid</systemitem>'s GMC is more sophisticated than DivX's, but is only supported by few standalone players. </para></listitem> @@ -3116,8 +3116,8 @@ <sect2 id="menc-feat-xvid-encoding-profiles"> <title>Encoding profiles</title> <para> - XviD supports encoding profiles through the <option>profile</option> option, - which are used to impose restrictions on the properties of the XviD video + Xvid supports encoding profiles through the <option>profile</option> option, + which are used to impose restrictions on the properties of the Xvid video stream such that it will be playable on anything which supports the chosen profile. The restrictions relate to resolutions, bitrates and certain MPEG-4 Modified: trunk/DOCS/xml/en/faq.xml ============================================================================== --- trunk/DOCS/xml/en/faq.xml (original) +++ trunk/DOCS/xml/en/faq.xml Mon Nov 13 09:53:20 2006 @@ -1181,7 +1181,7 @@ Therefore, if you change the FourCC to DIVX, some bad software or hardware players may choke on some advanced features that <systemitem class="library">libavcodec</systemitem> supports, but DivX -doesn't; on the other hand <systemitem class="library">XviD</systemitem> +doesn't; on the other hand <systemitem class="library">Xvid</systemitem> is closer to <systemitem class="library">libavcodec</systemitem> in terms of functionality, and is supported by all decent players. </para></answer> Modified: trunk/DOCS/xml/en/mencoder.xml ============================================================================== --- trunk/DOCS/xml/en/mencoder.xml (original) +++ trunk/DOCS/xml/en/mencoder.xml Mon Nov 13 09:53:20 2006 @@ -84,7 +84,7 @@ </row> <row> <entry>xvid</entry> - <entry>XviD, MPEG-4 Advanced Simple Profile (ASP) codec</entry> + <entry>Xvid, MPEG-4 Advanced Simple Profile (ASP) codec</entry> </row> <row> <entry>x264</entry> @@ -524,7 +524,7 @@ </para></listitem> <listitem><para> <application>MEncoder</application> then feeds the decoded image to the - chosen video compressor (DivX4, XviD, FFmpeg msmpeg4, etc.). + chosen video compressor (DivX4, Xvid, FFmpeg msmpeg4, etc.). </para></listitem> </orderedlist>

1 0

r20873 - trunk/DOCS/xml/en/video.xml
by diego 13 Nov '06

13 Nov '06

Author: diego Date: Sun Nov 12 23:56:42 2006 New Revision: 20873 Modified: trunk/DOCS/xml/en/video.xml Log: Misc issues noticed by Torinthiel. Modified: trunk/DOCS/xml/en/video.xml ============================================================================== --- trunk/DOCS/xml/en/video.xml (original) +++ trunk/DOCS/xml/en/video.xml Sun Nov 12 23:56:42 2006 @@ -166,9 +166,9 @@ <para> 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, <emphasis role="bold">crashes with YV12</emphasis>. +didn't support YUY2 or YV12 colorspaces. Verify that you have XFree86 +version 4.2.0 or later, it can handle YV12 and YUY2 while previous +versions, including 4.1.0, <emphasis role="bold">crash with YV12</emphasis>. If you experience strange effects using <option>-vo xv</option>, try SDL (it has XVideo, too) and see if it helps. Check the <link linkend="sdl">SDL</link> section for details. @@ -193,7 +193,7 @@ <para> There is now a native framebuffer driver for S3 Virge cards similiar to tdfxfb. Set up your framebuffer (e.g. append -"<option>vga=792 video=vesa:mtrr</option>" to your kernel) and use +"<option>vga=792 video=vesa:mtrr</option>" to your kernel comand line) and use <option>-vo s3fb</option> (<option>-vf yuy2</option> and <option>-dr</option> will also help). </para> @@ -928,7 +928,7 @@ </para> <para> -<command>export $__GL_SYNC_TO_VBLANK=1</command> +<command>export __GL_SYNC_TO_VBLANK=1</command> </para> </sect2> @@ -1528,7 +1528,7 @@ <para> The driver was written and is maintained by -<ulink url="http://www.blackfiveservices.co.uk/EPIAVidix.shtml">Alastair M. Robinson</ulink> +<ulink url="http://www.blackfiveservices.co.uk/EPIAVidix.shtml">Alastair M. Robinson</ulink>. </para> </sect3>

1 0

r20872 - trunk/DOCS/man/en/mplayer.1
by reimar 13 Nov '06

13 Nov '06

Author: reimar Date: Sun Nov 12 21:09:51 2006 New Revision: 20872 Modified: trunk/DOCS/man/en/mplayer.1 Log: Clarify -dumpaudio, it is not useful normally Modified: trunk/DOCS/man/en/mplayer.1 ============================================================================== --- trunk/DOCS/man/en/mplayer.1 (original) +++ trunk/DOCS/man/en/mplayer.1 Sun Nov 12 21:09:51 2006 @@ -1196,7 +1196,8 @@ . .TP .B \-dumpaudio (MPlayer only) -Dumps raw compressed audio stream to ./stream.dump (useful with MPEG/\:AC3). +Dumps raw compressed audio stream to ./stream.dump (useful with MPEG/\:AC3, +in most other cases the resulting file will not be playable). If you give more than one of \-dumpaudio, \-dumpvideo, \-dumpstream on the command line only the last one will work. .

1 0

r20866 - trunk/DOCS/xml/en/install.xml
by diego 13 Nov '06

13 Nov '06

Author: diego Date: Sun Nov 12 17:44:54 2006 New Revision: 20866 Modified: trunk/DOCS/xml/en/install.xml Log: Recommend gcc 3.4+. Modified: trunk/DOCS/xml/en/install.xml ============================================================================== --- trunk/DOCS/xml/en/install.xml (original) +++ trunk/DOCS/xml/en/install.xml Sun Nov 12 17:44:54 2006 @@ -33,8 +33,8 @@ </para></listitem> <listitem><para> <emphasis role="bold">gcc</emphasis> - Recommended versions are 2.95 - and 3.3+. 2.96 and 3.0.x are known to generate faulty code, 3.1 and - 3.2 also had problems. On PowerPC, use 4.x+. + and 3.4+. 2.96 and 3.0.x are known to generate faulty code, 3.1 and + 3.2 also had problems, 3.3 some minor ones. </para></listitem> <listitem><para> <emphasis role="bold">XFree86</emphasis> - Recommended version is <emphasis role="bold">always the

3 2

r20870 - trunk/DOCS/xml/en/install.xml
by diego 13 Nov '06

13 Nov '06

Author: diego Date: Sun Nov 12 19:41:30 2006 New Revision: 20870 Modified: trunk/DOCS/xml/en/install.xml Log: Restore PowerPC gcc note that I mistakenly removed. Modified: trunk/DOCS/xml/en/install.xml ============================================================================== --- trunk/DOCS/xml/en/install.xml (original) +++ trunk/DOCS/xml/en/install.xml Sun Nov 12 19:41:30 2006 @@ -34,7 +34,7 @@ <listitem><para> <emphasis role="bold">gcc</emphasis> - Recommended versions are 2.95 and 3.4+. 2.96 and 3.0.x are known to generate faulty code, 3.1 and - 3.2 also had problems, 3.3 some minor ones. + 3.2 also had problems, 3.3 some minor ones. On PowerPC, use 4.x. </para></listitem> <listitem><para> <emphasis role="bold">XFree86</emphasis> - Recommended version is <emphasis role="bold">always the

1 0

Online Russian HTML page, generated from mplayer.1 is broken
by Vladimir Voroshilov 12 Nov '06

12 Nov '06

Hi, All I have found that russian html page, generated by groff from mplayer.1 and published on MPlayer website have broken encoding. It doesn't have any cyrilly characted. Here is a line from page source <a href="#éóðïìøúï÷áîéå">éóðïìøúï÷áîéå</a><br> I'm think, that it was generated using ISO-8859-1 (or similar) encoding enstead of koi8-r. -- Regards, Vladimir Voroshilov mailto:voroshil@gmail.com JID: voroshil(a)jabber.ru ICQ: 95587719

5 10