Mercurial > mplayer.hg
changeset 11913:60a38618e6e4
duplicate words and spaces removed
author | nicolas |
---|---|
date | Mon, 02 Feb 2004 22:07:28 +0000 |
parents | 8eb96d751dcd |
children | 47f653a0edd2 |
files | DOCS/xml/en/mencoder.xml |
diffstat | 1 files changed, 8 insertions(+), 8 deletions(-) [+] |
line wrap: on
line diff
--- a/DOCS/xml/en/mencoder.xml Mon Feb 02 19:51:39 2004 +0000 +++ b/DOCS/xml/en/mencoder.xml Mon Feb 02 22:07:28 2004 +0000 @@ -965,7 +965,7 @@ <title>Mixed progressive and interlaced</title> <para> In "mixed progressive and interlaced" content, progressive - and interlaced video have been have been spliced together. + and interlaced video have been spliced together. </para> <para> @@ -1050,12 +1050,12 @@ <listitem><para> Use a deinterlacing filter before encoding. There are several of these filters available to choose from, each with its own advantages - and disadvantages. Consult <option>mplayer -pphelp</option> to see + and disadvantages. Consult <option>mplayer -pphelp</option> to see what's available (grep for "deint"), and search the <ulink url="http://www.mplayerhq.hu/homepage/design6/info.html#mailing_lists"> MPlayer mailing lists</ulink> to find many discussions about the various filters. Again, the framerate is not changing, so no - <option>-ofps</option>. Also, deinterlacing should be done after + <option>-ofps</option>. Also, deinterlacing should be done after cropping <link linkend="menc-feat-telecine-footnotes">[1]</link> and before scaling. @@ -1080,7 +1080,7 @@ use this method, then Reference the manual, and chose whichever option looks best for your material. Note that when using <option>tfields</option> you - <emphasis role="bold">have to </emphasis> specify both + <emphasis role="bold">have to</emphasis> specify both <option>-fps</option> and <option>-ofps</option> to be twice the framerate of your original source. @@ -1091,7 +1091,7 @@ only one of the two fields. Of course, you'll lose half the vertical resolution, but if you plan on downscaling to at most 1/2 of the original, the loss won't matter much. The result will be a - progressive 29.97 frames per second file. The procedure is to use + progressive 29.97 frames per second file. The procedure is to use <option>-vf field</option>, then crop <link linkend="menc-feat-telecine-footnotes">[1]</link> and scale appropriately. Remember that you'll have to adjust the scale to @@ -1116,7 +1116,7 @@ Currently the most reliable method to deal with this type of video is to, rather than inverse-telecine the telecined parts, telecine the non-telecined parts and then inverse-telecine the whole - video. Sound confusing? softpulldown is a filter that goes through + video. Sound confusing? softpulldown is a filter that goes through a video and makes the entire file telecined. If we follow softpulldown with either <option>detc</option> or <option>ivtc</option>, the final result will be entirely @@ -1139,7 +1139,7 @@ <application>MEncoder's</application> behavior of dropping frames to maintain synchronization between the audio and video: it drops frames before sending them through the filter chain, rather than - after. As a result, <option>pullup</option> is sometimes deprived + after. As a result, <option>pullup</option> is sometimes deprived of the data it needs. </para> @@ -1255,7 +1255,7 @@ <para> When you are dealing with interlaced YUV 4:2:0, the situation is a bit more complicated. Instead of every four luma pixels in the - <emphasis>frame </emphasis> sharing a chroma pixel, every four luma + <emphasis>frame</emphasis> sharing a chroma pixel, every four luma pixels in each <emphasis> field</emphasis> share a chroma pixel. When fields are interlaced to form a frame, each scanline is one pixel high. Now, instead of all four luma pixels being in a