Burned-in timecode only displays when playing or scrubbing in sequence and won't export Premiere Pro

This worked for me! Thank you!

Just had the same issue using 25.0.0 for the first time with this effect on the individual clips. 1080 timeline had UHD clips and the effect could only be seen when playing.  The TC could be seen in media exporter, but did not appear on the file created. Added a transparent layer and put the effect there and now it can be seen on the exported file

pigsalreadyfly

This worked ! Thanks so much!

The fix for this is to make SURE you are adding the effect onto a transparent video layer that is created when you have your sequence open, that way it's the same resolution as you sequence. If the transparent video layer or adjustment layer is a different resolution, it glitches the metadata and timecode effect as you described. I just encountered this and fixed it this way.

Hi @Steve Wildside thank you for the information.  I can repro and have logged a bug.

I also have this issue. Mac Studio M3. Metadata & Timecode Burn-in Plugin. When paused the timecode disappears. When playing it shows up just fine. I have gotten around this by using the (obsolete) Timecode plugin. It does show up when paused or playing. 

I updated to Premiere Pro version 24.4.1

I believe this is the latest version. The disapearing BITC display is still the same.

Cheers,

Steve

The picture is fine on the HD monitor. The problem is that the burned-in timecode box disapears as soon as the play head is paused in the sequence. Also, if I export I get a perfect exported video file except that the burned-in timecode doesn't feature. No rectangular black box with timecode numbers in it. It's very strange.

Cheers,

Steve

I'm puzzled about this. I can have a UHD sequence, playing it back on a 1920x1080 monitor, and see the whole image just fine. The monitor pixel dimensions shouldn't matter.

Hence my puzzlement.

Hi,

I had just one 30 minute clip on a sequence and applied the 'burned-in timecode' effect to that clip. I've now updated to the latest version of Premiere Pro and still have the same issue.

However, after some experimenting, I've now found what I am doing that causes this. My original camera rushes have been shot on a Sony FS7 in UHD 25p. So 3840x2160. I've dropped them onto an HD 1920x1080 sequence which allows, with the equipment I have, for me to monitor on an HD video monitor. The UHD clips are scalled to 50% so I can view the entire picture. Changing the sequence to 3840x2160 solves the 'burned-in timecode' problem (but I can't monitor on the HD video monitor of course). It will now display the BITC all the time, not just when the sequnce is in play. I've also been able to export a small H.264 viewing copy and this time with the BITC.

My final masters will be HD 1920x1080 and will be a mix of UHD and HD material. I've worked like this for some years and it gives several advantages, not least the ability to crop in on UHD footage and move around inside a shot without losing quality for HD export. It also allows for real time monitoring on my grade one HD video monitor. I've worked like this and used a very large number of effects on UHD shots in the past on 1920x1080 ProRes sequences and I've been impressed that it has always worked in real time, usually without the need for rendering to view in full quality.

So this is the first time there's been an issue when working this way. I'm exporting the rushes using UHD squences now and the BITC is working and exporting correctly now.

These are just basic rushes for client viewing at this initial stage. So now I know what causes the issue I can work around the problem. However, it would be useful if the BITC generator would work normally even after scaling on a different resolution sequence. maybe a future fix?

Thanks,

Steve