[x264-devel] [PATCH] Dump frame statistics to the csv log file in encode order

[Steve Borho]

On 05/28, BugMaster wrote:
> On Thu, 28 May 2015 12:10:26 +0530, Gopu Govindaswamy wrote:
> > And Also we are planing to add more information? like 
> 
> > Counts of each MB partition size/mode
> > Quantify per-frame residual energy after motion prediction 
> > Final Rate Factor per frame (when VBV caps reduce quality)
> > Average chroma and luma distortion
> > Mean, median, min, max, and standard deviation of luma level per frame
> 
> > its very difficult to manage in console output, the csv file is a easily manageable
> 
> Hi. Before you process father with it am I going note that I am
> currently against of including such things in upstream. Because imho
> it is useless and only complicate codebase without any real benefit.
> It doesn't help debugging (I know because I fixed a lot of them; it
> will need custom printf-s in places specific to the bug anyway) and
> worthless in quality control because it wouldn't replace need for
> separate stream analyzer and metric calculation tools which can be
> used for cross-codec comparison (and digging in csv-files is painful).
> Also there is already API for returning frame-based quality metrics,
> QPs and frame types from libx264 and so it is imho not task of libx264
> to write this in file but task of libx264 user app (or visualize it
> any other way then dumping to file).

Would you be amenable to increasing the data returned from libx264 and
writing this data to a file in x264.c, so all string manipulation and
file i/o is handled in the cli?

-- 
Steve Borho