Skip to main content
Known Participant
August 23, 2024

#nbsp on burn-ins coming from Premiere

  • August 23, 2024
  • 22 replies
  • 1526 views

Steps to reproduce:
    1. Apply Metadata burn-in in Premiere
    2. Send sequence to MediaEncoder

    3. Preview the preset in Premiere 
Result: Timecode burn-ins have #nbsp at the head, but this does not appear in Premiere.
Expected: See the burn-ins as they exist in Premiere.

 

 


System info
    Application: Adobe Media Encoder (Beta) v24.6.0.8
    OS: macOS v14.6.0, RAM: 64.00 GB GB, CPUs (logical): 24

22 replies

a_levenAuthor
Known Participant
August 28, 2024

It is tied to a clip in the audio tracks.  If I remove all audio tracks this issues goes away.  When I remove each track one at a time I am able to identify the track with the trouble clips, but it appears to be a combination of clips and not just one single clip in the timeline.

 

Either way, these burn-ins are looking at clips on the video tracks, not sure why audio tracks are causing the issue.

EckiAME
Community Manager
Community Manager
August 28, 2024

I was not able to repro Adobe Premiere Pro (Beta) 25.0.0.31 and Adobe Media Encoder (Beta) 25.0.0.31 on macOS 14.6.1.
I used a mov. Created a sequence. Applied "Metadata & Timecode Burn in". Added Timecode in line 1 and clip name in line 2. Exported to AME as H.264. Result looks fine.