[MPlayer-users] Porting Win32 Cineform codec in mplayer...

George Dsilva die4multimedia at yahoo.co.in
Tue May 29 15:01:29 CEST 2007


Hi,
 
 I want to port Cineform Codec (which is DirectShow compatible)  to our mplayer.
 The steps followed to do this were as follows:
 
 1. Made a entry in "etc/codecs.conf"
 videocodec cineform
   info "cineform codec"
   status working
   fourcc CFHD,cfhd
   driver dshow
   dll "CFDecode2.ax"
   guid 0xAD83011E, 0x01d1, 0x4623, 0x91, 0xfd, 0x6b, 0x75, 0xf1, 0x83, 0xc5, 0xa9
   out YUY2
 
 
 2. Copied the "CFDecode2.ax" file in "/usr/local/lib/codecs" (win32 codecs directory on my machine)
 
 3. configured and compiled mplayer using configure and make tool respectively.
 
 After this, if I play a movie with Cineform codec, mplayer crashes. The following log file was generated...
 
 
 # mplayer cineform-orig.avi
 MPlayer 1.0rc1-3.3.3 (C) 2000-2006 MPlayer Team
 CPU: mobile AMD Athlon(tm) MP-M 2000+ (Family: 6, Model: 8, Stepping: 1)
 CPUflags:  MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 0
 Compiled for x86 CPU with extensions: MMX MMX2 3DNow 3DNowEx SSE
 mplayer: could not connect to socket
 mplayer: Connection refused
 Failed to open LIRC support. You will not be able to use your remote control.
 
 Playing cineform-orig.avi.
 AVI file format detected.
 AVI_NI: No audio stream found -> no sound.
 AVI: No audio stream found -> no sound.
 VIDEO:  [CFHD]  2048x856  31bpp  24.000 fps  77605.8 kbps (9473.4 kbyte/s)
 ==========================================================================
 Opening video decoder: [dshow] DirectShow video codecs
 Called unk_GetModuleBaseNameA
 Called unk__splitpath
 Called unk__mbsupr
 Called unk__mbscmp
 Called unk__mbscmp
 Called unk__mbscmp
 Called unk__mbscmp
 
 
 MPlayer interrupted by signal 11 in module: init_video_codec
 - MPlayer crashed by bad usage of CPU/FPU/RAM.
   Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
   disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
 - MPlayer crashed. This shouldn't happen.
   It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
   gcc version. If you think it's MPlayer's fault, please read
   DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
   won't help unless you provide this information when reporting a possible bug.
 
 
 
 
 Can someone please guide me if I am missing any steps.
 
 Regards
 
 George
 
       
---------------------------------
 Did you know? You can CHAT without downloading messenger.  Know how!


More information about the MPlayer-users mailing list