January 2007 - MPlayer-DOCS - lists.mplayerhq.hu

Hungarian docs broken
by Dominik 'Rathann' Mierzejewski 25 Jan '07

25 Jan '07

Clearly someone did NOT run xmllint before committing: /usr/bin/make HTMLDIR=../../HTML/hu -C hu html-chunked make[1]: Entering directory `/builddir/build/BUILD/MPlayer-22010/DOCS/xml/hu' rm -f ../../HTML/hu/* ../xmllint.sh main.xml faq.xml:85: parser error : Opening and ending tag mismatch: qandaentry line 76 and para </para></question> ^ faq.xml:85: parser error : Opening and ending tag mismatch: qandadiv line 73 and question </para></question> ^ faq.xml:95: parser error : Opening and ending tag mismatch: qandaset line 6 and qandaentry </qandaentry> ^ faq.xml:201: parser error : Opening and ending tag mismatch: chapter line 3 and qandadiv </qandadiv> ^ faq.xml:1284: parser error : chunk is not well balanced </qandaset> ^ faq.xml:1284: parser error : chunk is not well balanced </qandaset> ^ documentation.xml:187: parser error : Failure to process entity faq.xml &faq.xml; ^ documentation.xml:187: parser error : Entity 'faq.xml' not defined &faq.xml; ^ main.xml:29: parser error : Failure to process entity documentation.xml &documentation.xml; ^ main.xml:29: parser error : Entity 'documentation.xml' not defined &documentation.xml; ^ make[1]: *** [../../HTML/hu/index.html] Error 1 make[1]: Leaving directory `/builddir/build/BUILD/MPlayer-22010/DOCS/xml/hu' make: *** [html-chunked-hu] Error 2 Regards, R. -- MPlayer developer and RPMs maintainer: http://mplayerhq.hu http://rpm.livna.org There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan

2 3

[homepage]: r2777 - trunk/mwn/NEWS
by diego 25 Jan '07

25 Jan '07

Author: diego Date: Thu Jan 25 02:24:49 2007 New Revision: 2777 Removed: trunk/mwn/NEWS Log: Whatever this was, it's obsolete now.

1 0

[homepage]: r2776 - in trunk: design7/src/selector images/hup2006-s.png images/hup2006.png src/news.src.en
by diego 25 Jan '07

25 Jan '07

Author: diego Date: Thu Jan 25 02:12:59 2007 New Revision: 2776 Added: trunk/images/hup2006-s.png (contents, props changed) trunk/images/hup2006.png (contents, props changed) Modified: trunk/design7/src/selector trunk/src/news.src.en Log: HUP award 2006 Modified: trunk/design7/src/selector ============================================================================== --- trunk/design7/src/selector (original) +++ trunk/design7/src/selector Thu Jan 25 02:12:59 2007 @@ -20,6 +20,8 @@ <div> awards<br> + <a href="news.html#HUPAward2006"> + <img src="../images/hup2006-s.png" alt="HUP Readers' Choice Award 2006" width="29" height="29"></a> <a href="news.html#LqAward2005"> <img src="../images/LQ-2005MCA-video-s.png" alt="2005 LinuxQuestions.org Members Choice Award" width="29" height="29"></a> <a href="news.html#HUPAward2005"> Added: trunk/images/hup2006-s.png ============================================================================== Binary file. No diff available. Added: trunk/images/hup2006.png ============================================================================== Binary file. No diff available. Modified: trunk/src/news.src.en ============================================================================== --- trunk/src/news.src.en (original) +++ trunk/src/news.src.en Thu Jan 25 02:12:59 2007 @@ -8,6 +8,40 @@ <div class="newsentry"> <h2> + <a name="HUPAward2006">2007.01.17, Wednesday :: HUP Readers' Choice Award 2006</a> + <br><span class="poster">posted by Diego</span> +</h2> + +<p class="left-inset"> +<a href="http://hup.hu/node/33504"> +<img src="../images/hup2006.png" alt="HUP Readers' Choice Award 2006" width="120" height="120"></a> +</p> + +<p> +Like every year the <a href="http://hup.hu">Hungarian Unix Portal</a> has +held its annual Readers' Choice Award and once again MPlayer came out on +top of the "favorite video player" category. +MPlayer got 799 votes (73%), placing it before VLC with 148 (13%) and +xine with 52 (5%). +<p> + +<p> +We also managed to return to the top of the "Favorite Hungarian Project" +category. Thanks for the support! +</p> + +<p> +If you can read Hungarian, check out the +<a href="http://hup.hu/node/33504">HUP award page</a>. +</p> + +</div> + + + +<div class="newsentry"> + +<h2> <a name="vuln14">2006.12.31, Sunday :: buffer overflow in asmrp.c</a> <br><span class="poster">posted by Roberto</span> </h2>

