Mercurial > mplayer.hg
comparison DOCS/xml/en/encoding-guide.xml @ 16340:5ceeeb85804c
Avoid short forms.
author | diego |
---|---|
date | Thu, 01 Sep 2005 23:53:33 +0000 |
parents | 9d772123c27d |
children | f71d1d8468df |
comparison
equal
deleted
inserted
replaced
16339:9d772123c27d | 16340:5ceeeb85804c |
---|---|
1201 25 fps things will sound right, even though the audio track (and hence the | 1201 25 fps things will sound right, even though the audio track (and hence the |
1202 whole movie) has a running time that is 4% less than NTSC DVDs. | 1202 whole movie) has a running time that is 4% less than NTSC DVDs. |
1203 </para> | 1203 </para> |
1204 | 1204 |
1205 <para> | 1205 <para> |
1206 Because the video in a PAL DVD has not been altered, you needn't worry | 1206 Because the video in a PAL DVD has not been altered, you need not worry |
1207 much about framerate. The source is 25 fps, and your rip will be 25 | 1207 much about framerate. The source is 25 fps, and your rip will be 25 |
1208 fps. However, if you are ripping an NTSC DVD movie, you may need to | 1208 fps. However, if you are ripping an NTSC DVD movie, you may need to |
1209 apply inverse telecine. | 1209 apply inverse telecine. |
1210 </para> | 1210 </para> |
1211 | 1211 |
2456 | 2456 |
2457 <para> | 2457 <para> |
2458 After running <option>mplayer dvd://1</option>, we follow the process | 2458 After running <option>mplayer dvd://1</option>, we follow the process |
2459 detailed in the section <link linkend="menc-feat-telecine">How to deal | 2459 detailed in the section <link linkend="menc-feat-telecine">How to deal |
2460 with telecine and interlacing in NTSC DVDs</link> and discover that it is | 2460 with telecine and interlacing in NTSC DVDs</link> and discover that it is |
2461 24000/1001 fps progressive video, which means that we needn't use an inverse | 2461 24000/1001 fps progressive video, which means that we need not use an inverse |
2462 telecine filter, such as <option>pullup</option> or | 2462 telecine filter, such as <option>pullup</option> or |
2463 <option>filmdint</option>. | 2463 <option>filmdint</option>. |
2464 </para> | 2464 </para> |
2465 | 2465 |
2466 <para> | 2466 <para> |
3078 exact same set of options on both passes, two pass encoding is almost | 3078 exact same set of options on both passes, two pass encoding is almost |
3079 twice as slow. | 3079 twice as slow. |
3080 </para> | 3080 </para> |
3081 <para> | 3081 <para> |
3082 Still, there are very good reasons for using two pass encoding. For | 3082 Still, there are very good reasons for using two pass encoding. For |
3083 one thing, single pass ratecontrol isn't psychic, and it often makes | 3083 one thing, single pass ratecontrol is not psychic, and it often makes |
3084 unreasonable choices because it can't see the big picture. For example, | 3084 unreasonable choices because it cannot see the big picture. For example, |
3085 suppose you have a two minute long video consisting of two distinct | 3085 suppose you have a two minute long video consisting of two distinct |
3086 halves. The first half is a very high-motion scene lasting 60 seconds | 3086 halves. The first half is a very high-motion scene lasting 60 seconds |
3087 which, in isolation, requires about 2500kbps in order to look decent. | 3087 which, in isolation, requires about 2500kbps in order to look decent. |
3088 Immediately following it is a much less demanding 60-second scene | 3088 Immediately following it is a much less demanding 60-second scene |
3089 that looks good at 300kbps. Suppose you ask for 1400kbps on the theory | 3089 that looks good at 300kbps. Suppose you ask for 1400kbps on the theory |
3091 will make a couple of "mistakes" in such a case. First of all, it | 3091 will make a couple of "mistakes" in such a case. First of all, it |
3092 will target 1400kbps in both segments. The first segment may end up | 3092 will target 1400kbps in both segments. The first segment may end up |
3093 heavily overquantized, causing it to look unacceptably and unreasonably | 3093 heavily overquantized, causing it to look unacceptably and unreasonably |
3094 blocky. The second segment will be heavily underquantized; it may look | 3094 blocky. The second segment will be heavily underquantized; it may look |
3095 perfect, but the bitrate cost of that perfection will be completely | 3095 perfect, but the bitrate cost of that perfection will be completely |
3096 unreasonable. What's even harder to avoid is the problem at the | 3096 unreasonable. What is even harder to avoid is the problem at the |
3097 transition between the two scenes. The first seconds of the low motion | 3097 transition between the two scenes. The first seconds of the low motion |
3098 half will be hugely over-quantized, because the ratecontrol is still | 3098 half will be hugely over-quantized, because the ratecontrol is still |
3099 expecting the kind of bitrate requirements it met in the first half | 3099 expecting the kind of bitrate requirements it met in the first half |
3100 of the video. This "error period" of heavily over-quantized low motion | 3100 of the video. This "error period" of heavily over-quantized low motion |
3101 will look jarringly bad, and will actually use less than the 300kbps | 3101 will look jarringly bad, and will actually use less than the 300kbps |
3153 bitrate. Typically this would make high-motion scenes look completely | 3153 bitrate. Typically this would make high-motion scenes look completely |
3154 awful, while low-motion scenes would probably look absolutely | 3154 awful, while low-motion scenes would probably look absolutely |
3155 perfect, but would also use many times more bitrate than they | 3155 perfect, but would also use many times more bitrate than they |
3156 would need in order to look merely excellent. At the other extreme, | 3156 would need in order to look merely excellent. At the other extreme, |
3157 <option>qcomp=1</option> achieves nearly constant quantization parameter | 3157 <option>qcomp=1</option> achieves nearly constant quantization parameter |
3158 (QP). Constant QP doesn't look bad, but most people think it's more | 3158 (QP). Constant QP does not look bad, but most people think it is more |
3159 reasonable to shave some bitrate off of the extremely expensive scenes | 3159 reasonable to shave some bitrate off of the extremely expensive scenes |
3160 (where the loss of quality isn't as noticeable) and reallocate it to | 3160 (where the loss of quality is not as noticeable) and reallocate it to |
3161 the scenes that are easier to encode at excellent quality. | 3161 the scenes that are easier to encode at excellent quality. |
3162 <option>qcomp</option> is set to 0.6 by default, which may be slightly | 3162 <option>qcomp</option> is set to 0.6 by default, which may be slightly |
3163 low for many peoples' taste (0.7-0.8 are also commonly used). | 3163 low for many peoples' taste (0.7-0.8 are also commonly used). |
3164 </para></listitem> | 3164 </para></listitem> |
3165 <listitem><para> | 3165 <listitem><para> |