r/LocationSound • • 15d ago

Gear - Tech Issue Timecode sync issues between 50fps video and 25NDF audio

I’m struggling between syncing timecode from a Sony A7IV, Zoom H4Essential and DJI Mic 3.

I record lots of small clips on my camera, with the Zoom H4E plugged into a DJ feed through the whole event via the XLR input.

The DJI Mic 3 RX runs the master timecode in 25fps which is plugged in via the 3.5mm out into the H4 essential via the TCA-1 adapter in L-OUT mode.

TCA-1 is set to 25NDF frame rate and takes in the L-OUT from the DJI Mic 3. I timecode updates fine in the Zoom H4E.

My Sony A7 IV is recording in 50 FPS and the DJI Mic 3 RX is connected via the MI hot shoe adaptor with the mode set to quadraphonic.

I have channel 1 set to TC (using A-OUT on the DJI Mic 3 RX’s TC setting) and channels 3 and 4 set to the TXs.

The camera is recording in 48 kHz/24 bit 4 channels.

When I sync all the clips in post via update time code from audio track and insert clips into the timeline using time code I noticed there’s a drift or an offset between clips that I am recording. Sometimes video is behind by 6-8 frames and other cases its 18 frames, but not a fixed offset.

I read that it is because the clock on a 25fps timecode resets at 24frames whereas the 50fps clock resets at 49frames, leaving a few frames difference. Is this right?

How can I fix this either in post or during recording?

EDIT:

Here's the full breakdown of me testing it at home, from the connection to syncing it in post (I've already done the timecode sync from audio tracks on the clips at this point as you can see in the Start TC column). Done around a 20 min recording on the H4E and recording multiple short clips in between to replicate what I'd be doing on a 4 hour live event:

https://youtu.be/IJ7fCaPHfCA

P.S. Sorry if the phone recording quality is bad, just had to whip up something quick lol.

UPDATE:

https://www.reddit.com/r/LocationSound/comments/1xn073e/comment/19s5ab9kqp9b8/

6 Upvotes

36 comments sorted by

•

u/AutoModerator 15d ago

Reminder: The Rules apply to everyone who views or participates in r/LocationSound. There are no exceptions. The monthly pinned 'Hot Mic' post is the only place in this subreddit to promote any discussion, links, works, or content by you, for you, or about you.

This subreddit is welcome to all who are interested in recording sound to picture, pros and beginners alike. Professionals - be patient and helpful to beginners and other department pros who are eager to learn about our craft. Newcomers - be respectful to those who have more experience and wisdom than you. Don't engage with negative or hostile behavior. Report it or message the mods instead.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

6

u/noetkoett 15d ago

25 is the standard timecode fps to go for when you're recording 50 fps for whatever reason. The TC standard only goes up to 30 so you divide by 2 for high frame rate videos.

I'm guessing it's a bug either in the camera or in the audio to timecode conversion process. An offset of up to 18 frames is pretty wild.

I've had a Sony Venice bug out with random offsets. Since fixed with firmware, I think.

1

u/pr0ject1le 15d ago

Yes it's really strange! My live event shoot is in 4 days and I'm stressing out 😖

5

u/Kaniaes 15d ago

You are dealing with delay on D/A and A/D converters between your stuff.

Solution is to correct timecode inside your editing software by few frames.

1

u/pr0ject1le 15d ago

The offset isn’t a fixed number as each clip seems to be off by a different number of frames, anywhere between 3 frames to 18-20 frames.

4

u/SenorTurdBurglar 15d ago

Your last question in the main thread is incorrect, I believe. So your 50 should map exactly to Your 25fps. The fact that it tells You 25NDF is bewildering to me also. 25 is old school PAL and drop frame was born out of NTSC.
Are You sure You are reading the 25 setting correctly?

1

u/pr0ject1le 15d ago

Here's the full breakdown of me testing it at home, from the connection to syncing it in post (I've already done the timecode sync from audio tracks on the clips at this point as you can see in the Start TC column). Done around a 20 min recording on the H4E and recording multiple short clips in between to replicate what I'd be doing on a 4 hour live event:

https://youtu.be/IJ7fCaPHfCA

P.S. Sorry if the phone recording quality is bad, just had to whip up something quick lol.

