Nick Porcino

BTW, the community continued to develop the bindings, and the source is now in the OpenEXR repo itself, https://github.com/AcademySoftwareFoundation/openexr and on PyPi as https://pypi.org/project/OpenEXR/

In case it's useful, OpenTimelineIO has a setup.py that facilitates building the C++ portions as part of the pip install. You can see it in the root of the OpenTimelineIO...

Not sure that closest is what is required. My first reaction is that we must be missing the bog standard add a half before rounding down somewhere.

@phil-man-git-hub Do you want to edit your message? I notice that your phone number has somehow got appended into the post. I'm afraid I am not following how a start...

That makes sense, thank you. The interfaces for to/from seconds/frames could be a little less simplistic to help with those cases.

To summarize, MC and OTIO ~~agree~~ disagree, but time-code-calculator ~~significantly differs~~ agrees with OTIO. ~~?~~ Maybe we need to ping Avid. ~~the calculator's author...~~

@jminor I closed that one in favor of this one, since this one rectifies the treatments of documented SMPTE rates with the code. @splidje NLEs have various "tricks" for dealing...

Thanks for doing the extra checks! So I think the theory is that MC is displaying time code at 30, even for a selected rate of 60 (as opposed to...

Had a look at the link you provided, quite an interesting read ~ TimeCodeKit's major difference, I'd say, is that it introduces a strongly typed TimeCode object from which a...

I ran the tests in my own repo, the python unit tests are what failed, the tests themselves may need correction. ``` ====================================================================== FAIL: test_invalid_rate_to_timecode_functions (test_opentime.TestTime.test_invalid_rate_to_timecode_functions) ---------------------------------------------------------------------- Traceback (most recent...