Ok sooooo after much back and forth, my issue got fixed by deleting fonts in my iMacs font book ( duplicate fonts ), have no idea how this fixed the issue but Adobe Tech support did it for me, and it worked ....I HAVE TIMECODE OVERLY AGAIN!!!!!!!!

T

Terry Kelley

Known Participant

I'm an ACE editor, professional for 35 years. WTF is up with this stupid problem with timecode burn-in? It absolutely prevents me from using Premiere for professional work.

M

marcusg82263131

Participant

I'm on PP 13.1.5 trying to get burn in TC to appear on a transparent or adjustment layer. But no numbers appear at all. I've cross tested on my laptop and it works. Adobe tech support spent 2.5hrs trying to fix with screen sharing, but they failed to get it working.

They tried changing the render engine. I've tried a full uninstall/reinstall. I've updated the operating system. On a Mac Pro 2013 3.5 GHz 6-Core Intel Xeon E5 so plenty of grunt.

Is it something to do with the settings in sequence? It's like the effect can't see any TC.

Weirdly, when I export the sequence to Media Encoder and try to apply a BITC there, same issue?

Any ideas welcome. I really need to get transcribing of the interviews done asap for this doco.

F

FeedbackCommunityMemberAuthor

Inspiring

The Software only is a temp fix but it would be great to have this problem fixed by Adobe!

F

FeedbackCommunityMemberAuthor

Inspiring

After spending time talking to Adobe over the last week, I was able to get them to fix the bug in Premiere where the timecode overlay from 24fps sequences was incorrect when using the Mercury Engine (Hardware Cudu). The update was released today. v13.1.3 Hopefully this will address the issue most people here where having.

F

FeedbackCommunityMemberAuthor

Inspiring

This is still an issue in 13.1.2 Build 9 Adobe please fix this ASAP.

M

mkammes

Participating Frequently

I'll add to the chorus; something is awry. I typically use it on an adjustment layer over the entire sequence for a timecode window burn. The starting TC is never right, and the offset doesn't allow for enough flexibility to correct for it. Yes, this is with CUDA acceleration (CC 13.x).

F

FeedbackCommunityMemberAuthor

Inspiring

Here is the work around: switch the Mercury Playback Engine to Software Only. In Premiere you go to File\Project Settings\General. In Media Encoder you go to Preferences\General\Video Rendering. That is only for exporting media. This give accurate sequence and clip timecode burn ins.

F

FeedbackCommunityMemberAuthor

Inspiring

Premiere Pro 13.1.2 (build 9), and Media Encoder 13.1 (Build 173). I'm hoping my frame grabs will upload to show that outputting a sequence (1920x1080, 24 fps, ProRes 422 HQ media) to Media Encoder (by selecting Queue), adding a Timecode display effect, the timecode displayed is WRONG.
1) The sequence starts at 00:59:40.00. This frame shows the burnin at 00:59:36.10. 2) Adding a frame offset of 86 frames to start the sequence at 00:59:40.00, the last frame of picture the timecode is way off (54 frames). 3) Changing the timeline frame rate to 25 (and no 86 frame adjustment), the start timecodes match. 4) The last frame of picture the timecode is 1 frame off from the burnin (the burnin is wrong).

Timecode doesn't work correctly as an adjustment layer, displaying incorrect timecode for the sequence AND the clip, and Media Encoder doesn't at all display the correct timecode.

Very serious items to fix.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded