[Bouke Vahl]

If you have an audio channel to spare, you can capture without machine control, and feed the TC to an audio channel.
(I assume you have a TC OUT connector on your deck. No matter the connector (probably a BNC), it is an audio signal)

Then, use my Aux TC reader:
https://www.videotoolshed.com/product/26/fcp-auxtc-reader

It can analyze the entire clip, and create new clips (self contained or reference) based on the breaks.

It also comes with helper applications to easilly sync your BWF’s to the new clips.

hth,

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

Yes, i do. and you?
Did you look into your (sequence) settings?

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

I don’t quite follow you.
Sure, TC can have overlaps (and if you have a multicam shoot, it definitly will!), but if you do your work well, you have different Reelnames for all sources, hence make it so that each and every frame is unique.
Or do i miss the point?

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

Drop / non-drop changes nothing to the video.
It’s just how the TC is written.
So, depending on how you do your export, change the TC to drop before you do the export.
Now, adding the pulldown is something to worry. You want normal pulldown, not Advanced pulldown! And i’m not sure if FCP can do that.

What other tools do you have at hand?

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

Try QTchange.
The 60d has an embedded THM file, that QTchange can extract (or read and add timecode)

Thus, you can give the files TC, and / or extract the THM file, and let it travel with the transcodes, and add TC to the new transcoded files.

https://www.videotoolshed.com/product/42/qtchange

hth,

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

well, i don’t know ITX nor your transcoder, but:
If you import the QT back into FCP, what TC does it have then?

If that is indeed the 10:01:30:00, your transcoder is retaining the QT TC. That should be normal. You then only have to export the QT with the correct TC, or alter it.

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

I now concider this as a feature request for QTchange…

But since QTchange can do a shitload of things, and i’m not going to compete with FFmpeg (i would if i could, but i’m mortal), what should be supported for a start?

(best to take the conversation off list i suppose…)

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

This makes no sense whatsoever.
A QT timecode track CANNOT be discontinuous. This is out of specs.

So the problem lies elsewhere.
Do note, QT TC is a QT track. That can be duplicated / edited / copied / pasted.
You can have virtually unlimited TC tracks in one file, but it depends on the host to decide what track to use.

You can have a mismatch between video FPS and TC fps. So it is very well possible to paste a 3 fps TC track onto a 25 fps video track.

You could delete the TC track and start without TC. that should solve the issue.
Or, refresh the TC track (Use my QTchange to do so if you have more than a few clips to process)
But how are you transcoding to MXF? Trough FCP? I have never ever have encountered trouble in an FCP MXF export…
(and i’ve done a fair share of them for automated playout…)

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

but the good news, i just saw Michael Phillips is hanging around here.
Now if anyone knows about Avid, it’s Michael. (And he’s a nice guy too!)
Could not hurt paging him…

Bouke

https://www.videotoolshed.com/
smart tools for video pros

[Bouke Vahl]

Peter,
well, as stated before, i have NO idea what is happening, and i don’t know daVinci.
But i’m a general TC geek.
Your problem IS a df / ndf issue, since the difference is EXACTLY a df/ndf mismatch.
Now we agree that there should not be DF in 23.976, but do the math, this is no coincidence since you gave two matching examples.

I can give you an analyzer tool to see what i think should be the correct timecode, as well as what i think that goes wrong.
(daVinci using an old version of AvidMXFinfo…)

But what good would it do? I would contact tech support…

Bouke

https://www.videotoolshed.com/
smart tools for video pros