Michael Romano
Well-known member
Had some trouble syncing audio in Resolve 9 Lite recently. Picture was RED EPIC. Audio recorder was a Zaxcon Diva.
On set we checked the Ambient TC lock-it box against the Zaxcon Diva, slate and EPIC. All of them matched by a human count off.
So I get into syncing and its all messed up. Resolve is WAY off by timecode. I synced everything by hand on the day (it was a commercial with only a few lines of dialogue anyways) and decided to revisit it when the production was over to find out what happened.
I choose one clip to try and sort it out with the following results:
----------------------------------------------------------------------
Resolve Lite 9
RESOLVE LITE 9 - AUDIO TC READS SLATE AT:
16:08:17:10
RESOLVE LITE 9 - VISUAL CHECK SEES SLATE AT R3D TC:
16:07:19:09
----------------------------------------------------------------------
Premiere Pro CS6.0.2
PPCS6 - AUDIO TC READS SLATE AT:
16;08;17;16
PPCS6 - VISUAL CHECK SEES SLATE AT R3D TC:
16:07:19:09
----------------------------------------------------------------------
HOLY HELL! THIS CREATES AN OFFSET OF:
00:00:58:07 (In PPCS6) & 00:00:58:01 (In Resolve Lite 9)
I thought this might be a DF / NDF issue but check this out:
Sound Devices WAVEAGENT ID's the BWF file as 23.97 ND
FROM RED EPIC MANUAL:
Drop Frame (DF) is not supported.
The audio file shows the ";" instead of the ":" in-between its TC numbers in PPCS6 leading me to think its a DF issue but Sound Devices Wave Agent reports the BWF as ND.
Audio Mixer said he had it set to 23.976 ND as well.
----------------------------------------------------------------------
WORSE YET:
Waveagent shows starting TC on the BWF at:
16:07:03:16
Resolve 9 shows starting TC on the BWF at:
16:08:01:17
PPCS6 shows starting TC on the BWF at:
16;08;01;25
----------------------------------------------------------------------
Somehow, it actually works syncing via TC in PPCS6, even though the application ID's a TC offset when you manually check where the slate occurs.
WORKS* WHEN SYNCING IN PPCS6.0.2
1 - Select both audio & R3D
2 - Radio box on "Timecode"
3 - Uncheck "Ignore Hours"
4 - Uncheck "Use Timecode From Clip"
* THIS APPEARS TO HAVE A 1 FRAME OFFSET (AUDIO COMES LATE 1 FRAME)
So it comes down to two very odd observations:
1 - Resolve reads the TC differently in audio files than PPCS6. In fact, Resolve, Waveagent and PPCS6 all differ.
2 - Even though the media reads a *horrendous* offset, PPCS6 manages to make it work within 1 frame.
----------------------------------------------------------------------
It is possible that this has pushed me over the edge of insanity.
If it is a Drop Frame issue, the only possible conclusion I have, how come the file is ID'ed as NDF?
Have I found a bug in at least two different pieces of software? Three pieces?
Anyone else have issues like this with these software and hardware combinations?
On set we checked the Ambient TC lock-it box against the Zaxcon Diva, slate and EPIC. All of them matched by a human count off.
So I get into syncing and its all messed up. Resolve is WAY off by timecode. I synced everything by hand on the day (it was a commercial with only a few lines of dialogue anyways) and decided to revisit it when the production was over to find out what happened.
I choose one clip to try and sort it out with the following results:
----------------------------------------------------------------------
Resolve Lite 9
RESOLVE LITE 9 - AUDIO TC READS SLATE AT:
16:08:17:10
RESOLVE LITE 9 - VISUAL CHECK SEES SLATE AT R3D TC:
16:07:19:09
----------------------------------------------------------------------
Premiere Pro CS6.0.2
PPCS6 - AUDIO TC READS SLATE AT:
16;08;17;16
PPCS6 - VISUAL CHECK SEES SLATE AT R3D TC:
16:07:19:09
----------------------------------------------------------------------
HOLY HELL! THIS CREATES AN OFFSET OF:
00:00:58:07 (In PPCS6) & 00:00:58:01 (In Resolve Lite 9)
I thought this might be a DF / NDF issue but check this out:
Sound Devices WAVEAGENT ID's the BWF file as 23.97 ND
FROM RED EPIC MANUAL:
Drop Frame (DF) is not supported.
The audio file shows the ";" instead of the ":" in-between its TC numbers in PPCS6 leading me to think its a DF issue but Sound Devices Wave Agent reports the BWF as ND.
Audio Mixer said he had it set to 23.976 ND as well.
----------------------------------------------------------------------
WORSE YET:
Waveagent shows starting TC on the BWF at:
16:07:03:16
Resolve 9 shows starting TC on the BWF at:
16:08:01:17
PPCS6 shows starting TC on the BWF at:
16;08;01;25
----------------------------------------------------------------------
Somehow, it actually works syncing via TC in PPCS6, even though the application ID's a TC offset when you manually check where the slate occurs.
WORKS* WHEN SYNCING IN PPCS6.0.2
1 - Select both audio & R3D
2 - Radio box on "Timecode"
3 - Uncheck "Ignore Hours"
4 - Uncheck "Use Timecode From Clip"
* THIS APPEARS TO HAVE A 1 FRAME OFFSET (AUDIO COMES LATE 1 FRAME)
So it comes down to two very odd observations:
1 - Resolve reads the TC differently in audio files than PPCS6. In fact, Resolve, Waveagent and PPCS6 all differ.
2 - Even though the media reads a *horrendous* offset, PPCS6 manages to make it work within 1 frame.
----------------------------------------------------------------------
It is possible that this has pushed me over the edge of insanity.
If it is a Drop Frame issue, the only possible conclusion I have, how come the file is ID'ed as NDF?
Have I found a bug in at least two different pieces of software? Three pieces?
Anyone else have issues like this with these software and hardware combinations?
