# HG changeset patch # User diego # Date 1083087798 0 # Node ID 9e5ebd0c97d02bcf138ee3aab1f210cbddc8ce46 # Parent fa573cfa912db16239057392441611e8d727fb67 Hint about testing different colorspaces and putting codes in ./, based on a patch by Compn. diff -r fa573cfa912d -r 9e5ebd0c97d0 DOCS/xml/en/ports.xml --- a/DOCS/xml/en/ports.xml Tue Apr 27 17:01:00 2004 +0000 +++ b/DOCS/xml/en/ports.xml Tue Apr 27 17:43:18 2004 +0000 @@ -295,6 +295,20 @@ DirectX 7 header files to compile the DirectX video output driver. +For best results MPlayer should use a + colorspace that your video card supports in hardware. Unfortunately many + Windows graphics drivers wrongly report some colorspaces as supported in + hardware. To find out which, try + + mplayer -benchmark -nosound -frames 100 -vf format=colorspace movie + + where colorspace can be any colorspace + printed by the option. If you + find a colorspace your card handles particularly bad + + will keep it from being used. Add this to your config file to permanently + keep it from being used. + You can use Win32 codecs and Real Win32 codecs (not Real Linux codecs) if you want to. Put the codecs somewhere in your path or pass (alternatively @@ -305,7 +319,8 @@ them writable if you have problems. QuickTime DLLs also work, but you will have to put them in your Windows system directory (C:\Windows\system\ - or similar). + or similar). As a last resort, try putting them in the same directory as + MPlayer. The Cygwin/MinGW console is rather slow. Redirecting output or using the