1 0

r22008 - trunk/DOCS/man/en/mplayer.1
by diego 24 Jan '07

24 Jan '07

Author: diego Date: Wed Jan 24 23:06:31 2007 New Revision: 22008 Modified: trunk/DOCS/man/en/mplayer.1 Log: Address age-old FIXMEs about tdfx_vid, tdfxfb and 3dfx vo drivers. Modified: trunk/DOCS/man/en/mplayer.1 ============================================================================== --- trunk/DOCS/man/en/mplayer.1 (original) +++ trunk/DOCS/man/en/mplayer.1 Wed Jan 24 23:06:31 2007 @@ -3594,16 +3594,14 @@ . .TP .B 3dfx (Linux only) -3dfx specific video output driver. -This driver directly uses the 3dfx hardware on top of X11. +3dfx-specific video output driver that directly uses +the hardware on top of X11. Only 16 bpp are supported. -FIXME: It' ok the difference between 3dfx, tdfxfb and tdfx_vid? . .TP .B tdfxfb (Linux only) -This driver employs the tdfx framebuffer driver to play movies with +This driver employs the tdfxfb framebuffer driver to play movies with YUV acceleration on 3dfx cards. -FIXME: It' ok the difference between 3dfx, tdfxfb and tdfx_vid? .PD 0 .RSs .IPs <device> @@ -3613,9 +3611,8 @@ . .TP .B tdfx_vid (Linux only) -3dfx specific video output driver. -This driver directly uses the tdfx_vid kernel module. -FIXME: It' ok the difference between 3dfx, tdfxfb and tdfx_vid? +3dfx-specific video output driver that works in combination with +the tdfx_vid kernel module. .PD 0 .RSs .IPs <device>

1 0

[homepage]: r2775 - trunk/src/projects.src.en
by diego 24 Jan '07

24 Jan '07

Author: diego Date: Wed Jan 24 12:34:58 2007 New Revision: 2775 Modified: trunk/src/projects.src.en Log: SMSG Modified: trunk/src/projects.src.en ============================================================================== --- trunk/src/projects.src.en (original) +++ trunk/src/projects.src.en Wed Jan 24 12:34:58 2007 @@ -200,6 +200,9 @@ <li><a href="http://mulder.dummwiedeutsch.de/home/html/projects.html#mencoder264">MEncoder264</a><br> a GUI for Windows for H.264 encoding via MEncoder </li> + <li><a href="http://sf.net/projects/smsg/">SMSG</a><br> + Simple Mencoder Shell GUI, batch video transcoding application + without all tabs, buttons and other fuzz</li> </ul>

1 0

r21989 - trunk/DOCS/man/en/mplayer.1
by Gabrov 21 Jan '07

21 Jan '07

Author: Gabrov Date: Sun Jan 21 22:40:23 2007 New Revision: 21989 Modified: trunk/DOCS/man/en/mplayer.1 Log: fix typo Modified: trunk/DOCS/man/en/mplayer.1 ============================================================================== --- trunk/DOCS/man/en/mplayer.1 (original) +++ trunk/DOCS/man/en/mplayer.1 Sun Jan 21 22:40:23 2007 @@ -768,7 +768,7 @@ (\-vo directx only). .br .I NOTE: -you will get slightly different behaviour depending on whether you bind +You will get slightly different behaviour depending on whether you bind MOUSE_BTN0_DBL or MOUSE_BTN0\-MOUSE_BTN0_DBL. . .TP

1 0

r21954 - trunk/DOCS/man/en/mplayer.1
by lorenm 17 Jan '07

17 Jan '07

