From 3be0851da3391931c41bfa83180debede5e8188d Mon Sep 17 00:00:00 2001 From: gpoirier Date: Wed, 6 Jul 2005 08:15:46 +0000 Subject: [PATCH] More fixes by Jeff, Diego, and Andrew git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@15926 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/xml/en/faq.xml | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/DOCS/xml/en/faq.xml b/DOCS/xml/en/faq.xml index 05df8c6aa4..49ab40a765 100644 --- a/DOCS/xml/en/faq.xml +++ b/DOCS/xml/en/faq.xml @@ -1160,9 +1160,8 @@ above command. -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 @@ the intended software to use for decoding the video). 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 @@ 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 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.