1

If I export raw video data with ffmpeg, it will have just the image data, the pixels, without any structural metadata. It won't have things like the frame size, frame rate, and pixel format. But if I need to encode the video or apply a filter, I need that metadata. So I put the metadata in a plain text file so that I don't lose this information. I then manually put it in ffmpeg commands.

For ffmpeg, I could improvise something with a custom console script to reduce manual manipulations, but that would not work for other applications, like if I want to import the a raw file into Sony Vegas.

My question is, what is the standard file format to store key video parameters? Namely at least resolution, pixel format, fps, number of frames.

I'm looking for a format that is human readable, easy parseable, and works across all video editing software. Is there such thing at all? If not, I would be slightly shocked.

If there is no such standard, what would be the closest alternative?

I use utvideo codec with avi container, it works fine with ffmpeg and Vegas and can store rgba data. So it is for footage which must not contain any artifacts and should work fast (least decoding/encoding possible).

  • 1
    Unfortunately, I don't know of any human readable formats. Most containers store the structural metadata in various binary forms. The closest thing that I can think of to what you are trying to do is to use a Quicktime or MXF reference file. However, I don't know if either of those support the UT video codec. – Michael Liebman May 5 '17 at 2:28
  • I use .nut when working with ffmpeg, otherwise V210 is well-supported and documented. – Michael Steinberg May 14 '17 at 4:57

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.