Incorrect Timecode on Some Panasonic Camera

Addressed an issue with incorrect timecode on some Panasonic camera QuickTime files

Even when the notes mention a correction in timecode handling of some Panasonic cameras, this issue is not solved, or to be precise, it is only partly solved.

I use a Panasonic AG-DVX200 in UHD/50p with H.264 encoding in QuickTime container. If I select a clip from the camcorder in the media page of Resolve, a wrong timecode is shown. Minutes and Seconds are o.k. (after the correction mentioned in the notes to public beta 3), however the frame number is wrong. It always shows 0.5 x <frame number>. This leads to overlapping or gaps in the timecode of consecutive clips taken by the camcorder.

For example:
Clip 1 starts with timecode 00:00:00 and is 9:30 long (Resolve shows start timecode 00:00:00 end timecode 00:09:15 and length 9:30).

Clip 2 starts with 00:09:30 and is 08:32 long (Resolve shows start timecode 00:09:15, end timecode 00:17:47, and length 08:32).

Clip 3 starts with Timecode 00:18:12 and is 09:06 long (Resolve shows start timecode 00:18:06, end timecode 00:27:12, and length 09:06).

This could easily be solved by multiplying the frame number with 2.

The reason is simply with the way H.264 encodes "frames" in the timecode field. It is a remnent from interlaced video, where 25 frames have 50 fields. In the timecode field of H.264 the numbering runs from "field" 0 - 49 and increases frame number every second "field" from 0 - 24.

Joachim

Yes, it's Resolve bug/standards limitation.
Officially there is no SMPTE timecode for 50p (even if people used such a format for years now!), so in such a case 2 frames are shown with the same number and then it changes on 3rd frame (and so on). Just get use to it

Andrew,
I cannot get used to it, as this error leads to overlapping timecode values of different clips in a sequence. As a consequence I cannot reconform a timeline. In addition it leads to totally wrong timecodes when I send the timeline to Avid Media Composer using Avid AAF export.
Either This bug will be corrected or I will drop Resolve at all.
Joachim

GOOD NEWS
With Resolve 14 Beta 4 the issue has been solved!
Thank you BM
Joachim