On Wed, 10 May 2006 22:31:50 -0700 RC <rcooley@spamcop.net> wrote:
On Wed, 10 May 2006 00:21:11 -0400 compn <tempn@twmi.rr.com> wrote:
vp6vfw.dll works for me. 04d635a364243013898fd09484f913fb *j:\\cdrive\\mplayer\\vp6vfw.dll
Same MD5, still I get:
ya, i was using windows mencoder, what cpu are you testing on? i'm testing on an amd 900mhz with MEncoder dev-CVS-060323-19:17-3.4.4
Of course, it looks like you're using mencoder under Windows, which would explain it. I suspect MPlayer doesn't use the wine DLL loader code when it's actually running under Windows :-) In fact I expect that a *lot* more codecs will work under Windows than on other OSes.
how about adding compatability to the codec list table? codec name, md5sum, windows / linux codec1, md5sum, yex / no codec2, md5sum, yes / yes
Looks like you left out the MD5 for: aslcodec_vfw.dll: 608af234a6ea4d90cdc7246af5f3f29a ViVD2.dll: a7b4bf5cac630bb9262c3f80d8a773a1
ya i didnt have those two codecs to get the md5sums
MD5 mismatch for: m3jp2k32.dll: f3c174edcbaef7cb947d6357cdfde7ff m3jpeg32.dll: 1cd13fff5960aa2aae43790242c323b1
whoops!
Here's a far better script, which just writes the files, and requires a human to check them: ____ for CODEC in /usr/local/lib/win32/*.dll do CODEC_BASE=`basename $CODEC` mencoder -nosound -ovc vfw -xvfwopts codec=$CODEC_BASE \ VIDEO.avi -endpos 30 -o TEST-"$CODEC_BASE".avi rm "`du -k TEST*.avi | awk '/^0/ {print $2}'`" done ____
And if anyone cares, vp7vfw.dll: cb4cc3d4ea7c94a35f1d81c3d750bc8d mostly works but writes the wrong fourcc, and "-ffourcc VP70" doesn't work. Manually putting the correct fcc into the header (byte 00000070 and 000000BC) allows it to playback with Windows players (MPlayer doesn't support VP7 playback yet).
what do you mean doesn't support? did you add it to codecs.conf? thanks for giving me all this info, i wonder how many people will actually use vfw support in mencoder? -compn