Timecode of .WAV file not matching video file when sound synced

Forum|Forum|11 months ago
February 17, 2025
3 replies
565 views

I hoping the experts here can help with a problem I'm having today. I'm sure there is a simple fix or explanation but it's alluding me and the sound technician. He recorded to a Sound Devices mixer at 23.976 and Camera at 23.976 and Slate showing the Timecode for takes. When I import the video and wav files place them in a 23.976 sequence and sync the files using Audio Channel one, the WAV files timecode no longer matches the Slate Video Timecode. Sometimes around 54 seconds off. I conducted a test on my own Sound Devices today and also have the exact same thing, mine was less around 14 secs offset from the video showing the timecode on the mixer. So the mixer shows 04:00:50:07 the waveform file recorded and then synced shows 04:01:04:19. I'm missing something here and can't figue it out. If I try to use timecode to sync the camera to the wav file it does not work. It's off by that same 00:00:14:12. We both checked and the devices are running at NDF 23.976 record. Overlay shows the WAV timecode in the test - look at the visual display, that should match the overlay timecode.

D

dave_beatyAuthor

Inspiring

One reason this usually doesn't come up is that even if we did jam sync time code to the cameras and the audio files they would match so we don't normally look at the time code slate number.

R Neil Haugen

Legend

I think ... though I'm not sure ... that you're talking about the duration of the video, not the say beginning time code point?

Everyone's mileage always varies ...

D

dave_beatyAuthor

Inspiring

The slate is jam synced to the Sound Devices. But when I line up the .WAV with the Camera at clacker point, the Slate display and the WAV timecode in PPro do not match. I have the files here if anyone want's to look at this. I tried it on my own Sound Devices and had the same issue. I checked the Metadata on the WAV and it is reading the starting frame correctly. I'm sure it's something I'm overlooking but I can't figure it out.

D

dave_beatyAuthor

Inspiring

No. In this case they didn't Jam Sync the two cameras for some reason. So I don't have TC on the MOV files. But I have the TC slate with the running timecode. The WAV files should be in sync with that slate. But it's offset. In the case of the main shoot, about :55 secs off all day. The Slate is showing the same TC as the display on the Sound Devices Mixer on the shoot. So WAV files should also be in sync with slate. When the slate is marked, the timecode on the slate clapper, sould match the audio sync of both "CLICK" and TC. But it doesn't.

Let me drop a test of MOV from a iPhone that shows Slate, Mixer and then the WAV recorded. Use PPro to do an audio syn to channel one and you'll see the TC in the visual does not match the TC on Overlay view of Audio 1 or Audio 2 in PPro from the WAV file : https://www.dropbox.com/scl/fo/8zr1vftqfkh15nd7lsils/ABSJU1kgCeAMwhq09rAxx5I?rlkey=r9jw4zf0byzjwy5l9bi96trz3&st=4downb0n&dl=0

D

dave_beatyAuthor

Inspiring

My Next step is to load these clips into a previous version of PPro to see if the .WAV is still reading in at the wrong timecode. Is there a util that will read the timecode meta-data outside of Adobe? At one time I was informed the timecode of these audio files is in the metadata as start frame only and the software interprets the rest. Since this happened on two Sound Devices mixers using 23.976 timecode, I'm thinking it's related to that. I'll also look at 29.97 timecode. And do some tests recordins on the mixer.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded