Re: [Openexr-devel] keycode

[Ken McGaugh]

Kevin Wheatley wrote:
> Ken McGaugh wrote:
>
> > We want to store film keycode information in our exr's, and before I
> > decide what header attribute(s) to create for this I wanted to
> > know if anybody else is doing this already.  If so, what type and
> > names did you choose for your header attributes.
> >
> > I was hoping to embed the keycode information into one string attribute
> > rather than 5 attributes of various types is is done in DPX/cineon files.
>
>
> timecode ?
> framerate ?
> ...
>
> soon you'll end up with cut down DPX format that supports HDR and
> compression ... with a decent reference implementation.
>
> That idea sounds silly, I mean who on earth would want such a thing
> :-)
>
> (For the irony deprived, that's a yes)
>
> If your going to encode it, do you want the numeric encoding of the
> barcode or the human lettered encoding? I'd go with barcodes, that way
> when there is a new stock code you don't care about it. Leave it to
> the application to decode it. At which point I'm not sure the string
> encoding is worth while.

I'm not fully aware of what our needs are going to be, but for now we
just want enough information to be able to do a telecine-style burn-in
of the keycode.  We also want to be able to write this information back
into the cineons we use for our data conforms.  I also must admit that
I don't really know what fields need to be kept to meet our needs. :)

--Ken