Time Code offsets: SMPTE vs QuickTime: Dealing with the offset

[Premiopolis]

We've got miles of footage with SMPTE time code typically capturing time of day.

We've got producers/writers viewing everything on QuickTime, VLC, and a transcription service all of which zero out the time code.

This creates heaps of file-specific TC offsets.

It's entirely possible to rectify the 0-hour-based scripts to the SMPTE sources by cuing to the beginnings of clips and typing "+TC:They:Read:Off:Their:Screen"

But it is hardly ideal.

We could also 0 out the TCs on all our source clips to match, which will cause a few other problems in the post-pipeline.

Avid has an interesting solution to the problem: Auxiliary Time code which is both set-able and cue-able.

So for the above-described workflow you would 0 out all the Auxiliary Time Codes, then set Aux TC as a "top-most" readout above the source monitor, and, behold, you can type in the zeroed TC directly into the UI and go directly to the proper cue point.  In this way you protect the SMPTE TC, respect the Zeroed TC from the Producer/Writer workflow, and achieve all around post-production mirth.

Is there a similar ability hidden somewhere in Premiere: That is, an ability to display an Aux TC that can be cued by typing into the UI?

[Jim_Simon]

The closest you could get is to put the clip you're working on into a sequence, which has a starting timecode of zero, then Match Frame that into the Source Monitor.

My own preference and the industry standard method here would be to create Windows Dubs for them to review so they can see the real timecode.

[Premiopolis]

Jim_Simon  wrote

The closest you could get is to put the clip you're working on into a sequence, which has a starting timecode of zero, then Match Frame that into the Source Monitor.

Thanks Jim.  Plus there's a solution in preferences that solves the more narrow problem outlined in the OP:

PPro > Preferences > Media > Timecode: > Start at 0:00:00:00  (as opposed to Use Media Source)

Jim_Simon  wrote

My own preference and the industry standard method here would be to create Windows Dubs for them to review so they can see the real timecode.

Agreed 100%.

Problem: E.P. "We don't have time for that" even though we're ready to go with a system that is automated and fast.

There's still the issue of handling TC offsets that DON'T involved 0-Hour time code vs SMPTE.

[Jim_Simon]

That preference can mess things up if you need to go out for color, effects or sound work, so test the full pipeline before working on a real project.

[Premiopolis]

Jim_Simon  wrote

That preference can mess things up if you need to go out for color, effects or sound work, so test the full pipeline before working on a real project.

Interesting.  So that setting impacts exported lists.

I'm assuming setting it back to Use Media Source resolves that particular issue?

[Trevor_Asq]

It's a toggle - just toggle it back before exporting any lists.

And adobe.com/go/wish for a feature request for "aux timecode like avid" - I expect there is already a request for it you can add your vote to

[Premiopolis]

Trevor_Asq  wrote

It's a toggle - just toggle it back before exporting any lists.

And adobe.com/go/wish for a feature request for "aux timecode like avid" - I expect there is already a request for it you can add your vote to

You're right, indeed: Timecode: allow numeric entry to go to source timecode – Adobe video & audio apps

[Trevor_Asq]

Look at that - I even started it myself! And a whole 7 votes, it’s a winner!!