[MPlayer-dev-eng] help, uncompressable video stream

[Joey Parrish]

On Thu, Mar 20, 2003 at 10:09:26AM +0100, Michael Niedermayer wrote:
> hmm what filesize do u get for each of the following, 2.6G is really a bit 
> huge, perhaps its a bug ...
> -lavcopts vcodec=mpeg4:vqscale=31
> -lavcopts vcodec=mpeg4:vhq:vbitrate=400
> -lavcopts vcodec=mpeg4:vqscale=31 -ssf lgb=1 -ssf cgb=2 -vop scale
> -lavcopts vcodec=huffyuv:vstrict=-1:vpass=1:pred=2 
> -lavcopts vcodec=huffyuv:vstrict=-1:vpass=2:pred=2
            ^^^^^^^^^^^^^^
	    Please add this to the manpage!!  I never tried it because
	    it's not documented under vcodec.

Okay, here are the results for a very few frames. (100 from the middle.)
I will run it on a larger sample later, but I have a very slow computer
and very little drive space left.  So, for 100 frames (3.3s at 680x332):

-lavcopts vcodec=mpeg4:vqscale=31   3.3M 
-lavcopts vcodec=mpeg4:vhq:vbitrate=400    15M 
-lavcopts vcodec=mpeg4:vqscale=31 -ssf lgb=1 -ssf cgb=2 -vop scale   696k 
-lavcopts vcodec=huffyuv:vstrict=-1:vpass=1:pred=2   8.0k 
-lavcopts vcodec=huffyuv:vstrict=-1:vpass=2:pred=2    14M 

The blurred version is smaller, but the blur makes the use of ascii
unrecognizable, which defeats the purpose of using it.  :)

The huffyuv pass1 version produced garbage.  Is this normal?
http://joey.nicewarrior.org/huff.jpg (cropped, lq, ~10kb)

The huffyuv pass2 version looked normal.

1Mb per second seems to be our best result so far without blurring the
video stream.  Does this tell you anything useful?  Do you think it's a
bug, or have I just tried to do something silly?

--Joey