On Fri, Jan 22, 2021 at 12:28 PM Paul B Mahol <one...@gmail.com> wrote: > > As an end user I would find an output file with a known format much > > easier to work with. > > This works very well for the libvmaf filter, for example. > > Could you please explain how to achieve the same kind of output with > > the metadata injection? > > > > -vf your_filter,metadata=mode=print
Thanks, I know this, but this is not a known format that can be easily parsed like a plain CSV file. At least the way the SITI filter is used, regular users just want simple output in a file that they can directly load into Excel, Python, whatever. (Just like for VMAF.) I understand why you wouldn't want each filter to have its own IO functionality, but in terms of usability, only having the metadata option would be extremely bad. (Perhaps the real solution would be to have the metadata filter generate different kinds of known output formats.) Werner _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
