Mark Reid

I tried that online [tc calculator](https://robwomack.com/timecode-calculator/). Its pretty finicky but you might have had it set to 59.97fps DF , I get 1084319 frames = 05:01:11:59 @ 60 fps. 1084319...

The TC display in MC is might be showing 30fps TC where it duplicates every step. My MC cannot display 60 TC without using a burn in.  To make...

ok, in MC general settings there is option to change the TC display format from 30fps to 60 fps   Still haven't found a 60fps drop frame option.

No, those would produce different answers. maybe using 23.97 is a bit more clear. It would be the equivalent of this ``` frame = otio.opentime.from_timecode(timecode_str, 24).value a = otio.opentime.from_frames(frame, 23.97)...

what is the the project format/edit rate?  some formats can't access certain timecodes.

I've verified those calculations in Resolve, it actually supports 59.94 TC with drop frame. 1084319 frames = 05:01:11:59 @ 59.94 fps without drop frame 1084319 frames = 05:01;30;03 @ 59.94...

Resolve also additionally supports a 16, 18, 47.952 and 48 TC format. The 47.952 appears to just be 48, like 23.976 is just 24 

I'm quite sure @jminor had his avid set in 30 TC mode for 60. Its the default setting. The timecode ticks every 2 frames and the top dot of the...

I've also verified those timecode values in Unreal Engine 60 fps NDF  59.94 fps DF 

From that magic signature it looks like a KLV formatted AAF file. It is basically an MXF file. These type of files have been starting to coming up recently, another...