Author: lorenm Date: Thu Jan 18 00:20:32 2007 New Revision: 21954 Modified: trunk/DOCS/man/en/mplayer.1 Log: "-lavdopts fast" has applied to mpeg4 and h264 for a while Modified: trunk/DOCS/man/en/mplayer.1 ============================================================================== --- trunk/DOCS/man/en/mplayer.1 (original) +++ trunk/DOCS/man/en/mplayer.1 Thu Jan 18 00:20:32 2007 @@ -4069,11 +4069,11 @@ .br 4: very aggressive .REss -.IPs "fast (MPEG-2 only)" +.IPs "fast (MPEG-2, MPEG-4, and H.264 only)" Enable optimizations which do not comply to the specification and might -potentially cause problems, like simpler dequantization, assuming use -of the default quantization matrix, assuming YUV 4:2:0 and skipping a few -checks to detect damaged bitstreams. +potentially cause problems, like simpler dequantization, simpler motion +compensation, assuming use of the default quantization matrix, assuming +YUV 4:2:0 and skipping a few checks to detect damaged bitstreams. .IPs "gray\ " grayscale only decoding (a bit faster than with color) .IPs "idct=<0\-99> (see \-lavcopts)"

1 0

encoding-guide: inconsistency info about threads in x264enc
by Andrew Savchenko 17 Jan '07

17 Jan '07

Hi, I've found some contradiction in encoding-guide documentation: 1) Section "Making a high quality MPEG-4 ("DivX") rip of a DVD movie", subsection "Choosing the video codec" says: ***** x264 also allows multi-threaded encoding, which currently speeds up encoding by 15-30% (depending on the encoding settings) while lowering PSNR by about 0.05dB. ***** But in recently added part "Using MEncoder to create QuickTime-compatible files", subsection "Encoding example" anyone can find: ***** If you have multi-processor machine, you can add threads=auto. This increases encoding speed by about 94% per CPU core, with very little quality penalty (about 0.005dB for dual processor, about 0.01dB for a quad processor machine). ***** I uderstand, that speedup values are only for rude estimation purposes. But they differs very greatly: 15-30% vs ~94%. One of them should be fixed... I've no multi-processor system, so I can't check this values on my own. PSNR impact also varies... Maybe algorithms in x264enc was changed since 1st quotation was wrote, or perhaps this value is highly dependant on source material. 2) The last quatation mentions about 'threads=auto' option, but 'auto' is not mentioned in man page as acceptable value: ***** threads=<1-4> Split each frame into slices and encode them in parallel (default: 1). Also allows multithreaded decoding if the decoder supports it (lavc doesnot). This has a slight penalty to compression. Requires that libx264 was compiled with pthread support; if not, this option will produce a warningand enables slices but not multithreading. ***** I've test option threads=auto, it seems work fine. So man page should be updated.

3 2

r21861 - trunk/DOCS/xml/en/encoding-guide.xml
by gpoirier 15 Jan '07

15 Jan '07

