Timecode offset 1 frame build 30.5.0

[Bryan Golder]

Red One/MX, 30.5.0, Sound Devices 702T, Denecke TS-2

702T -> jam the slate
702T -> jam the Red
Roll on the slate

Example result:

14:53:24:01 on the clip timecode (viewing in RCX build 247) = 14:53:24.00 visual frame on the slate

Is this a Red firmware bug that's been hanging around? I recall some talk about it a while back.

Thanks,
Bryan

 

[Trailangel]

This is normal.

 

[Bryan Golder]

How is not-in-sync "normal"?

Do you mean it's a bug which Red has yet to resolve?

It's certainly not correct.

 

[Conrad Hunziker]

Your slate doesnt take genlock, and it sounds like you didnt feed the camera genlock. So neither source knows WHEN that TC occurs in time. So both sources take the timecode to the current frame its capturing/displaying which may not start at the same instant on both devices.

Genlock is the drummer in the band. Without it, you just have a bunch of instruments playing, not knowing when the beat is. They may be in perfect pitch (speed), but they dont know when exactly to play the note.

So +/-1 frame is normal in this case. You'll get the same results with just about every camera out there if you dont genlock them.

 

[Trailangel]

How is not-in-sync "normal"?

Do you mean it's a bug which Red has yet to resolve?

It's certainly not correct.

Time Code is not sync. TC is Positional reference, and one to four frames off is normal. This is what assistant editors are for.... re-sync. There could be a 1 frame delay in the readout of your slate. Get over it.