Blackmagic Forum

I'm trying to export color corrected/edited video files while retaining the timecode from the source files. The source timecode is important with these files because I later use another program (Garmin Virb) to sync fitness data files (with video overlays) with the timecode of the recorded GoPro video files.

When I export Resolve uses the timecode from the timeline and not the timecode from the source files. I can confirm the original file timecode in the Media or Edit tabs in Resolve. After exporting files from resolve I verify the timecode is incorrect by importing the new files back into resolve and I can see the "Start TC" and "End TC" have been reset to match the time from the Timeline. I've read in the Resolve user manual (page 2517) that when exporting as "Individual clips" it should retain the source timecode, not the timeline timecode. I've tried multiple different options when exporting the video.

I'm using:
DaVinci Resolve 15.2.1.005
GoPro Hero 5 Black source video files

I've tried:
Exporting clips using "Media Management" in Resolve
Exporting using the "Deliver" section of Resolve (using both "Single Clip" and "Individual Files")
I've tried multiple different output formats/codecs, mostly .MP4/H.264

Any help would be greatly appreciated!

I'm still struggling with retaining the source file timecodes on export. I also tried the latest version of Resolve 14 and I have the same issue.

So, I ended up finding a workaround for my issue. I can do color correction, or some other edits using DaVinci Resolve, export the individual clips and use FFMPEG to copy the metadata information (including the timecode) from the original source files to the color corrected exported files. This method requires the framerate and video file length to be the same as the original files. Don't trim or edit the length of the files or the timecode will be off.

Replace the following sections:

You of course need ffmpeg in the path you're executing this from

<Video file exported from DaVinci Resolve> Path to the video file exported from DaVinci Resolve

<Original file with the correct timecode and metadata> Path to the original file with the correct Timecode

<Output Filename>.mov Exported filename (must be .mov, but, you can change it to .mp4 later for imported in some other programs)

Code: Select all

ffmpeg" -i "<Video file exported from DaVinci Resolve>" -i "<Original file with the correct timecode and metadata>" -c copy -map_metadata 1 -map 0:0 -map 0:1 -map 1:2 -map 1:3 -map 1:4 "<Output Filename>.mov"

The batch file below allows you to process all of the .mp4 files in a folder and correct the timecode. Save the code as a batch file and make sure to have FFMPEG in a "/bin" directory.

You'll need:

Have this batch file and FFMPEG in a "/bin" directory.

Directory with the source files in .mp4 format.

A directory inside the source file directory named "DaVinci Export" with the DaVinci Resolve exported .mp4 files.
All of the files in this directory must be named <Source Filename>_DR.mp4

Drag a source file onto the batch script and it will process all of the files and export them to a "\MetadataFix" directory and append "_MDF" to the end of the file.

The process doesn't re-encode the video so it's runs fairly quickly. Runs faster on an SSD because it has to read both source files and write the exported file at the same time. Just drag and drop any of the source files onto the script and it will run.

Code: Select all

@echo off
SETLOCAL EnableDelayedExpansion

:: Edit this to tell the script anything that has been postpended to the filename of the DaVinci Resolve exported files.
set postpend=_DR

:: Edit this to tell the script anything that has been prepended to the filename of the DaVinci Resolve exported files.
set prepend=

:: This is the name of the nested directory under the source file directory that contains the DaVinci Resolve files
set DaVinciExportPath=DaVinci Export

:: Shouldn't need to edit below this line.

Set SourceScriptDirectory=%~dp0

echo %~dp1
cd %~dp1
mkdir "%~dp1\MetadataFix"

