> Thanks for the report! Typically, people will measure a few coding points > per file (instead of one) so you can plot filesize vs. quality (in whatever > metric) and see relative improvement between clips (old vs. new) over > interpolated points. See e.g. a graph like this: > > https://blogs.gnome.org/rbultje/files/2015/09/vp9- x264-x265-encoding-quality.png
But FFV1 is lossless, so there is no quality range. 2016-08-17 14:59 GMT+03:00 Ronald S. Bultje <rsbul...@gmail.com>: > Hi Stanislav, > > On Wed, Aug 17, 2016 at 7:07 AM, Станислав Долганов < > stanislav.dolga...@gmail.com> wrote: > > > Hello, > > > > I'm sending the patch set with implementation of GSoC project -- FFV1 P > > frame support. The current FFV1 uses the same OBMC code as the Snow > codec. > > Also new median_me_mp function has appeared. > > > > I'm attaching speed&compression report to every patch to proof > effectivity > > of each implemented part. > > > Thanks for the report! Typically, people will measure a few coding points > per file (instead of one) so you can plot filesize vs. quality (in whatever > metric) and see relative improvement between clips (old vs. new) over > interpolated points. See e.g. a graph like this: > > https://blogs.gnome.org/rbultje/files/2015/09/vp9- > x264-x265-encoding-quality.png > > More importantly: nice work! > > Ronald > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > -- Станислав Долганов _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
