# HG changeset patch # User gpoirier # Date 1120637746 0 # Node ID 5e1ea4b159d4dc777b3d81022029973606be1dff # Parent 154b64188f8eb1466fa2c121046c174b22282210 More fixes by Jeff, Diego, and Andrew diff -r 154b64188f8e -r 5e1ea4b159d4 DOCS/xml/en/faq.xml --- a/DOCS/xml/en/faq.xml Wed Jul 06 07:56:41 2005 +0000 +++ b/DOCS/xml/en/faq.xml Wed Jul 06 08:15:46 2005 +0000 @@ -1160,9 +1160,8 @@ -Since 1.0pre7, DivX encoded by MPlayer -cannot be watched on third party players because it sets 'FMP4' as a -FourCC. +Why do third-party players fail to play MPEG-4 movies encoded by +MEncoder versions later than 1.0pre7? @@ -1174,12 +1173,13 @@ This led many people to think that libavcodec 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. +MPEG-4 encoding library which implements the MPEG-4 standard much +better than DivX. Therefore, the new default FourCC used by libavcodec is 'FMP4', but you may override this behavior using MEncoder's option. -You may also change the FourCC of existing files in this same way: +You may also change the FourCC of existing files in the same way: mencoder input.avi -o output.avi -ffourcc XVID @@ -1189,9 +1189,9 @@ Therefore, if you change the FourCC to DIVX, some bad software or hardware players may choke on some advanced features that libavcodec supports, but DivX -doesn't, whereas XviD closer -to libavcodec in terms of -functionalities, and is supported but all decent players. +doesn't; on the other hand XviD +is closer to libavcodec in +terms of functionality, and is supported by all decent players.