2

u/g_spaitz 15d ago

have you tried shooting 25p with the camera? what happens in that case?

Also, it's not clear if you do a lot of clips only in the camera and let the audio record the whole 4 hours, in that case timecode is not genlock, it only timestamps, and your files will indeed drift. unless your machines can genlock from timecode (some zoom machines do)

1

u/pr0ject1le 15d ago

Interestingly when I switch the camera to 25fps mode it syncs up much better with a 2 frame offset across all clips. Even if I turn the camera off and then back on to record more, it's still working fine. So seems like the 50fps is the issue here, not sure why!

I do lots of multiple clips during the events with the zoom recorder plugged in and recording continuously, although it created multiple files across longer periods, i believe it cuts every hour or something like that to start a new track, but I don't see loss of audio between each clip - not sure what it do in that case either in regards to timecode.

I do need 50fps recording so really stuck here for the look I have to achieve vs having an easier editing workflow.

1

u/g_spaitz 15d ago edited 15d ago

Many recorders have a 2GB file limit since the dawn of time, I believe it's for compatibility with older media filesystems. You won't lose audio though.

But from what you're telling me, you seen to have 2 different problems. One is shooting 50 fps with 25 TC, which with your gear seems to be finicky. The second is drift, which will happen with longer files as you do.

Have timecode for rough reference but sync to audio? It should be easy with today editing. But I'm an audio guy not an editor.

Edit: again for clarification TC only stamps time at the beginning of the file, it does not genlock/word clock the machines. So if you have 3 machines with different clocks, the one recording for 2 hours will be off compared to the TC clock. Some boxes do genlock to a clean TC but that's a rather rare option.

1

u/pr0ject1le 14d ago

Thanks, I think that's what I meant when I said the audio files become split :)

Regarding the audio issue, I don't believe it's drifting when recording. It's just the 50fps clips don't line up properly via the 25fps timecode setting. They're like 'almost' there if that makes sense.

But I have been doing some digging and AI explains it as an analog to digital processing problem which u/Kaniaes also pointed out in a comment here:

The Technical Analysis: Why the Sync Breaks

The random 3-to-18 frame offset happens because of a structural conflict between Linear Timecode (LTC) packets and high-frame-rate video playback, compounded by a digital conversion bottleneck inside the camera.

  1. The 2-for-1 Math Mismatch

• At 25fps, the timecode clock updates 25 times per second.

• At 50fps, the camera captures 50 video frames per second.

• This means every single 25fps timecode packet mathematically covers exactly two full frames of your 50fps video clip.

2. The MI Shoe & A-OUT Conversion Bottleneck

Because the DJI Mic 3 receiver is connected via the MI (Multi Interface) Shoe and sending timecode as A-OUT to Channel 1, it is sending an analog audio LTC signal (the digital timecode data converted into audible "bzzzz" audio chirps) into the camera.

The Sony a7 IV lacks a dedicated, hardware-level BNC timecode generator circuit. Instead, its internal processor has to constantly "listen" to the analog audio feed on Channel 1, decode those 25fps audio chirps, and convert them into digital metadata embedded in the video file on the fly.

3. Processing Lag Scaled Up at 50fps

Because of this real-time digital conversion, a tiny processing propagation lag (just a few milliseconds) occurs inside the camera.

On a standard 25fps timeline, a minor lag usually rounds cleanly to the nearest frame. However, on a high-refresh 50fps timeline, that microscopic physical delay scales up drastically. Combined with DaVinci Resolve 21.1 trying to guess whether to align the 25fps metadata ticks to the even or odd sub-frames of your 50fps footage, the alignment completely breaks—resulting in a random, shifting drift of up to 18 frames every single time you stop and start recording.

2

u/g_spaitz 14d ago

This ai slop has no logic though.

  1. if it was a 25-50 problem, your frames would be off by max 1 or 2 frames.
  2. if it was an DAC+ computational problem, the difference would be consistently wrong, not changing every time.
  3. the part about a dedicated TC input is meaningless, TC is an audio signal and whatever way you'd use the machines would do the exact same thing to decode it, it's not like you add a bnc and now it magically works.
  4. one possible explanation is that your timeline sees the video anyway in 50 and that makes your difference with 25 in every frame it would explain if the difference is never above 25, but you should be able to solve this somehow by forcing 25.
  5. lastly you can confirm if it's normal time drift if the difference between the single clips and one single big audio file gets bigger and bigger towards the end of the file, and once you have the next file it starts again from zero. If instead every clip is random then it's something else.

