[MPlayer-users] Re: trouble converting ppm to mpeg - repost
Lawrence M./ Lifshitz
Lawrence.Lifshitz at umassmed.edu
Wed Sep 24 19:30:18 CEST 2003
It finally works! (at least more than before). I tried:
mencoder "mf://*.png" -mf fps=2:type=png -ofps 2 -ovc lavc -lavcopts vcodec=mpeg1video -of mpeg -o
movie2.mpg
and it produces an mpeg movie. I still can't say I understand the syntax of the "mf:" stuff,
but that's ok. Thank you very much for your guidance. But (seems like there's
always a "but" :-)) the colors are really bad (eg, red changed to blue) and very
streaky. It complains about colorspace and other problems:
Limiting audio preload to 0.4s
Increasing audio density to 4
VDec: Codec did not set sh->disp_w and sh->disp_h, trying workaround.
VDec: vo config request - 594 x 590 (preferred csp: BGR 8-bit)
Could not find matching colorspace - retrying with -vop scale...
Opening video filter: [scale]
VDec: using BGR 32-bit as output csp (no 0)
Movie-Aspect is undefined - no prescaling applied.
I tried increasing the bitrate (the mpeg produced is tiny) with
mencoder "mf://*.png" -mf fps=2:type=png -ofps 2 -ovc lavc
-lavcopts vcodec=mpeg1video:vbitrate=16000 -of mpeg -o movie3.mpg
but that made almost no difference in size or image quality. Since the man page says
the default
is 800 kb/sec and 16000 should be 16000kb/sec I expected to see a large
increase in size - but maybe that's because each image is essentially up
for .5 seconds, so many frames are identical.
How can I get better color fidelity and/or image quality?
thanks again for your help so far.
Larry
Jonathan Rogers wrote:
> [Automatic answer: RTFM (read DOCS, FAQ), also read DOCS/bugreports.html]
> Lawrence M./ Lifshitz wrote:
>
>> when I do a "man mplayer" I don't see exactly what you see. I see
>> mencoder "mf://*.jpg" -mf fps=25 -o output.avi -ovc divx4
>> not the example you are sending me.
>> Also I also don't see any mention of an "on" option for -mf.
>> (I'm running MPlayer 1.0pre1-3.2.2). I find the example I do see
>> confusing, since the man page talks about -mf, not "mf://".
>> I'm also confused by which options are "global" and go at the front and
>> which are supposed to come immediately AFTER the file name. Looking
>> at my
>> man page it looks like almost all options to mencoder should come before
>> the file names
>> mencoder [options] [ file | URL | - ] [-o file]
>>
>> However, I had thought that filename expansion might be part of the
>> problem
>> so I had tried just listing all the files on the command line, that
>> didn't seem
>> to help.
>
>
> Do whatever your manpage says, but I'm quite certain that order of the
> arguments doesn't matter. I usually use a recent CVS version, which
> takes the URL style arguments, like "mf://", but I wasn't sure what your
> version wants.
>
> My CVS manpage gives this example:
> --------------------------------------------------------------------------
> Encoding all *.jpg files in the current dir
> mencoder "mf://*.jpg" -mf fps=25 -o output.avi -ovc divx4
> --------------------------------------------------------------------------
>
> What does yours give?
>
> Jonathan Rogers
>
> _______________________________________________
> RTFM!!! http://www.MPlayerHQ.hu/DOCS
> Search: http://www.MPlayerHQ.hu/cgi-bin/htsearch
> http://mplayerhq.hu/mailman/listinfo/mplayer-users
--
Lawrence M. Lifshitz, Ph. D., Associate Professor
Biomedical Imaging Group (http://invitro.umassmed.edu)
University of Massachusetts Medical School (http://www.umassmed.edu)
Phone: (508) 856-3392 email: Lawrence.Lifshitz at umassmed.edu
Fax: (508) 856-1840 web: http://invitro.umassmed.edu/~lml
More information about the MPlayer-users
mailing list