deliver clips with specific start timecode

I'm delivering my timeline as "single clip", however marking one individual clip (in/out).
In the file settings, I set "each clip starts at frame 1" and "start timeline timecode at 00:00"
Still, the delivered clip starts not at zero, but at the timecode of its position in the timeline.

Any ideas what I am doing wrong?

bump

I'm not seeing those checkboxes make any difference in Studio 18.1.4 on Windows 10.

But then reading the manual, I'm not sure I really understand their purpose.

I'm not seeing those checkboxes make any difference in Studio 18.1.4 on Windows 10. But then reading the manual, I'm not sure I really understand their purpose.

Thank you very much for getting back.

According to the manual, "Start timeline timecode at" should work "When rendering Single Clip" and "Specifies the timecode that will be written to the media being output", writing the timecode "to the appropriate metadata container."

So it should do exactly what I need.

Would you maybe want to check if it's not working on your machine neither, so it could be flagged as a bug?

If it's a MOV/MXF export then you can overwrite start TC with AMCDX tool.

If you do normal (single clip export) timecode should be written and normally it's.
It's copied from timeline start TC or you can overwrite it with setting in Export/File tab.
If you render IN/OUT then it will be most likely taken from IN position within timeline. In such a case you may need to overwrite it with mentioned export setting.
What is your export container, MOV?

If it's a MOV/MXF export then you can overwrite start TC with AMCDX tool.

Thanks, seems to be a great workaround without reencoding

It's copied from timeline start TC or you can overwrite it with setting in Export/File tab.
If you render IN/OUT then it will be most likely taken from IN position within timeline. In such a case you may need to overwrite it with mentioned export setting.

I do render in/out and check settings to overwrite it. But it doesn't work.

What is your export container, MOV?

mov

The "Start timeline timecode at XX:XX:XX:XX" setting on the Deliver page just sets the start timecode for the timeline. When you're rendering from an In point on that timeline it will have the start timecode plus the offset of the In point.

The "Start timeline timecode at XX:XX:XX:XX" setting on the Deliver page just sets the start timecode for the timeline. When you're rendering from an In point on that timeline it will have the start timecode plus the offset of the In point.

Ahhhh, that makes sense.

Not sure if this is a useful behaviour to someone. In any case, I'd say it is not what is stated in the manual ("Specifies the timecode that will be written to the media being output by DaVinci Resolve").

The "Start timeline timecode at XX:XX:XX:XX" setting on the Deliver page just sets the start timecode for the timeline. When you're rendering from an In point on that timeline it will have the start timecode plus the offset of the In point.

This is incorrect behaviour for me.
Overwrite should always set final TC regardless how you setup export (use IN/OUT or not etc).
I don't think any other tool does it this way. Don't like it at all.

I would agree, but the setting is called "Start timeline timecode at" which muddies it a bit.

I had the same interpretation of the manual as Roger. But I also agree with Andrew on how it should work.

Or at least, there should be some way to make that happen.

This is incorrect behaviour for me. Overwrite should always set final TC regardless how you setup export (use IN/OUT or not etc). I don't think any other tool does it this way.

I also don't see in what circumstances this kind of behaviour could be useful.

Not sure if this should be reported as bug or feature request.

It's very possible it's a bug as well, so can be reported as bug or as a feature request.
One or another- should be fixed or improved, so we can properly force start TC.

It's very possible it's a bug as well, so can be reported as bug or as a feature request.
One or another- should be fixed or improved, so we can properly force start TC.

Is there a bug report sticky thread, or only one for feature requests?

I've posted a feature request, in case someone wants to subscribe:

viewtopic.php?f=33&t=178747

If it's a MOV/MXF export then you can overwrite start TC with AMCDX tool.

Do you know of any tool who would be able to set TC for more than one clip at a time?

Same tool in cmd line mode+ small shell script.

Same tool in cmd line mode+ small shell script.

I don't manage to do this. AMCDXVideoPatcherCLI.exe works with a json script, but I don't get it working directly. Maybe you could spare an example? This is what I'm trying right now:

