[BUGREPORT] Mencoder floating point exception...
This is a strange one... When using -ovc vfw with ANY source and ANY output codec, I get an immediate floating point exception. Exact same result when compiled with gcc-2.95.3 or gcc-3.3.6. The strangest thing is, it worked perfectly on this exact machine, using Slackware 10.0, until I wiped the drive and installed Slackware 10.2... Stock kernel, seemingly perfectly normal system, with practically no other problems with mplayer/mencoder to speak-of. Why oh why do MPlayer bugs love me so?
On Thu, 04 May 2006 02:31:30 -0700 RC <rcooley@spamcop.net> wrote:
This is a strange one... When using -ovc vfw with ANY source and ANY
-ovc vfw only supports one output codec iirc. H:\>mencoder -ovc help|grep vfw vfw - VfW DLLs, currently only AVID is supported. its in the todo to get it working with all vfw codecs. http://www.mplayerhq.hu/DOCS/tech/TODO -compn
On Thu, 4 May 2006 09:11:02 -0400 compn <tempn@twmi.rr.com> wrote:
-ovc vfw only supports one output codec iirc.
H:\>mencoder -ovc help|grep vfw vfw - VfW DLLs, currently only AVID is supported.
The docs are wrong a lot... It's limited and undocumented, but it works. Perhaps I'll send a patch... I'm probably one of only 2-3 people using -ovc vfw. See my "success thread" from about 6 months ago when encoding with -ovc vfw: http://thread.gmane.org/gmane.comp.video.mplayer.user/38781/focus=38781 Actually, believe it or not, you've just solved my problem. I was completely mistaken about which codecs were actually working. Sorry for wasting time. Chalk this one up to "I'm an idiot for submitting bugreports late at night."
its in the todo to get it working with all vfw codecs. http://www.mplayerhq.hu/DOCS/tech/TODO
I'd LOVE to see bitrate selection added, but DLL/codec selection is already there, and working with a few codecs. In fact, I pledge $5 to whoever writes the necessary code to allow setting a bitrate for encoding with vfw. :-)
On Thu, 04 May 2006 17:59:10 -0700 RC <rcooley@spamcop.net> wrote:
On Thu, 4 May 2006 09:11:02 -0400 compn <tempn@twmi.rr.com> wrote:
-ovc vfw only supports one output codec iirc.
H:\>mencoder -ovc help|grep vfw vfw - VfW DLLs, currently only AVID is supported.
The docs are wrong a lot... It's limited and undocumented, but it works. Perhaps I'll send a patch... I'm probably one of only 2-3 people using -ovc vfw.
can you give us some example command lines? i will make some patches to the DOCS and get ovc vfw in there properly!
See my "success thread" from about 6 months ago when encoding with -ovc vfw: http://thread.gmane.org/gmane.comp.video.mplayer.user/38781/focus=38781
Actually, believe it or not, you've just solved my problem. I was completely mistaken about which codecs were actually working.
using the wrong dll? hehe ... also... maybe we should start a list of codecs that do work? like codecs.conf or vfwcodecs.txt it should include codec filename , md5sum, maybe url to file on mphq (so that the version that works can be preserved in case newer/older versions crash) -compn
On Fri, 5 May 2006 13:53:38 -0400 compn <tempn@twmi.rr.com> wrote:
can you give us some example command lines? i will make some patches to the DOCS and get ovc vfw in there properly!
It's quite simple. "-ovc vfw -xvfwopts codec=vp4vfw.dll"
using the wrong dll? hehe ...
Yeah, I forgot that the vp3 DLL in mplayer's codec pack is older than the one on xiph.org, and doesn't work for encoding... I could also have sworn that encoding worked with, eg. vp6.
also... maybe we should start a list of codecs that do work? like codecs.conf or vfwcodecs.txt it should include codec filename , md5sum, maybe url to file on mphq (so that the version that works can be preserved in case newer/older versions crash)
I made a quick script to try each of the ~100 I have, and these are the ones that seem to work: ViVD2.dll aslcodec_vfw.dll asusasv2.dll asusasvd.dll avimszh.dll avizlib.dll divx.dll huffyuv.dll iccvid.dll icmw_32.dll jp2avi.dll m3jp2k32.dll m3jpeg32.dll mcmjpg32.dll mpg4c32.dll tsccvid.dll vp31vfw.dll ** vp4vfw.dll wnvplay1.dll wnvwinx.dll ** Downladed from: http://downloads.xiph.org/releases/vp3/3.2.6.1/winvfw/vp31vfw.dll
On Fri, 05 May 2006 16:25:16 -0700 RC <rcooley@spamcop.net> wrote:
On Fri, 5 May 2006 13:53:38 -0400 compn <tempn@twmi.rr.com> wrote:
can you give us some example command lines? i will make some patches to the DOCS and get ovc vfw in there properly!
It's quite simple. "-ovc vfw -xvfwopts codec=vp4vfw.dll"
using the wrong dll? hehe ...
Yeah, I forgot that the vp3 DLL in mplayer's codec pack is older than the one on xiph.org, and doesn't work for encoding... I could also have sworn that encoding worked with, eg. vp6.
vp6vfw.dll works for me. 04d635a364243013898fd09484f913fb *j:\\cdrive\\mplayer\\vp6vfw.dll i made a patch to encoding-guide.xml and it was commited. http://www1.mplayerhq.hu/pipermail/mplayer-docs/2006-May/007644.html also i dont suppose you could verify the md5sums i put into the docs with your codecs' md5sums? did you check codecs.conf for every vfw codec? are you missing any from that list? also there might be some vfw codecs in the mplayer codecs repository that could be checked. or even vfw versions of dshow codecs that are in the codec packs. can you paste your script to test codecs here and maybe someone will do an extensive test against mphq codecs archive? thanks a bunch! -compn
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: get_path('subfont.ttf') -> '/home/root/.mplayer/subfont.ttf' Unicode font: 255 glyphs. Floating point exception 2006Apr25/main# Same with mencoder versions from Feb2005 to Apr2006. And whether compiled with gcc 2.95.3 or 3.3.6 (in debug mode no less). If anyone else can get this working (on Linux), I'd certainly want to know how. 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.
http://www1.mplayerhq.hu/pipermail/mplayer-docs/2006-May/007644.html also i dont suppose you could verify the md5sums i put into the docs with your codecs' md5sums?
Looks like you left out the MD5 for: aslcodec_vfw.dll: 608af234a6ea4d90cdc7246af5f3f29a ViVD2.dll: a7b4bf5cac630bb9262c3f80d8a773a1 MD5 mismatch for: m3jp2k32.dll: f3c174edcbaef7cb947d6357cdfde7ff m3jpeg32.dll: 1cd13fff5960aa2aae43790242c323b1 My codecs are from "all-20050412.tar.bz2" and "windows-all-20050412.zip".
did you check codecs.conf for every vfw codec? are you missing any from that list?
A handful, but it's probably better to stick to codecs which are in the codecs packs right now.
can you paste your script to test codecs here and maybe sollone will do an extensive test against mphq codecs archive?
Arg! It wasn't a very thorough test, there are lots more failures: asusasv2.dll asusasvd.dll wnvplay1.dll and wnvwinx.dll are just failing quietly, and not outputting any video. avimszh.dll is only outputting colorful static. mcmjpg32.dll wnvplay1.dll and wnvwinx.dll are not outputting anything playable (bluescreen--perhaps a colorspace problem?). jp2avi.dll apparently needs "-vf flip". Very sorry :-( 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).
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
On Thu, 11 May 2006 02:37:22 -0400 compn <tempn@twmi.rr.com> wrote:
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
Athlon XP (1.66Ghz) 2000+ MEncoder dev-CVS-060425-06:19-2.95.3
how about adding compatability to the codec list table? codec name, md5sum, windows / linux codec1, md5sum, yex / no codec2, md5sum, yes / yes
Sounds like a good idea, but you're pretty well on your own.
what do you mean doesn't support? did you add it to codecs.conf?
Actually, it's already in there, and it DOES work. Not sure why it was crashing before (perhaps it doesn't like some filter), but I'll track that down later.
thanks for giving me all this info, i wonder how many people will actually use vfw support in mencoder?
My guess: 3 (including myself) That may change drastically if someone writes the code for setting the bitrate and basic encoding options.
On Fri, May 12, 2006 at 12:54:51AM -0700, RC wrote:
thanks for giving me all this info, i wonder how many people will actually use vfw support in mencoder?
My guess: 3 (including myself)
That may change drastically if someone writes the code for setting the bitrate and basic encoding options.
Isn't it only selectable via a windows dialog box? Rich
On Sat, 13 May 2006 10:20:35 -0400 Rich Felker <dalias@aerifal.cx> wrote:
That may change drastically if someone writes the code for setting the bitrate and basic encoding options.
Isn't it only selectable via a windows dialog box?
Hmm... Perhaps encoding options, (although they are also stored in the registry, so might be setable that way) but the bitrate is definately just a value passed via VFW.
participants (3)
-
compn -
RC -
Rich Felker