Author: gpoirier Date: Wed Jan 10 01:08:16 2007 New Revision: 21861 Modified: trunk/DOCS/xml/en/encoding-guide.xml Log: explain how to use MEncoder to create QuickTime-compatible files Mainly based on a patch by Mark Pilgrim % pilgrim A gmail P com % Original thread: Date: Oct 19, 2006 9:50 PM Subject: [MPlayer-DOCS] Interested in contributing case studies Modified: trunk/DOCS/xml/en/encoding-guide.xml ============================================================================== --- trunk/DOCS/xml/en/encoding-guide.xml (original) +++ trunk/DOCS/xml/en/encoding-guide.xml Wed Jan 10 01:08:16 2007 @@ -2898,11 +2898,12 @@ <option>filmdint</option>. </para> -<para> +<para id="menc-feat-dvd-mpeg4-example-crop"> Next, we want to determine the appropriate crop rectangle, so we use the cropdetect filter: <screen>mplayer dvd://1 -vf cropdetect</screen> -Make sure you seek to a fully filled frame (such as a bright scene), and +Make sure you seek to a fully filled frame (such as a bright scene, +past the opening credits and logos), and you will see in <application>MPlayer</application>'s console output: <screen>crop area: X: 0..719 Y: 57..419 (-vf crop=720:362:0:58)</screen> We then play the movie back with this filter to test its correctness: @@ -4082,6 +4083,321 @@  +<sect1 id="menc-feat-quicktime-7"> +<title>Using <application>MEncoder</application> to create +<application>QuickTime</application>-compatible files</title> + + +<sect2 id="menc-feat-quicktime-7-why-use-it"> +<title>Why would one want to produce <application>QuickTime</application>-compatible Files?</title> + +<para> + There are several reasons why producing + <application>QuickTime</application>-compatible files can be desirable. +</para> +<itemizedlist> +<listitem><para> + You want any computer illiterate to be able to watch your encode on + any major platform (Windows, Mac OSX, Unices …). +</para></listitem> +<listitem><para> + <application>QuickTime</application> is able to take advantage of more + hardware and software acceleration features of Mac OSX than + platform-independent players like <application>MPlayer</application> + or <application>VLC</application>. + That means that your encodes have a chance to be played smoothly by older + G4-powered machines. +</para></listitem> +<listitem><para> + <application>QuickTime</application> 7 support the next-generation codec H.264, + which yields significantly better picture quality than previous codec + generations (MPEG-2, MPEG-4 …). +</para></listitem> +</itemizedlist> +</sect2> + +<sect2 id="menc-feat-quicktime-7-constraints"> +<title><application>QuickTime</application> 7 limitations</title> + +<para> + <application>QuickTime</application> 7 supports H.264 video and AAC audio, + but it does not support them muxed in AVI container format. + However, you can use <application>MEncoder</application> to encode + the video and audio, and then use an external program such as + <application>mp4creator</application> (part of the + <ulink url="http://mpeg4ip.sourceforge.net/">MPEG4IP suite</ulink>) + to remux the video and audio tracks into an MP4 container. +</para> + +<para> + <application>QuickTime</application>'s support for H.264 is limited, + so you will need to drop some advanced features. + If you encode your video with features that + <application>QuickTime</application> 7 does not support, + <application>QuickTime</application>-based players will show you a pretty + white screen instead of your expected video. +</para> + +<itemizedlist> +<listitem><para> + <emphasis role="bold">B-frames</emphasis>: + <application>QuickTime</application> 7 supports a maximum of 1 B-frame, i.e. + <option>-x264encopts bframes=1</option>. This means that + <option>b_pyramid</option> and <option>weight_b</option> will have no + effect, since they require <option>bframes</option> to be greater than 1. +</para></listitem> +<listitem><para> + <emphasis role="bold">Macroblocks</emphasis>: + <application>QuickTime</application> 7 does not support 8x8 DCT macroblocks. + This option (<option>8x8dct</option>) is off by default, so just be sure + not to explicitly enable it. This also means that the <option>i8x8</option> + option will have no effect, since it requires <option>8x8dct</option>. +</para></listitem> +<listitem><para> + <emphasis role="bold">Aspect ratio</emphasis>: + <application>QuickTime</application> 7 does not support SAR (sample + aspect ratio) information in MPEG-4 files; it assumes that SAR=1. Read + <link linkend="menc-feat-quicktime-7-scale">the section on scaling</link> + for a workaround. +</para></listitem> +</itemizedlist> + +</sect2> + +<sect2 id="menc-feat-quicktime-7-crop"> +<title>Cropping</title> +<para> + Suppose you want to rip your freshly bought copy of "The Chronicles of + Narnia" Your DVD is region 1, + which means it is NTSC. The example below would still apply to PAL, + except you would omit <option>-ofps 24000/1001</option> and use slightly + different <option>crop</option> and <option>scale</option> dimensions. +</para> + +<para> + After running <option>mplayer dvd://1</option>, you follow the process + detailed in the section <link linkend="menc-feat-telecine">How to deal + with telecine and interlacing in NTSC DVDs</link> and discover that it is + 24000/1001 fps progressive video. This simplifies the process somewhat, + since you do not need to use an inverse telecine filter such as + <option>pullup</option> or a deinterlacing filter such as + <option>yadif</option>. +</para> + +<para> + Next, you need to crop out the black bars from the top and bottom of the + video, as detailed in <link linkend="menc-feat-dvd-mpeg4-example-crop">this</link> + previous section. +</para> + +</sect2> + +<sect2 id="menc-feat-quicktime-7-scale"> +<title>Scaling</title> + +<para> + The next step is truly heartbreaking. + <application>QuickTime</application> 7 does not support MPEG-4 videos + with a sample aspect ratio other than 1, so you will need to upscale + (which wastes a lot of disk space) or downscale (which loses some + details of the source) the video to square pixels. + Either way you do it, this is highly inefficient, but simply can not + be avoided if you want your video to be playable by + <application>QuickTime</application> 7. + <application>MEncoder</application> can apply the appropriate upscaling + or downscaling by specifying respectively <option>-vf scale=-10:-1</option> + or <option>-vf scale=-1:-10</option>. + This will scale your video to the correct width for the cropped height, + rounded to the closest multiple of 16 for optimal compression. + Remember that if you are cropping, you should crop first, then scale: + + <screen>-vf crop=720:352:0:62,scale=-10:-1</screen> +</para> + +</sect2> + +<sect2 id="menc-feat-quicktime-7-avsync"> +<title>A/V sync</title> + +<para> + Because you will be remuxing into a different container, you should + always use the <option>harddup</option> option to ensure that duplicated + frames are actually duplicated in the video output. Without this option, + <application>MEncoder</application> will simply put a marker in the video + stream that a frame was duplicated, and rely on the client software to + show the same frame twice. Unfortunately, this "soft duplication" does + not survive remuxing, so the audio would slowly lose sync with the video. +</para> + +<para> + The final filter chain looks like this: + <screen>-vf crop=720:352:0:62,scale=-10:-1,harddup</screen> +</para> + +</sect2> + +<sect2 id="menc-feat-quicktime-7-bitrate"> +<title>Bitrate</title> + +<para> + As always, the selection of bitrate is a matter the technical properties + of the source, as explained + <link linkend="menc-feat-dvd-mpeg4-resolution-bitrate">here</link>, as + well as a matter of taste. + This movie has a fair bit of action and lots of detail, but H.264 video + looks good at much lower bitrates than XviD or other MPEG-4 codecs. + After much experimentation, the author of this guide chose to encode + this movie at 900kbps, and thought that it looked very good. + You may decrease bitrate if you need to save more space, or increase + it if you need to improve quality. +</para> + +</sect2> + +<sect2 id="menc-feat-quicktime-7-example"> +<title>Encoding example</title> + +<para> + You are now ready to encode the video. Since you care about + quality, of course you will be doing a two-pass encode. To shave off + some encoding time, you can specify the <option>turbo</option> option + on the first pass; this reduces <option>subq</option> and + <option>frameref</option> to 1. To save some disk space, you can + use the <option>ss</option> option to strip off the first few seconds + of the video. (I found that this particular movie has 32 seconds of + credits and logos.) <option>bframes</option> can be 0 or 1. + The other options are documented in <link + linkend="menc-feat-x264-encoding-options-speedvquality">Encoding with + the <systemitem class="library">x264</systemitem> codec</link> and + the man page. + + <screen>mencoder dvd://1 -o /dev/null -ss 32 -ovc x264 \ +-x264encopts pass=1:turbo:bitrate=900:bframes=1:\ +me=umh:4x4mv:trellis=1:qp_step=4:qcomp=0.7:direct_pred=3:keyint=300 \ +-vf crop=720:352:0:62,scale=-10:-1,harddup \ +-oac faac -faacopts br=192:mpeg=4:object=1 -channels 2 -srate 48000 \ +-ofps 24000/1001</screen> + + If you have multi-processor machine, you can add + <option>threads=auto</option>. This increases encoding speed by about + 94% per CPU core, with very little quality penalty (about 0.005dB for + dual processor, about 0.01dB for a quad processor machine). +</para> + +<para> + The second pass is the same, except that you specify the output file + and set <option>pass=2</option>. + + <screen>mencoder dvd://1 <emphasis role="bold">-o narnia.avi</emphasis> -ss 32 -ovc x264 \ +-x264encopts <emphasis role="bold">pass=2</emphasis>:turbo:bitrate=900:frameref=5:bframes=1:\ +me=umh:4x4mv:trellis=1:qp_step=4:qcomp=0.7:direct_pred=3:keyint=300 \ +-vf crop=720:352:0:62,scale=-10:-1,harddup \ +-oac faac -faacopts br=192:mpeg=4:object=1 -channels 2 -srate 48000 \ +-ofps 24000/1001</screen> +</para> + +<para> + The resulting AVI should play perfectly in + <application>MPlayer</application>, but of course + <application>QuickTime</application> can not play it because it does + not support H.264 muxed in AVI. + So the next step is to remux the video into an MP4 container. +</para> +</sect2> + +<sect2 id="menc-feat-quicktime-7-remux"> +<title>Remuxing as MP4</title> + +<para> + There are several ways to remux AVI files to MP4. You can use + <application>mp4creator</application>, which is part of the + <ulink url="http://mpeg4ip.sourceforge.net/">MPEG4IP suite</ulink>. +</para> + +<para> + First, demux the AVI into separate audio and video streams using + <application>MPlayer</application>. + + <screen>mplayer narnia.avi -dumpaudio -dumpfile narnia.aac +mplayer narnia.avi -dumpvideo -dumpfile narnia.h264</screen> + + The filenames are important; <application>mp4creator</application> + requires that AAC audio streams be named <systemitem>.aac</systemitem> + and H.264 video streams be named <systemitem>.h264</systemitem>. +</para> + +<para> + Now use <application>mp4creator</application> to create a new + MP4 file out of the audio and video streams. + + <screen>mp4creator -create=narnia.aac narnia.mp4 +mp4creator -create=narnia.h264 -rate=23.976 narnia.mp4</screen> + + Unlike the encoding step, you must specify the framerate as a + decimal (such as 23.976), not a fraction (such as 24000/1001). +</para> + +<para> + This <systemitem>narnia.mp4</systemitem> file should now be playable + with any <application>QuickTime</application> 7 application, such as + <application>QuickTime Player</application> or + <application>iTunes</application>. If you are planning to view the + video in a web browser with the <application>QuickTime</application> + plugin, you should also hint the movie so that the + <application>QuickTime</application> plugin can start playing it + while it is still downloading. <application>mp4creator</application> + can create these hint tracks: + + <screen>mp4creator -hint=1 narnia.mp4 +mp4creator -hint=2 narnia.mp4 +mp4creator -optimize narnia.mp4</screen> + + You can check the final result to ensure that the hint tracks were + created successfully: + + <screen>mp4creator -list narnia.mp4</screen> + + You should see a list of tracks: 1 audio, 1 video, and 2 hint tracks. + +<screen>Track Type Info +1 audio MPEG-4 AAC LC, 8548.714 secs, 190 kbps, 48000 Hz +2 video H264 Main(a)5.1, 8549.132 secs, 899 kbps, 848x352 @ 23.976001 fps +3 hint Payload mpeg4-generic for track 1 +4 hint Payload H264 for track 2 +</screen> +</para> + +</sect2> + +<sect2 id="menc-feat-quicktime-7-metadata"> +<title>Adding metadata tags</title> + +<para> + If you want to add tags to your video that show up in iTunes, you can use + <ulink url="http://atomicparsley.sourceforge.net/">AtomicParsley</ulink>. + + <screen>AtomicParsley narnia.mp4 --metaEnema --title "The Chronicles of Narnia" --year 2005 --stik Movie --freefree --overWrite</screen> + + The <option>--metaEnema</option> option removes any existing metadata + (<application>mp4creator</application> inserts its name in the + "encoding tool" tag), and <option>--freefree</option> reclaims the + space from the deleted metadata. + The <option>--stik</option> option sets the type of video (such as Movie + or TV Show), which iTunes uses to group related video files. + The <option>--overWrite</option> option overwrites the original file; + without it, <application>AtomicParsley</application> creates a new + auto-named file in the same directory and leaves the original file + untouched. +</para> + +</sect2> + +</sect1> + + + + + <sect1 id="menc-feat-video-for-windows"> <title> Encoding with the <systemitem class="library">Video For Windows</systemitem>

