Timecode generator is broken and buggy
Fix the timecode generator
Projectile Objects commented
Attila Lecza commented
It's a shame... This EPIC problem still there. Adobe doesn't give a **** about it. If Í drop a timecode on an Adjustment Layer, it will start with 01:00:00:00, unless you set it to 00:00:00:00, and your timeline is 00:00:00:00 too. Now I have to send HOURS of footages for scripting, and I'm ******* around on the net to get solution, and THERE IS NO SOLUTION! WTF!???
Johannes Klemt commented
Timecode Generator works on Windows but on Mac OS there is no Timecode Available at all. Are You serious? I pay so much money for the CC and this Issue ist still not fixed. Shame on you Adobe!
anthony mascorro commented
I've had timecode issues ever since I started a job that cuts on Premiere last year. The worst for me is that as far as I can tell, there's no way to get the timecode display on the Timeline or Program Monitor to display the Time of Day timecode attached to the clip. The reason this is important is that it's way, way more efficient to type or paste the timecode I'm looking for there and jump to that spot, rather than scrub through the timeline looking at the TOD timecode in the timecode window. If you work on a show where producers are scripting from transcripts, this is pretty essential, and it's incredibly easy in Avid. In Avid you type in the timecode, hit return and the playhead jumps there. Not being able to do this in Premiere is a serious hinderance to professional workflows.
Julian Neville commented
I'm still having this issue in Premiere 22.2.0. Incredibly annoying and debilitating for professional workflows. I'm an editor for high end commercials. Lately producers have been asking me what I think about switching to Resolve. I gotta say the type of bugs that constantly seem to come out of nowhere in Premiere are a reason to switch, but the timecode generator error really is Little League. If Resolve catches up on one or two more issues I'm switching. I've alreay given it a good test drive, and coming from Avid it's evident that Da Vinci has a much better grasp on what's important in postproduction pipelines.
John Tagudin commented
Hey, I got the solution for the timecode error on source monitor. See the attachment.
I just modify the timecode value on the video. Right click the video > look for modify > Timecode.
Daniel Leonforte commented
TC the newest version 14.3.1 Build 45 is still buggy! Adobe, please fix, such a essential feature needs to work!!! Even under GPU acceleration! It can´t be that users with state of the art hardware have to think everytime they want to use a tool, if it´s working or not! Can´t you understand, that we´re all people with normal needs? No fancy dancy extra thing! We want to go home after a working day without thinking the whole night how to build workarounds to the problems you make us!!!!!!!!!!!!!!!!!!!! So: fix it ASAP please!!!!!!!!!!!!
Ivan Ivanov commented
I can't believe that something so FUNDAMENTAL such as a timecode feature is COMPLETELY not working in Premiere. If applied as a plugin on my timeline it will not display AT ALL and if applied during export it is always OFF no matter what I try.
Lauren Wimmers commented
Please help i am desperately trying to hand over BUT THE TIME CODE IS ALWAYS WRONG - am running most recent update
sean kyt commented
Still having this Problem, is there a **** fix?
Alan Stuart commented
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!!!!!!!!
Terry Kelley commented
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.
Marcus Gillezeau commented
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.
Djordje Stamenkovic commented
The Software only is a temp fix but it would be great to have this problem fixed by Adobe!
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.
This is still an issue in 13.1.2 Build 9 Adobe please fix this ASAP.
Michael Kammes commented
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).
Harry Miller commented
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.
Harry Miller commented
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.
René Caron commented
Problem still there in 13.1.2. Definitely related to GPU acceleration. Using GPU acceleration (OpenCL or Metal) breaks the timecode. Software only is a the only workaround at a huge rendering speed expense. Guys fix this ASAP please! Unworkable in my situation cannot use this release as it is right now.