<!-- Some styling for better description lists --><style type='text/css'>dt { font-weight: bold;float: left;display:inline;margin-right: 1em} dd { display:block; margin-left: 2em}</style>

   pinchartl: we have lots of tools that capture raw frames (v4l2-ctl, yavta, ...)
   <br> and tools that convert them to a format that can be displayed (for instance raw2rgbpnm)
   <br> it's annoying to have to pass the same metadata to both the capture tool (to configure the device) and to the conversion tool
   <br> it would be nice if the capture tool could record the metadata, and the conversion tool could read it
   neg: <u>pinchartl</u>: not sure about stride but for the rest tiff ?
   pinchartl: <u>neg</u>: can it store, for instance, NV12M ?
   neg: <u>pinchartl</u>: Not sure if it works out of the box, but one can set private tags. So if one where to adopt the V4L2 tools to work with tiff files I'm sure one can teach it to store/read the V4L2 pixel format from such a tag ;-)
   pinchartl: <u>neg</u>: I'll have a look. after working on DNG I'm not the biggest fan of TIFF :-)
   neg: <u>pinchartl</u>: I understand, nobody is a fan of libtiff ;-) But while working with qcam and DNG I always thought I should extend yavta and raw2rgbpnm to work with TIFF files to avoid the same metadata issue you point out so maybe it could be a fit for your use-case as well
   pinchartl: <u>neg</u>: if TIFF files can indeed store arbitrary raw types, it's certainly worth investigating
   <br> (raw here means binary data from the captured buffers, not necessarily raw bayer)