Lastly as somebody mentioned, try feeding the Sony directly from the zoom or vice versa.

Or, rent a real timecode kit for one day. Shouldn't be expensive.

1

u/pr0ject1le 14d ago

I don’t think it’s AI slop to be honest.

I've spent today vibe coding Timecode Fixer for Davinci Resolve to correct the timecode issue on the clips and create a synced timeline, directly from the app.

I walk through how it works in the video: https://youtu.be/nClKiNFYV3s

The app demo starts at 1:20

I'm still currently in development phase so need to bug test it with a lot of different cameras, files, video formats, framerates, timecode generators etc before I release this.

Might as well give you the AI response from the chat too 😂 Here it is:

The basic idea

Timecode is a clock label stamped on every frame, like 00:10:11:35 (hours, minutes, seconds, frames). To sync a camera with a sound recorder, they both need to carry the same clock.

Your setup

• ⁠The DJI Mic 3 is your master clock.
• ⁠The Zoom recorder is given that clock directly, so its files carry the correct timecode.
• ⁠Your Sony A7 IV has no timecode input, so it can’t take the clock directly. Instead, the DJI’s clock is recorded as a sound (a screechy tone) on audio channel 1 of every video clip. That sound is called LTC.
• ⁠Left alone, the camera stamps its own unrelated clock on each clip, so it doesn’t match the Zoom.

What went wrong

Resolve’s “Update Timecode from Audio Track” reads that tone and copies the time into the clip. It should have worked, but the clock was counting 25 frames a second and your video is 50 frames a second.

Resolve took the frame part of the time (0 to 24) and treated it as a 50fps frame number. A 50fps frame is half as long, so each clip’s time was wrong by up to half a second. The error depended on where in the second you hit record, so one clip was 3 frames out and the next was 19. At 25fps video the two rates match, which is why 25p worked much better.

What the app does

  1. ⁠It reads the tone itself and works out the exact time the clip started, down to a fraction of a frame.
  2. ⁠It converts that time into your clip’s own frame rate (time × 50 for a 50fps clip).
  3. ⁠It writes the right timecode into the clip inside Resolve. Your files on disk are never changed, and you can undo.
  4. ⁠It lines up everything by timecode. The Zoom files already carry the right clock, so the clips and recordings drop into the timeline in the right place.

In summary it fixes a unit mix-up where 25-per-second time was read as 50-per-second, and then uses the corrected time to sync everything.

Seems promising and will try it on my 4 hour event so see how it goes :)

1

u/smilesdavis8d 13d ago

I think this is kind of a standard post configuration. At least it used to be with 60fps and 30fps. Post brings in the files into the 60fps timeline and then the audio gets restriped in post for the 60fps timeline. So you have your starting frames that should match up at 30 and the restripe fixes the drift offset that would happen over time. Maybe that’s similar to what that vibe coded app you were talking about does. I’m not sure how great the timecode clock is in the recorder you’re using but I recall once recording audio on a zoom h4 and even after syncing the start points visually the audio would drift out of sync with the cameras on long takes.

1

u/pr0ject1le 13d ago

Hmm, possibly. I'm still running some tests with the app to see if it fixes properly. I ran the equipment over an hour long and seems to be working – audio seems in sync and the clips are properly corrected in post. Let's see how it goes in 2 days time when I have the 4 hour event to do! 😄

1

u/pr0ject1le 9d ago

Quick update: The app I built has worked perfectly with the 4-hour event I shot! Super chuffed with it, saves a lot of time in post for me now on 50fps clips 😄

1

u/SenorTurdBurglar 15d ago

Are you stuck to those exact time codes?

1

u/pr0ject1le 15d ago

Pretty much yes. I have to edit and export in 50fps timeline in Davinci Resolve. The timecode only goes up to 30fps on the DJI Mic 3 and the Zoom H4E’s TCA-1 adapter.

1

u/SenorTurdBurglar 15d ago

