[FFmpeg-devel] Official status of FFv1?

Lars Täuber lars.taeuber
Sun Mar 28 12:11:16 CEST 2010


Hi!

On Mon, 22 Mar 2010 14:07:31 -0700 Baptiste Coudurier <baptiste.coudurier at gmail.com> wrote:
> On 03/22/2010 01:11 PM, Jason Garrett-Glaser wrote:
> > Here's some benches for you, Baptiste.  Source: standard foreman CIF.
> >
> > $ ffmpeg -i videos/foreman_cif.y4m -vcodec ffv1 -coder 1 output.avi
> > frame=  300 fps= 48 q=0.0 Lsize=   19017kB time=10.01 bitrate=15563.4kbits/s
> > ----------+ 1 Jason None 19473662 Mar 22 13:07 output.avi
> >
> > $ ffmpeg -i videos/foreman_cif.y4m -vcodec ffv1 -coder 0 output.avi
> > frame=  300 fps= 98 q=0.0 Lsize=   19270kB time=10.01 bitrate=15770.5kbits/s
> > ----------+ 1 Jason None 19732838 Mar 22 13:10 output.avi
> >
> > $ ./x264 videos/foreman_cif.y4m --preset veryfast --qp 0 -o test.h264
> > --threads 1
> > encoded 300 frames, 75.17 fps, 13583.06 kb/s
> > ----------+ 1 Jason None 16995802 Mar 22 13:07 test.h264
> >
> > $ ./x264 videos/foreman_cif.y4m --preset veryfast --qp 0 -o test.h264
> > --threads 1 --no-cabac;ls -l test.h264
> > encoded 300 frames, 161.38 fps, 15550.08 kb/s
> > ----------+ 1 Jason None 19457036 Mar 22 13:09 test.h264
> >
> > Note of course in practice you would use multiple threads with x264,
> > which would put it well ahead speed-wise (since FFV1 cannot be
> > frame-multithreaded in the typical way).
> 
> Well, it seems to really depend on the input file:

I suspect it heavily depends on the resolution too. It may not seasonable to test with CIF files nowadays as Dark did.

Regards
Lars



More information about the ffmpeg-devel mailing list