Nick Porcino

> `otio.opentime.from_frames(1084319, 60).to_timecode() # no dropframe rate requested` referencing @markreidvfx's reported values from Resolve and Unreal 1084319 frames = 05:01:11:59 @ 59.94 fps without drop frame 1084319 frames = 05:01:30;03...

Could you clarify why it's misleading? Maybe I've been looking at it too long and have got some assumptions that make me overlook something. >>> otio.opentime.from_frames(1, 3).to_timecode(30) '00:00:00:10' 1 frame...

Hi! One year later, are we stalemated? Today I am wondering if the work here fixes the very sad rounding bug reported yesterday. How can we unstick this one? Have...

@apetrynet I'm not following the comment "The use of the "valid_xx" functions have come up in quite a few discussions and issues." are you saying that supports merging, or that...

Unfortunately the follow on steps 1 and 2 never occurred. I am not an advocate of this style; and with no other input and a year of inactivity I have...

Please read this as trying to be constructive, rather just taking an arbitrary position about stylistic choices. To me, this is not a stylistic change, it's a productivity change, so...

Sure! BTW I'm perfectly fine with doxygenating just this one file to establish a pattern ~ I think that is what you are proposing.

CI is failing for a reason that seems unrelated to this PR, I can't see the trailing whitespace. line 1003 is not in the PR, nor does it have 84...

TIL that the Python % operator and the C % operator are not the same thing. So I withdraw my flag of a bug in the timecode conversion routine. Creating...

Here is some excellent background reading. https://randomascii.wordpress.com/2012/02/13/dont-store-that-in-a-float/ The conclusion is that double precision will store a time value with constant precision at the microsecond level for 136 years. So what's...