Audio LTC interpretation faulty

Hi,

we are using three Tentacles to sync two panasonic cameras (GH4 / GH5) and one Zoom F8 recorder. The timecode on the cameras is being recorded on the audio track. We had some difficulties with our workflow, as sync never worked properly, until we found that Audio LTC readout in Davinci is not working accurate. The same video files work in Pomfort Silverstack as expected, so the audio timecode track is recorded properly.

LTC.png (676.31 KiB) Viewed 1607 times

Testfiles
I'm not allowed to post links. If you provide me an email, i could send you the testclips.

Thank you

What frame rate?

Any chance you could test this on a Resolve v15.3.1 system? It seems there have been more than just a few reports of anomaly’s in v16+ audio system.

What frame rate?

25fps

Any chance you could test this on a Resolve v15.3.1 system? It seems there have been more than just a few reports of anomaly’s in v16+ audio system.

Ill try that later!

Any chance you could test this on a Resolve v15.3.1 system? It seems there have been more than just a few reports of anomaly’s in v16+ audio system.

Same behaviour in 15.3.1.

Search for the thread: Update Timecode from Audio LTC is Inaccurate

(I can't post URLs)

Hi,

Using similar setup, had same problems, root cause explained below.

The problem is not exactly with Resolve, but with GH5. If you take a close look at audio in your GH5/4 file, you'll see that audio in GH5 is not being recorded for first 7-11 frames (dependent on resolution & settings). Because of this, resolve reads first timecode that appears and saves it as file timecode - not taking into account that delay. Luckily for particular setting this delay is repeatable, so for me simply offsetting audio recorder file by particular no of frames solved the issue.

Not exactly issue with resolve, but rather GH5 implementation.

However, it can be easily done way better in resolve, so that this issue is corrected. Tentacle sync software checks for timecode approx. 3 seconds into the video, so that it ignores issues with first frames. I've already requested this fix in one of "Feature requests" topics. You could also add your voice to one of those topics - the more this point is mentioned, the higher likelihood BM will actually do something around it, as from programming point of view the fix should be crazy simple.

BR,
Adam

PLease fix this!!!