Set OutputDir=%~dp1MetadataFix

 for %%f in (*.MP4) do (
   if exist "%OutputDir%\%%~nf_MDF.mp4" (
      ECHO.
      ECHO *************************************************
      ECHO ********** Output File already exists! **********
      ECHO *************************************************
   ) else (
         cls
         ECHO.
         ECHO *** Processing file: ***
         ECHO *** "%~dp1%%~f" ***
         ECHO.
         START "" /WAIT "%SourceScriptDirectory%bin\ffmpeg" -i "%~dp1%DaVinciExportPath%\%prepend%%%~nf%postpend%.mp4" -i "%~dp1%%~f" -c copy -map_metadata 1 -map 0:0 -map 0:1 -map 1:2 -map 1:3 -map 1:4 "%OutputDir%\%%~nf_MDF.mov"
         @echo on
         Move "%OutputDir%\%%~nf_MDF.mov" "%OutputDir%\%%~nf_MDF.mp4"
      )
   )

Hi, I am struggling with the exact same issue and it seems a little funny to me that such a seemingly simple feature still doesn't work or hasn't been properly implemented in the 5 years since this original post.

It would be very helpful for daily workflows to be able to export individual clips while retaining their original source TC.

As quoted from the manual in the first post, an export using the "Individual clips" setting will retain the source timecode and reel name. I have not encountered a single case where that didn't work.

Well I have here exactly such a case. Original camera data is BRAW with a timecode roughly equal to the time of shooting. When I export those as individual clips to mxf, the source timecode is lost and overwritten, starting now at 01:00:00:00

Here is a screenshot:



In the Media Bin you see that the exported MXF timecode starts 01:00:00:00, while you see the burned in original source TC to be starting at 09:43:44:06, meaning the clip was shot on 09:43am

Or am I doing something wrong?

After a lot of experimentation I found the problem:
Apparently you cannot activate "render timeline effects" in the delivery settings. This will overwrite the TC.
If you uncheck the box, the source TC is kept.

Is this a feature or a bug?

That's too bad - sounds like a bug. In the original implementation the ability to retain source timecode was required for round-tripping to the likes of Avid Media Composer, I'll bet.

Chiming in that I'm been having the same issue. Found your tip to uncheck "Render Timeline Effects" and that fixed it for me too. Thank you!

Hi,
I don't understand. I check show "Source TC" and "Rec TC", and both TCs that appear on the screen are the same, (expect the Rec TC has one hour extra as the Timeline starts at 1 hour). See attached image.
My goal is to export a bunch of files with the source TC (TC of the original media). This seems reall weird. Am I correct in thinking this is a bug and that when I choose show "Source TC" I should see the TC of the orignal files?!

SORRY - I just figured it out. The files provided have a "rec run" TC, so the first file starts at 00:00:00:00 and the second file starts off right after the TC of the previous file, and so on, which is why the SRC TC matchs (expect for the +1 hour) the REC TC.
PS I do not know the operator (he also shot in 50fps!), it is what it is.

Damien

yanuolin wrote:After a lot of experimentation I found the problem:
Apparently you cannot activate "render timeline effects" in the delivery settings. This will overwrite the TC.
If you uncheck the box, the source TC is kept.

Is this a feature or a bug?

Man , thanks for saving my life !!! I've been looking for this. This is a horrible bug. Now I got my TC back .. but the problem is I got many clips in my timeline using speed keyframing. With the 'render timeline effects' has to be off then it means I have to scrap it manually. Thanks Resolve for giving me more works

Hi everyone,
I'm running into an issue when rendering MXF OP-Atom proxies for Avid: the rendered files are not retaining the original source timecode, specifically with clips at 119.88.

Here’s what I’ve tried:
- Trying all color space settings
- Matching original FPS and project settings to 119.88
- Ensuring "Render timeline effects" is NOT enabled in render settings

This problem occurs with footage shot at non-standard frame rates—specifically 118.88 fps and 60 fps. However, footage at 29.97 fps renders just fine, with proper timecode retention.

Interestingly, when I export proxies as .mov, prores proxy, the timecode is preserved correctly. The issue seems isolated to MXF OP-Atom exports.

Has anyone experienced timecode issues with high or non-standard FPS footage when generating MXF OP-Atom proxies for Avid? Any ideas or workarounds would be greatly appreciated.