Skip to main content
Known Participant
August 23, 2024

#nbsp on burn-ins coming from Premiere

  • August 23, 2024
  • 21 replies
  • 1416 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

21 replies

Participant
March 14, 2025

Have you figured out how to stop this issue from happening? I tried all the steps people reccomended and it still happens. With no audio, still happens. Adobe media encoder is set to import from premiere natively as well. Is there a fix yet?

EckiAME
Community Manager
Community Manager
December 17, 2024

Still a bug then. Would you be able to share a small repro project for this?

Participant
December 16, 2024

I was having the same issue on the public version of 25 and after trying to trouble shoot it by trying loads of different settings. I found that if you go media encoder>settings>general and under Premiere Pro and tick the checkbox for 'Import sequences nativley' then it exports the sequences as you see and export in Premiere. 

EckiAME
Community Manager
Community Manager
October 29, 2024

If anybody has a reliable repro project for me, please let me know.

Participant
October 29, 2024

I had this exact problem when exporting with encoder, and found that the problem went away when I directly exported from premiere (v25.0.0)

laurab60501389
Participant
October 25, 2024

I had the same issue on 24.5.0 (metadata shows well during play out and export in Premiere, but has the nbsp error on all clips in Media Encoder), and for me it had the following origin;

 

At one time during the editing process, I imported part of a sequence from another project. That project seemed to come from a newer update, maybe it was even downgraded. All source files were the same, with a different timing in its clips. One audio file however, also had a standard power fade added, which I believe was the culprit. This happened via Media Browser as well as via copy-paste while having both projects open at once.

 

The solution for me was just removing that fade. For someone else removing all clip effects [Remove Attributes] on specific parts may work when the origin is unknown.

EckiAME
Community Manager
Community Manager
September 16, 2024

I guess I need a small project with media to repro. It did not repro for me using offline media.

Participating Frequently
September 12, 2024

I'm seeing this same issue in the public release of 24.5.

EckiAME
Community Manager
Community Manager
September 12, 2024

Got it. I was not able to repro in AME (Beta) 25.1.0.9. We would need the media to look into the issue more. 

a_levenAuthor
Known Participant
September 12, 2024

No, we are on a feature with multiple users and can not update to 25.0 mid-show.