# HG changeset patch
# User gpoirier
# Date 1120580356 0
# Node ID c821dbc2c21b0c844735a30cbfe777a502823623
# Parent  e5bc2812c4a008f91b1a78b96d51bd5521b3b5d2
New FAQ entry: Explain why libavcodec now sets FMP4 FourCC, and how to enventualy change it.

diff -r e5bc2812c4a0 -r c821dbc2c21b DOCS/xml/en/faq.xml
--- a/DOCS/xml/en/faq.xml	Tue Jul 05 14:57:48 2005 +0000
+++ b/DOCS/xml/en/faq.xml	Tue Jul 05 16:19:16 2005 +0000
@@ -1158,6 +1158,33 @@
 </para></answer>
 </qandaentry>
 
+<qandaentry>
+<question><para>
+Since 1.0pre7, DivX encoded by <application>MPlayer</application>
+cannot be watched on third party players because it sets 'FMP4' as a
+FourCC.
+</para></question>
+
+<answer><para>
+<systemitem class="library">libavcodec</systemitem>, the native MPEG-4
+encoding library usually shipped with <application>MEncoder</application>
+used to set the 'DIVX' FourCC (which is an AVI tag to identify the
+software used to encode and the intended software to use for decoding)
+when encoding MPEG-4 videos, which lead to make many people think that
+<systemitem class="library">libavcodec</systemitem> was a DivX encoding
+library, when in fact it is just another MPEG-4 encoding library whose
+MPEG-4 support is much better than DivX's.
+Therefore, the new default FourCC used by
+<systemitem class="library">libavcodec</systemitem> is 'FMP4', but you
+may override this behavior using <application>MEncoder</application>'s
+<option>-ffourcc</option>.
+You may also change the FourCC of existing files like this:
+<screen>
+  mencoder <replaceable>input.avi</replaceable> -o <replaceable>output.avi</replaceable> -ffourcc DIVX
+</screen>
+</para></answer>
+</qandaentry>
+
 </qandadiv>
 </qandaset>