Win32 codecs importing HOWTO

# HG changeset patch # User diego # Date 1230388722 0 # Node ID d093bee92b15068551985c6f203a3d2c1637a1f5 # Parent 4c9698666a4c087d95de57bc8dd97be3a5675dbd Convert Win32 codec importing HOWTO into a text document in the tech section. diff -r 4c9698666a4c -r d093bee92b15 DOCS/tech/win32-codec-howto.txt --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/DOCS/tech/win32-codec-howto.txt Sat Dec 27 14:38:42 2008 +0000 @@ -0,0 +1,87 @@ +============================ +Win32 codecs importing HOWTO +============================ + +This document describes how to extract the information necessary to hook +up Win32 binary codecs in MPlayer from a Windows system. Different methods +exist depending on which video API your codec uses and which Windows +version you have. + +If you have gathered all the necessary information (fourcc, GUID, codec file, +sample file) as described below, notify the mplayer-dev-eng mailing list. +If you want to add a codec yourself, read DOCS/tech/codecs.conf.txt. + + + +VFW codecs +~~~~~~~~~~ + +VFW (Video for Windows) is the old video API for Windows. Its codecs have +the '.dll' or (rarely) '.drv' extension. If MPlayer fails at playing your +AVI with this kind of message: + +UNKNOWN video codec: HFYU (0x55594648) + +It means your AVI is encoded with a codec which has the HFYU fourcc (HFYU = +HuffYUV codec, DIV3 = DivX Low Motion, etc.). Now that you know this, you +have to find out which DLL Windows loads in order to play this file. In our +case, the 'system.ini' contains this information in a line that reads: + +VIDC.HFYU=huffyuv.dll + +So you need the 'huffyuv.dll' file. Note that the audio codecs are +specified by the MSACM prefix: + +msacm.l3acm=L3codeca.acm + +This is the MP3 codec. + + + +DirectShow codecs: +~~~~~~~~~~~~~~~~~~ + +DirectShow is the newer video API, which is even worse than its predecessor. +Things are harder with DirectShow, since 'system.ini' does not contain the +needed information, instead it is stored in the registry and we need the +GUID of the codec. + + +New Method: +----------- + +Using Microsoft GraphEdit (fast) + +- Get GraphEdit from either DirectX SDK or doom9. +- Start 'graphedit.exe'. +- From the menu select "Graph -> Insert Filters". +- Expand item "DirectShow Filters". +- Select the right codec name and expand item. +- In the entry "DisplayName" look at the text in winged brackets after the + backslash and write it down (five dash-delimited blocks, the GUID). +- The codec binary is the file specified in the "Filename" entry. + +If there is no "Filename" and "DisplayName" contains something like +'device:dmo', then it is a DMO-Codec. + + +Old Method: +----------- + +Take a deep breath and start searching the registry... + +- Start 'regedit'. +- Press "Ctrl-F", disable the first two checkboxes, and enable the third. + Type in the fourcc of the codec (e.g. "TM20"). +- You should see a field which contains the path and the filename (e.g. + "C:\WINDOWS\SYSTEM\TM20DEC.AX"). +- Now that you have the file, we need the GUID. Try searching again, but + now search for the codec's name, not the fourcc. Its name can be acquired + when Media Player is playing the file, by checking + "File -> Properties -> Advanced". + If not, you are out of luck. Try guessing (e.g. search for TrueMotion). +- If the GUID is found you should see a "FriendlyName" and a "CLSID" field. + Write down the 16 byte CLSID, this is the GUID we need. + +If searching fails, try enabling all the checkboxes. You may have +false hits, but you may get lucky... diff -r 4c9698666a4c -r d093bee92b15 DOCS/xml/en/codecs.xml --- a/DOCS/xml/en/codecs.xml Sat Dec 27 13:58:20 2008 +0000 +++ b/DOCS/xml/en/codecs.xml Sat Dec 27 14:38:42 2008 +0000 @@ -12,8 +12,8 @@ -If you have a Win32 codec which is not supported yet, -please read the codec importing HOWTO +If you have a Win32 codec which is not supported yet, please read the +Win32 codec HOWTO and help us add support for it. @@ -96,161 +96,4 @@ - - - - - -Win32 codecs importing HOWTO - - - - -VFW codecs - - -VFW (Video for Windows) is the old Video API for Windows. Its codecs have -the .DLL or (rarely) .DRV -extension. If MPlayer fails at playing your AVI -with this kind of message: -UNKNOWN video codec: HFYU (0x55594648) -It means your AVI is encoded with a codec which has the HFYU fourcc (HFYU = -HuffYUV codec, DIV3 = DivX Low Motion, etc.). Now that you know this, you -have to find out which DLL Windows loads in order to play this file. In our -case, the system.ini contains this information in a -line that reads: -VIDC.HFYU=huffyuv.dll - - - -So you need the huffyuv.dll file. Note that the audio -codecs are specified by the MSACM prefix: -msacm.l3acm=L3codeca.acm - - - -This is the MP3 codec. Now that you have all the necessary information -(fourcc, codec file, sample AVI), submit your codec support request by -mail, and upload these files to the FTP site: -ftp://upload.mplayerhq.hu/MPlayer/incoming/<codecname>/ - - - -On Windows NT/2000/XP search for this info in the registry, -e.g. search for "VIDC.HFYU". To find out how to do this, look at -the old DirectShow method below. - - - - - - -DirectShow codecs - - -DirectShow is the newer Video API, which is even worse than its predecessor. -Things are harder with DirectShow, since - - - system.ini does not contain the needed information, - instead it is stored in the registry and - - - we need the GUID of the codec. - - - - - -New Method: - -Using Microsoft GraphEdit (fast) - - - Get GraphEdit from either DirectX SDK or - doom9. - - - Start graphedit.exe. - - - From the menu select - Graph - Insert Filters. - - - Expand item DirectShow Filters. - - - Select the right codec name and expand item. - - - In the entry DisplayName look at the text in - winged brackets after the backslash and write it down (five dash-delimited - blocks, the GUID). - - - The codec binary is the file specified in the - Filename entry. - - - - -If there is no Filename and -DisplayName contains something like -device:dmo, then it is a DMO-Codec. - - - -Old Method: - -Take a deep breath and start searching the registry... - - - Start regedit. - - - Press CtrlF, disable - the first two checkboxes, and enable the third. Type in the fourcc of the - codec (e.g. TM20). - - - You should see a field which contains the path and the filename (e.g. - C:\WINDOWS\SYSTEM\TM20DEC.AX). - - - Now that you have the file, we need the GUID. Try searching again, but - now search for the codec's name, not the fourcc. Its name can be acquired - when Media Player is playing the file, by checking - File Properties - Advanced. - If not, you are out of luck. Try guessing (e.g. search for TrueMotion). - - - If the GUID is found you should see a FriendlyName - and a CLSID field. Write down the 16 byte CLSID, - this is the GUID we need. - - - - -If searching fails, try enabling all the checkboxes. You may have -false hits, but you may get lucky... - - - -Now that you have all the necessary information (fourcc, GUID, codec file, -sample AVI), submit your codec support request by mail, and upload these files -to the FTP site: -ftp://upload.mplayerhq.hu/MPlayer/incoming/<codecname>/ - - - -If you want to add a codec yourself, read -DOCS/tech/codecs.conf.txt. - - - - - diff -r 4c9698666a4c -r d093bee92b15 DOCS/xml/en/faq.xml --- a/DOCS/xml/en/faq.xml Sat Dec 27 13:58:20 2008 +0000 +++ b/DOCS/xml/en/faq.xml Sat Dec 27 14:38:42 2008 +0000 @@ -236,7 +236,8 @@ Check the codec status, if it doesn't contain your codec, read the codec documentation, especially the -codec importing HOWTO and contact us. +Win32 codec HOWTO +and contact us.