Incorrect Timecode on export

Has anyone else come across an issue where the Exported ProRes file's timecode doesn't match that of the project in FCP X?

It's a bit of an intermittent problem we've come across on Masters created from the MCR's edit suite. Sometimes the timecode will match (09:59:30:00) others will start from 00:00:00:00. Yesterday one master came through with time-of-day timecode (starting at the time the export was started). The File reports correctly in BlackMagic Media Express, but when played back through a HyperDeck it's different - if it's created on another Mac it's fine.

While not a huge problem with the workflow of that show, it could be an issue with file delivery of anything created on that system and cause confusion when mastering to tape (yes, tape is still thing we have to do). I don't experience this on exports from my suite, just from the MCR.

The system is running FCP version 10.2.2 on the last version of Yosemite (still afraid to update to El Capitan).

Anyone have any ideas before I waste too much valuable editing time looking in to it?

Phil

I have a similar problem...

I am currently working on subtitles for a feature film and I am noticing an increasing timecode delay between the project file and the .mov export (meaning that the delay starts with a few frames, and ends with a few seconds). My film is 100 minutes long.

What happened is that I imported an exported .mov version of my finished film into a new FCPX project in order to use the project's timecode to time the dialogue. The .mov version I imported does not have the burned in timecode. I timed all the lines and made an .srt file, which I then opened into my subtitle editor (Aegisub) only to find that all the lines were delayed. I used the same exported .mov file in both Aegisub and in the FCPX project. I also double-checked it, and the new project's frame rate matches the original and exported version's frame rate.

I'm afraid I'll have to re-time everything again manually... Any thoughts?

Thanks,
Shelly

We don't use any of those products for subs but, certainly, there has to be a user-specified timecode offset parameter in the interface.

Did you check if Aegisub interprets the video framerate in the right way?
(Video - > Show video details )

You could try to calculate how much the offset grows over a certain time.
That could help in finding out what causes the error.

This could be a difference in the type of timecode being used between the apps.

Check and see if they're both set as drop frame, or if they're both set to non-drop frame timecode.

If you exported a drop frame timecode from FCPX, and the subtitle software is EXPECTING to see non-drop, then you're timings will drift more and more over time.