From 000a6730404a157d6f0003828488e5659d0c6d86 Mon Sep 17 00:00:00 2001 From: diego Date: Tue, 27 Apr 2004 17:43:18 +0000 Subject: Hint about testing different colorspaces and putting codes in ./, based on a patch by Compn. git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@12326 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/xml/en/ports.xml | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) (limited to 'DOCS/xml') diff --git a/DOCS/xml/en/ports.xml b/DOCS/xml/en/ports.xml index 5588710391..483ef05209 100644 --- a/DOCS/xml/en/ports.xml +++ b/DOCS/xml/en/ports.xml @@ -295,6 +295,20 @@ since QNX has only X emulation which is VERY slow. Use SDL. 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 @@ since QNX has only X emulation which is VERY slow. Use SDL. 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 -- cgit v1.2.3