mirror of https://github.com/mpv-player/mpv
Suggestions and fixes by The Wanderer and Rich
git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@15923 b3059339-0415-0410-9bf9-f77b7e298cf2
This commit is contained in:
parent
e0323721f5
commit
7bde74f07f
|
@ -1167,21 +1167,31 @@ FourCC.
|
||||||
|
|
||||||
<answer><para>
|
<answer><para>
|
||||||
<systemitem class="library">libavcodec</systemitem>, the native MPEG-4
|
<systemitem class="library">libavcodec</systemitem>, the native MPEG-4
|
||||||
encoding library usually shipped with <application>MEncoder</application>
|
encoding library usually shipped with <application>MEncoder</application>,
|
||||||
used to set the 'DIVX' FourCC (which is an AVI tag to identify the
|
used to set the FourCC to 'DIVX' when encoding MPEG-4 videos
|
||||||
software used to encode and the intended software to use for decoding)
|
(the FourCC is an AVI tag to identify the software used to encode and
|
||||||
when encoding MPEG-4 videos, which lead to make many people think that
|
the intended software to use for decoding the video).
|
||||||
<systemitem class="library">libavcodec</systemitem> was a DivX encoding
|
This led many people to think that
|
||||||
library, when in fact it is just another MPEG-4 encoding library whose
|
<systemitem class="library">libavcodec</systemitem>
|
||||||
MPEG-4 support is much better than DivX's.
|
was a DivX encoding library, when in fact it is a completely different
|
||||||
|
MPEG-4 encoding library whose MPEG-4 support is much better than DivX's.
|
||||||
Therefore, the new default FourCC used by
|
Therefore, the new default FourCC used by
|
||||||
<systemitem class="library">libavcodec</systemitem> is 'FMP4', but you
|
<systemitem class="library">libavcodec</systemitem> is 'FMP4', but you
|
||||||
may override this behavior using <application>MEncoder</application>'s
|
may override this behavior using <application>MEncoder</application>'s
|
||||||
<option>-ffourcc</option>.
|
<option>-ffourcc</option> option.
|
||||||
You may also change the FourCC of existing files like this:
|
You may also change the FourCC of existing files in this same way:
|
||||||
<screen>
|
<screen>
|
||||||
mencoder <replaceable>input.avi</replaceable> -o <replaceable>output.avi</replaceable> -ffourcc DIVX
|
mencoder <replaceable>input.avi</replaceable> -o <replaceable>output.avi</replaceable> -ffourcc XVID
|
||||||
</screen>
|
</screen>
|
||||||
|
Note that this will set the FourCC as XVID rather than as DIVX.
|
||||||
|
This is recommended as DIVX FourCC means DivX4, which is a very basic
|
||||||
|
MPEG-4 codec, whereas DX50 and XVID both mean full MPEG-4 (ASP).
|
||||||
|
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, whereas <systemitem class="library">XviD</systemitem> closer
|
||||||
|
to <systemitem class="library">libavcodec</systemitem> in terms of
|
||||||
|
functionalities, and is supported but all decent players.
|
||||||
</para></answer>
|
</para></answer>
|
||||||
</qandaentry>
|
</qandaentry>
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue