OIIO may deal with image *files* rather than movie *files*, but the image files it deals with are often individual frames of motion pictures and at least two of the commonly-used formats (OpenEXR and DPX) have provisions in their specifications for fields that are SMPTE timecodes. We need to accommodate this fact in some way, it's just a matter of balancing the desire to make that timecodes not too awkward, with also making it not too intrusive on the internals, the formats that don't have SMPTE timecodes, and apps.
On Oct 10, 2013, at 10:29 AM, Daniel Wexler wrote: > This would allow us to store the timecode as an array of uint64 and provide a > way to get that same value as a string. Since OIIO deals with images, and not > video, I don't think there's justification for #3. > > -- Larry Gritz [email protected]
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
