On Fri, Feb 19, 2021 at 9:03 PM Werner Robitza <werner.robi...@gmail.com> wrote:
> On Mon, Feb 1, 2021 at 4:57 PM Nicolas George <geo...@nsup.org> wrote: > > > > Werner Robitza (12021-01-22): > > > Thanks, I know this, but this is not a known format that can be easily > > > parsed like a plain CSV file. > > > > What you need to do is to extend the metadata filter so that it lets > > output to a file and choose the format. > > I suppose that would be the best option, yes. However, metadata comes > in all kinds of shapes, so it's not easy to map arbitrary metadata > (that any filter can generate) to a meaningful output format, in > particular when the result should be CSV. > > In particular, such output should be tidy [1]. For instance, you don't > want to output "frame, key, value" with lines "1, si, 53.999", but > rather "frame, si, ti". Such transformations to useful/parsable output > must be done in the filter itself, not vf_metadata … > Huh, that does not make any sense. > > [1]: > https://cran.r-project.org/web/packages/tidyr/vignettes/tidy-data.html > _______________________________________________ > 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". _______________________________________________ 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".
