[MPlayer-cygwin] mencoder stability?
Joey Parrish
joey at nicewarrior.org
Tue Jul 19 21:18:22 CEST 2005
On Wed, Jul 06, 2005 at 05:44:32PM +0000, James Lee wrote:
> The Windows users of my front end to mencoder, iriverter
> (http://iriverter.sourceforge.net), are reporting that the mencoder.exe process
> is crashing on them during the encoding. They report that it is happening
> almost randomly. I do not have or use Windows, so I cannot reproduce this
> problem. I have included the binaries on the mplayer ftp, various third party
> binaries, and I've even compiled my own with mingw, both 1.0pre6 and pre7, yet I
> still receive reports.
>
> As an example, this is what a command would look like as run by iriverter:
>
> mencoder /home/jlee/Video/Firefly/firefly.s01e05.safe.avi -o
> /home/jlee/Video/Firefly/firefly.s01e05.safe.h300.avi -ovc xvid -xvidencopts
> bitrate=256:max_bframes=0 -oac mp3lame -lameopts mode=2:cbr:br=128 -vf
> scale=220:120,expand=220:176,harddup -af volnorm,resample=44100 -ofps 10 -srate
> 44100
>
> Is mencoder just unstable on Windows? I wish I could provide more information.
No, it's not. You should not ship binaries that you cannot test, for
one thing. Second, you should try shipping a recent CVS version of
Mencoder. Third, you should either reproduce the crash yourself and
send a bug report, or you should ship a binary that dumps a text log of
stdout. Have your users send that log to you after a crash. Publishing
and managing MPlayer binaries is not easy stuff, particularly when it
comes to getting your users to help you out. Good luck.
--Joey
--
"I eat donuts for dying children." --Andrew
More information about the MPlayer-cygwin
mailing list