Final Cut Pro inserts wonky timecode

[Jared Lorenz]

Here is the update as of 8:20pm.

This is a documented issue with 23.976 frame rates and FCP:
https://discussions.apple.com/thread.jspa?messageID=10157610

What isn’t documented is how to get it to work. People have suggested setting up a new Easy Setup with deck control and so on all set the way you want them. Done. Still no go. I have switched over to the Aja IO now, and as documented above, same issue.

Surely SOMEONE on this forum must lay off 23.98 material to tape on a F500 deck. If so, may that someone help me, please.

[Shane Ross]

Wish I could help. I have output 4 shows that were DVCPRO HD 720p 23.98 to HDCAM at 1080PSF 23.98. But I didn’t do the layback, I took the files to a post house and had them do it. Kona 3 to the deck. ANd I have an SR deck here, but don’t know it well enough to tell you what to do. This is VERY possible, I know that…

Shane

GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
Read my blog, Little Frog in High Def

[Jared Lorenz]

What kills me is that I’VE DONE IT TOO. Obviously I did something different.

Deck gods, may ye smile on me tomorrrow.

[Jared Lorenz]

I am just posting this in hopes of someone coming up with a solution.

Again here is the config (revised slightly from yesterday).

FCP6 / OS 10.5 Mac Pro 8core2.8ghz
Aja IO HD w/ latest drivers
Tri level sync set across the board to 23.98 sf
AJA IO HD set to 1080psf2398
Ext video and ETT settings 1080psf23.98
Device control set to RS422 (sony) 23.98 fps
F500 deck set to 23.98psf, LTC timecode with VITC set to follow LTC
rental house has confirmed deck settings are OK.

The problem is that when I go to black and code from final cut I cannot enter the timecode at 58:00:00 – it replaces that code with 46:26:24. Same case for the in point on edit to tape. Whatever timecode I enter is translated into a junk timecode.

Going to cross-post on the IO forum since I am sure someone there has done this before. Help.

[Joey Burnham]

This sounds like another reference issue. Kona 3 here but there has to be a way with the IO.
I’ve had this problem before and pretty sure that fixed it.
Joey

[Jared Lorenz]

You’re right.

It’s now confirmed with all parties that the deck was throwing errors. No matter what signal we sent it, it saw a 59.94 reference signal. VITC and LTC would not match and the timecode striped to tape, even though it was set to 23.98, was being seen by FCP as 29.97, hence the inability to enter a timecode accurately.

Deck went back, now we’re waiting for a replacement.