AMCDXVideoPatcherCLI.exe "{ "processor": "mov_meta", "params": {"video_file": "00001.mov", "timecode": {"tc": "00:00:00:07"}}}"

In the meantime I found that the string quotes were missing (as in the example on the amcdx website). So I'm trying now:

AMCDXVideoPatcherCLI.exe "{\"processor\": \"mov_meta\", \"params\": {\"video_file\": \"00001.mov\", \"timecode\": {\"tc\": \"00:00:00:07\"}}}"

However, no I'm getting a "this app can't run on your pc" error...

Try to google this issue on PC.
Sometimes compatibility mode helps, sometimes copy of your exe to new location...more on google.

AMCDXVideoPatcherCLI.exe "{\"processor\": \"mov_meta\",\"params\": {\"video_file\": \"D:/test.mov\",\"nclc\": {\"in_file\": true,\"primaries\": 2,\"transfer\": 2,\"matrix\": 2},\"gama\": {\"in_file\": true,\"gamma\": 2.4}}}"

AMCDXVideoPatcherCLI.exe "{\"processor\": \"mov_meta\",\"params\": {\"video_file\": \"D:/test.mov\",\"timecode\": {\"tc\": \"00:00:00:07\"}}}"


both worked for me (Win 10 Pro 20H2).

Thanks, I got it working now individually on the cmd line. But not as a batch script. Maybe a problem of to many escaped string characters?

forfiles /m *.mov /c "cmd /c echo file: @file && AMCDXVideoPatcherCLI.exe \"{\"processor\": \"mov_meta\", \"params\": {\"video_file\": @file, \"timecode\": {\"tc\": \"00:00:00:11\"}}}\""

Not sure- don't like PC's shell
I had crazy cases when on Pc I had to use """"" (5x") to avoid escaping problem.
I use Python

Not sure- don't like PC's shell
I had crazy cases when on Pc I had to use """"" (5x") to avoid escaping problem.
I use Python

Could you point out more or less how this passing of arguments would work in python?

Since you're on Windows you can use the more modern and much better PowerShell. It's installed by default. Save as Set-Timecode.ps1. Instructions are in the code.

Code: Select all

[CmdletBinding()]
param
(
   [parameter(Mandatory = $true)]
   [string] $Path,

   [parameter(Mandatory = $false)]
   [string] $Filter = "*.mov",

   [parameter(Mandatory = $false)]
   [switch] $Recurse,

   [parameter(Mandatory = $false)]
   [string] $Timecode = "00:00:00:00"
)

<#

   If you haven't set an execution policy in your system, do this before running the first time:

   1. Start PowerShell as Administrator
   
   2. Execute this to allow scripts created on your computer to run (but not unsigned scripts downloaded from elsewhere):
      Set-ExecutionPolicy RemoteSigned -Force
   
   You can now run the script from PowerShell (doesn't have to run as Administrator):
   .\Set-Timecode.ps1 -Path "D:\Renders\MyProject" -Recurse -Timecode "00:00:00:11"

#>

# Enter the full path to AMCDXVideoPatcherCLI.exe here
$amcdx = "z:\Downloads\AMCDXVideoPatcherCLI.exe"

foreach ($file in Get-ChildItem -Path $Path -Filter $Filter -Recurse:$Recurse -File)
{
    $json = "{ ""processor"": ""mov_meta"", ""params"": { ""video_file"": ""$($file.FullName -replace '\\', '\\')"", ""timecode"": { ""tc"": ""$($Timecode)"" } } }" -replace '"', '\"'
    & $amcdx "$json"
}


Since you're on Windows you can use the more modern and much better PowerShell. It's installed by default. Save as Set-Timecode.ps1. Instructions are in the code.

Fantastic! Thanks a lot for this. I had tried myself with powershell, but found it to have the same problem with escaping as the cmd line.

Your script works like a dream, saving me an enormous amount of time to manually reset delivered clips' timecode to zero.