summaryrefslogtreecommitdiffstats
path: root/DOCS/xml/it/encoding-guide.xml
diff options
context:
space:
mode:
Diffstat (limited to 'DOCS/xml/it/encoding-guide.xml')
-rw-r--r--DOCS/xml/it/encoding-guide.xml44
1 files changed, 22 insertions, 22 deletions
diff --git a/DOCS/xml/it/encoding-guide.xml b/DOCS/xml/it/encoding-guide.xml
index 1c6850fd99..e0f1f4da07 100644
--- a/DOCS/xml/it/encoding-guide.xml
+++ b/DOCS/xml/it/encoding-guide.xml
@@ -1398,7 +1398,7 @@ tecniche in gioco.
codifica.
Questo è semplicemente il contrappasso per usare la tecnologia di punta.
</para>
-
+
<para>
Inoltre iniziare ad utilizzare un codec nuovo richiede l'utilizzo di un po'
di tempo per familiarizzare con le sue opzioni, affinché tu sappia cosa
@@ -1431,14 +1431,14 @@ tecniche in gioco.
codifica. Tuttavia, possono avere delle opzioni avanzate che, quando
abilitate, rendono la codifica molto lenta fornendo poco guadagno.
</para>
-
+
<para>
Se stai cercando di incrementare la velocità dovresti cercare di non
modificare troppo le impostazioni di default del codec video (anche se
dovresti comunque provare le altre opzioni che sono citate in altre sezioni
di questa guida).
</para>
-
+
<para>
Puoi tenere in considerazione anche la scelta di un codec che possa eseguire
elaborazioni multi-thread, anche se ciò è utile solo per utenti di macchine
@@ -1884,7 +1884,7 @@ campo dopo l'altro.
non è lo scopo di questa documentazione.
</para></listitem>
<listitem><para>
- Ci sono alcune note a piè di pagina specifiche di questa guida, così
+ Ci sono alcune note a piè di pagina specifiche di questa guida, così
indicate:
<link linkend="menc-feat-telecine-footnotes">[1]</link>
</para></listitem>
@@ -2089,7 +2089,7 @@ Se non lo usi, <application>MEncoder</application> cercherà di codificare a
<para>
Spesso e volentieri capita che un video che sembra progressivo contenga anche
alcune brevi parti di telecine mescolate. A meno che tu non sia sicuro,
-conviene trattare il video come
+conviene trattare il video come
<link linkend="menc-feat-telecine-encode-mixedpt">progressivo e telecine mescolati</link>.
Il calo di prestazioni è piccolo
<link linkend="menc-feat-telecine-footnotes">[3]</link>.
@@ -2217,7 +2217,7 @@ uscita sarà a 24000/1001 fotogrammi al secondo.
<option>pullup</option> è tuttavia il modo migliore e più preciso disponibile
per codificare sia telecine che "progressivo e telecine mescolati".
<screen>
-mencoder dvd://1 -oac copy -vf pullup,softskip
+mencoder dvd://1 -oac copy -vf pullup,softskip
-ovc lavc -ofps 24000/1001<!--
--></screen>
</para></listitem>
@@ -3769,7 +3769,7 @@ random differences in the achieved bitrate.
This option is for choosing the motion estimation search method.
Altering this option provides a straightforward quality-vs-speed
tradeoff. <option>me=dia</option> is only a few percent faster than
- the default search, at a cost of under 0.1dB global PSNR. The
+ the default search, at a cost of under 0.1dB global PSNR. The
default setting (<option>me=hex</option>) is a reasonable tradeoff
between speed and quality. <option>me=umh</option> gains a little under
0.1dB global PSNR, with a speed penalty that varies depending on
@@ -3998,7 +3998,7 @@ random differences in the achieved bitrate.
(understanding that there are diminishing returns which may become
vanishingly low, or even zero). The video stream will still have seekable
points as long as there are some scene changes.
-</para></listitem>
+</para></listitem>
<listitem>
<para>
<emphasis role="bold">deblock</emphasis>:
@@ -4314,17 +4314,17 @@ and other options. This is known to work on x86 on both *NIX and Windows.
</para>
<para>
First you must build the <application>vfw2menc</application> program.
-It is located in the <filename class="directory">TOOLS</filename> subdirectory
+It is located in the <filename class="directory">TOOLS</filename> subdirectory
of the MPlayer source tree.
To build on Linux, this can be done using <application>Wine</application>:
<screen>winegcc vfw2menc.c -o vfw2menc -lwinmm -lole32</screen>
-To build on Windows in <application>MinGW</application> or
+To build on Windows in <application>MinGW</application> or
<application>Cygwin</application> use:
<screen>gcc vfw2menc.c -o vfw2menc.exe -lwinmm -lole32</screen>
To build on <application>MSVC</application> you will need getopt.
-Getopt can be found in the original <application>vfw2menc</application>
+Getopt can be found in the original <application>vfw2menc</application>
archive available at:
The <ulink url="http://oss.netfarm.it/mplayer-win32.php">MPlayer on win32</ulink> project.
</para>
@@ -4334,13 +4334,13 @@ Below is an example with the VP6 codec.
<screen>
vfw2menc -f VP62 -d vp6vfw.dll -s firstpass.mcf
</screen>
-This will open the VP6 codec dialog window.
+This will open the VP6 codec dialog window.
Repeat this step for the second pass
and use <option>-s <replaceable>secondpass.mcf</replaceable></option>.
</para>
</informalexample>
<para>
-Windows users can use
+Windows users can use
<option>-xvfwopts codec=vp6vfw.dll:compdata=dialog</option> to have
the codec dialog display before encoding starts.
</para>
@@ -4645,11 +4645,11 @@ mp4creator -optimize narnia.mp4</screen>
<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
+ (<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
@@ -4717,7 +4717,7 @@ compliant.
<tbody>
<row>
<entry>NTSC DVD</entry>
- <entry>720x480, 704x480, 352x480, 352x240</entry>
+ <entry>720x480, 704x480, 352x480, 352x240</entry>
<entry>MPEG-2</entry>
<entry>9800 kbps</entry>
<entry>48000 Hz</entry>
@@ -4730,7 +4730,7 @@ compliant.
<entry>NTSC DVD</entry>
<entry>352x240<footnote id='fn-rare-resolutions'><para>
These resolutions are rarely used for DVDs because
- they are fairly low quality.</para></footnote></entry>
+ they are fairly low quality.</para></footnote></entry>
<entry>MPEG-1</entry>
<entry>1856 kbps</entry>
<entry>48000 Hz</entry>
@@ -4825,7 +4825,7 @@ highly bitrate-starved and require effort to obtain acceptable quality.
<title>GOP Size Constraints</title>
<para>
-DVD, VCD, and SVCD also constrain you to relatively low
+DVD, VCD, and SVCD also constrain you to relatively low
GOP (Group of Pictures) sizes.
For 30 fps material the largest allowed GOP size is 18.
For 25 or 24 fps, the maximum is 15.
@@ -4841,7 +4841,7 @@ The GOP size is set using the <option>keyint</option> option.
VCD video is required to be CBR at 1152 kbps.
This highly limiting constraint also comes along with an extremly low vbv
buffer size of 327 kilobits.
-SVCD allows varying video bitrates up to 2500 kbps, and a somewhat less
+SVCD allows varying video bitrates up to 2500 kbps, and a somewhat less
restrictive vbv buffer size of 917 kilobits is allowed.
DVD video bitrates may range anywhere up to 9800 kbps (though typical
bitrates are about half that), and the vbv buffer size is 1835 kilobits.
@@ -4888,7 +4888,7 @@ DVD (with timestamps on every frame, if possible):
<para>
DVD with NTSC Pullup:
<screen>-of mpeg -mpegopts format=dvd:tsaf:telecine -ofps 24000/1001</screen>
-This allows 24000/1001 fps progressive content to be encoded at 30000/1001
+This allows 24000/1001 fps progressive content to be encoded at 30000/1001
fps whilst maintaing DVD-compliance.
</para>
@@ -4954,7 +4954,7 @@ or in the manual page.
<para>
If the audio sample rate in the original file is not the same as
required by the target format, sample rate conversion is required.
-This is achieved using the <option>-srate</option> option and
+This is achieved using the <option>-srate</option> option and
the <option>-af lavcresample</option> audio filter together.
</para>
@@ -5022,7 +5022,7 @@ or DVD:
Used to set the GOP size.
18 for 30fps material, or 15 for 25/24 fps material.
Commercial producers seem to prefer keyframe intervals of 12.
- It is possible to make this much larger and still retain compatibility
+ It is possible to make this much larger and still retain compatibility
with most players.
A <option>keyint</option> of 25 should never cause any problems.
</para></listitem>