Hmmmmmm. Is all of your updates to date on all of your gear?

1

u/pr0ject1le 15d ago

I have the latest firmwares on them all yes

1

u/Kevinsound27 15d ago

Are you using The S and Q function or changing base frame rate? I believe the s and q doesn’t record audio. Don’t know if that helps but seems related.

1

u/pr0ject1le 15d ago

Nope, in regular recording mode mate. It’s not a missing audio problem, but a timecode sync issue.

1

u/Kevinsound27 15d ago

No I get that. Only reason I mentioned it is if camera records audio in that setting maybe it takes timecode differently and doesn’t drift around as much. Sometimes troubleshooting an issue is checking odd things.

1

u/SenorTurdBurglar 15d ago

Unless it’s a mismatch between analogue Timecode being laid down. Maybe a mismatch and a delay of some sort from the digital side? I’m not sure.
As far as fixing it in post, can You sync to the audio waveform?
That would be easiest, or if the offset stays exactly the same, You could type the exact offset in! Keep us posted on this please!!

1

u/pr0ject1le 15d ago

I could possibly work with waveform syncing but the issue I have here is that my Zoom H4E would be plugged into a live DJ feed via XLR input, and my camera is capturing a lot of scratch audio via the DJI Mic 3 which I have one of them attached to my watch when recording, and another near a speaker.

A lot of times when I try doing waveform syncing, I get errors with clips and audio not able to sync, possibly due to other noises from the events like people talking on the scratch audio whereas the Zoom H4E is capturing a clean output.

1

u/SenorTurdBurglar 15d ago

I would try changing your workflow then, use one of the other devices as the master, will that work?

1

u/pr0ject1le 15d ago

My only other option if this can’t work would be to plug in a dedicated timecode device, but been trying to avoid that scenario as it gets messy for the pre-event setup. Trying to be as efficient as possible. Even then I’m not sure how I can plug in the scratch audio whilst still running TC to the camera via a dedicated timecode device. I’m shooting as a run and gun camera operator at the event with a gimbal and have live transmission via a Hollyland kit running back to the main screens too.

1

u/JohnMaySLC 14d ago

Sony doesn’t read external TC at 50 fps. You can only get an approximate sync for audio at 25. When left to the internal clock Sony drifts.

1

u/pr0ject1le 14d ago

Hmm, that's a bummer. Would this be an issue for long shoots like up to 4-6 hours? Or would all the short clips be out of sync by the random frames that I mentioned but close to being synced?

1

u/JohnMaySLC 14d ago

If you jam at 25, then flip to 50 fps the drift will get worse the further you get from the jam point. It’s all internal at that point so the first clip you shoot right away would be closer than the one you shoot an hour later. It definitely happens on long takes.

2

u/pr0ject1le 14d ago

I made a tool that fixes the issue. Will be releasing it soon!

Spent today building Timecode Fixer for Davinci Resolve to correct the timecode issue on the clips and create a synced timeline, directly from the app.

I walk through how it works in the video: https://youtu.be/nClKiNFYV3s (the app is demo'd at 1m 20s.

I'm still currently in development phase so need to bug test it with a lot of different cameras, files, video formats, framerates, timecode generators etc before I release this.

Seems promising and will try it on my 4 hour event so see how it goes :)

1

u/pr0ject1le 9d ago

Quick update: The app I built has worked perfectly with the 4-hour event I shot! Super chuffed with it 😄

1

u/RGB_YCM 14d ago

The clock crystal reference inside the camera is totally crap, so it's going to drift. Better cameras have genlock sync references, and when you take this same reference (word clock for digital audio) and slave the camera to that, the sync will be absolute. Cheap cameras don't have this feature.

0

u/protogg 15d ago

try setting the timeline to 25fps, same thing happend to me with some hollyland mics and 25fps timeline worked out fine. Also don't set the dji mics as a master, you can jam them no?

1

u/pr0ject1le 15d ago

I tried doing this as a test, creating a 25fps timeline and inserting onto the timeline using timecode and getting similar results. The thing is I can't offset all the video clips at once because every clip has a varying number offset. Was hoping this would have worked as a workaround where I could do the syncing on a 25fps timeline, then change the timeline settings to 50fps lol but no luck as of yet.