6 7

r21934 - trunk/DOCS/xml/en/encoding-guide.xml
by gpoirier 15 Jan '07

15 Jan '07

Author: gpoirier Date: Mon Jan 15 10:15:06 2007 New Revision: 21934 Modified: trunk/DOCS/xml/en/encoding-guide.xml Log: get rid of two spaces after a period (instead of one) Modified: trunk/DOCS/xml/en/encoding-guide.xml ============================================================================== --- trunk/DOCS/xml/en/encoding-guide.xml (original) +++ trunk/DOCS/xml/en/encoding-guide.xml Mon Jan 15 10:15:06 2007 @@ -4165,7 +4165,7 @@ <listitem><para> <emphasis role="bold">B-frames</emphasis>: <application>QuickTime</application> 7 supports a maximum of 1 B-frame, i.e. - <option>-x264encopts bframes=1</option>. This means that + <option>-x264encopts bframes=1</option>. This means that <option>b_pyramid</option> and <option>weight_b</option> will have no effect, since they require <option>bframes</option> to be greater than 1. </para></listitem> @@ -4173,13 +4173,13 @@ <emphasis role="bold">Macroblocks</emphasis>: <application>QuickTime</application> 7 does not support 8x8 DCT macroblocks. This option (<option>8x8dct</option>) is off by default, so just be sure - not to explicitly enable it. This also means that the <option>i8x8</option> + not to explicitly enable it. This also means that the <option>i8x8</option> option will have no effect, since it requires <option>8x8dct</option>. </para></listitem> <listitem><para> <emphasis role="bold">Aspect ratio</emphasis>: <application>QuickTime</application> 7 does not support SAR (sample - aspect ratio) information in MPEG-4 files; it assumes that SAR=1. Read + aspect ratio) information in MPEG-4 files; it assumes that SAR=1. Read <link linkend="menc-feat-quicktime-7-scale">the section on scaling</link> for a workaround. </para></listitem> @@ -4192,7 +4192,7 @@ <para> Suppose you want to rip your freshly bought copy of "The Chronicles of Narnia". Your DVD is region 1, - which means it is NTSC. The example below would still apply to PAL, + which means it is NTSC. The example below would still apply to PAL, except you would omit <option>-ofps 24000/1001</option> and use slightly different <option>crop</option> and <option>scale</option> dimensions. </para> @@ -4201,7 +4201,7 @@ After running <option>mplayer dvd://1</option>, you follow the process detailed in the section <link linkend="menc-feat-telecine">How to deal with telecine and interlacing in NTSC DVDs</link> and discover that it is - 24000/1001 fps progressive video. This simplifies the process somewhat, + 24000/1001 fps progressive video. This simplifies the process somewhat, since you do not need to use an inverse telecine filter such as <option>pullup</option> or a deinterlacing filter such as <option>yadif</option>. @@ -4245,10 +4245,10 @@ <para> Because you will be remuxing into a different container, you should always use the <option>harddup</option> option to ensure that duplicated - frames are actually duplicated in the video output. Without this option, + frames are actually duplicated in the video output. Without this option, <application>MEncoder</application> will simply put a marker in the video stream that a frame was duplicated, and rely on the client software to - show the same frame twice. Unfortunately, this "soft duplication" does + show the same frame twice. Unfortunately, this "soft duplication" does not survive remuxing, so the audio would slowly lose sync with the video. </para> @@ -4281,13 +4281,13 @@ <title>Encoding example</title> <para> - You are now ready to encode the video. Since you care about - quality, of course you will be doing a two-pass encode. To shave off + You are now ready to encode the video. Since you care about + quality, of course you will be doing a two-pass encode. To shave off some encoding time, you can specify the <option>turbo</option> option on the first pass; this reduces <option>subq</option> and - <option>frameref</option> to 1. To save some disk space, you can + <option>frameref</option> to 1. To save some disk space, you can use the <option>ss</option> option to strip off the first few seconds - of the video. (I found that this particular movie has 32 seconds of + of the video. (I found that this particular movie has 32 seconds of credits and logos.) <option>bframes</option> can be 0 or 1. The other options are documented in <link linkend="menc-feat-x264-encoding-options-speedvquality">Encoding with @@ -4334,7 +4334,7 @@ <title>Remuxing as MP4</title> <para> - There are several ways to remux AVI files to MP4. You can use + There are several ways to remux AVI files to MP4. You can use <application>mp4creator</application>, which is part of the <ulink url="http://mpeg4ip.sourceforge.net/">MPEG4IP suite</ulink>. </para> @@ -4366,7 +4366,7 @@ This <systemitem>narnia.mp4</systemitem> file should now be playable with any <application>QuickTime</application> 7 application, such as <application>QuickTime Player</application> or - <application>iTunes</application>. If you are planning to view the + <application>iTunes</application>. If you are planning to view the video in a web browser with the <application>QuickTime</application> plugin, you should also hint the movie so that the <application>QuickTime</application> plugin can start playing it

1 0