Terrific work!

[zachlewis]

Not an actual issue, just a thank-you. Having unsuccessfully attempted something similar myself, I can appreciate how much of a headache this is!

In particular, thanks for the attention given to chromaticities metadata -- it's data I'm specifically interested in, yet it's surprisingly often ignored or cast to a string by other exr metadata-scraping implementations, I guess owing to the unusual datatype...

👍

[vvzen]

This actually made my day. :)
This repo was a bit of hobby project, so I'm really glad that you found it useful!
Thanks for your kindness!

[Marcuzzz]

I also like the work you have done!!
Any chance you know how to go from timeAndFlags to the actual timecode?
It tried to parse the timeAndFlags integer but it doesn't seem to be accurate...

def frames_to_timecode(frames, framerate):
    return "{0:02d}:{1:02d}:{2:02d}:{3:02d}".format(
        int(frames / (3600 * framerate)),
        int(frames / (60 * framerate) % 60),
        int(frames / framerate % 60),
        int(frames % framerate),
    )

[vvzen]

Hi @Marcuzzz !
do you mind opening a new issue? It's been a while so I'd need to refresh my memory on what timeAndFlags is actually meant to represent. In the meantime, you might want to have a look at https://opentimelineio.readthedocs.io/en/latest/ , if you're working with timecodes, frames and time, since it gets really complex quite quickly! :)

[nathwilson22]

I just wanted to add a +1 to your work here @vvzen

After battling with OpenEXR compiling gcc-11 correctly on Rocky8 for use in Python, I found your repo and this has made the process of reading key attributes (mainly FPS) from exr headers much easier from an infrastructure point of view.

✌