Media Encoder showing {nbsp} with source timecode using Metadata Timecode and Burn-in from Premiere

[andrewp53113852]

I imagine this may have been brought up before (but didn't find any mention in my subject search), but Media Encoder 25 is displaying a bug where Metadata Timecode and Burn-in effect is used for a sequence on a Transparent layer. It will export fine out out Premiere, but once sent to Media Encoder, it will show {nbsp} as part of the source timecode.

Some other forums suggested checking on Import Sequences natively in Media Encoder, which sometimes solve the issue, but then occasionally double burns-in temp LUTs into the output for no clear reason. This issue isn't exhibited when exporting straight out of Premiere.

 

I'm confused why this is occurring, and having to export multiple sequences straight out of Premiere is inefficient.

I'm using a Mac M2 Ultra on Sonoma 14.6.1

[andrewp53113852]

Some further digging has focused the bug when adding a Metadata Label. In this case it's making sure SRC TC is included. When that's disabled, the {nbsp} disappears.

Whenever adding a Metadata Label like Sequence Timecode or Source Timecode, this bug reappears.

[bbb_999]

Weird!

Can you provide a project (we shouldn't need media) containing a sequence that exports correctly from PPro, but fails as described when exported via AME?

[Rach McIntire]

Hi @andrewp53113852,
What font are you using? Have you tried a different font?  Can you try it without any spaces to see if that may be part of the issue?  Sorry for the frustration and thanks for reaching out.

[andrewp53113852]

There is unfortunately no font option when using the Metadata and Timecode Burn-in effect in the Effects Panel.

[elijah_6843]

I am also having this problem, and it seems to be directly tied to the effect "Timecode and Metadata Burn-In" and the way that it's interpreted by Media Encoder, because it presents no problem for anything rendered out of Premiere natively, but instead only shows up when trying to run anything through ME.

There is no font attached to it, as the effect is in control of that, and it doesn't seem to matter whether I include the metadata label or not either, it always adds #{nbsp} before my timecode, whether it's SRC, CLIP, GEN, etc.

This has been a problem at least since the 2024 release.