• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
2

#nbsp on burn-ins coming from Premiere

Participant ,
Aug 23, 2024 Aug 23, 2024

Copy link to clipboard

Copied

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.

 

Screenshot 2024-08-23 at 11.47.22 AM.png 


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

Bug Unresolved
TOPICS
Bug

Views

522

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
19 Comments
Adobe Employee ,
Aug 28, 2024 Aug 28, 2024

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Participant ,
Aug 28, 2024 Aug 28, 2024

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Aug 28, 2024 Aug 28, 2024

Copy link to clipboard

Copied

Can you share a minimum repro project so we can look into the issue? I can private message you the instructions in this forum.

Votes

Translate

Translate

Report

Report
Participant ,
Aug 28, 2024 Aug 28, 2024

Copy link to clipboard

Copied

I messaged you, please let me know how I can send a PrP file.

Votes

Translate

Translate

Report

Report
Participant ,
Sep 09, 2024 Sep 09, 2024

Copy link to clipboard

Copied

Following up on this.  I sent you a sequence for testing in a DM.  Please let me know if you have been able to troubleshoot,

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Sep 10, 2024 Sep 10, 2024

Copy link to clipboard

Copied

I am not able to access your files. Please review your private messages inbox.

Votes

Translate

Translate

Report

Report
Participant ,
Sep 10, 2024 Sep 10, 2024

Copy link to clipboard

Copied

Please check your inbox and try again.

 

Thank you!

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Sep 12, 2024 Sep 12, 2024

Copy link to clipboard

Copied

Thanks for your project file. I was not able to repro your issue on macOS 14.6.1 (MacBook Pro 16", 2021, M1 Max) using Adobe Premiere Pro (Beta) 25.1.0.10 and Adobe Media Encoder (Beta) 25.1.0.9. I opened your project in PPro and sent it over to AME. The result shows offline media and metadata text but now " ".

Votes

Translate

Translate

Report

Report
Participant ,
Sep 12, 2024 Sep 12, 2024

Copy link to clipboard

Copied

Can you please try using MediaEncoder 24.6 Beta?  That is what I am using when I see this error.  Also, to be clear, I am working within an Production with shared projects.  All users are on the same version of Premiere and MediaEncoder and all users are seeing this same issue.

Votes

Translate

Translate

Report

Report
New Here ,
Sep 12, 2024 Sep 12, 2024

Copy link to clipboard

Copied

Hi @a_leven , I am on the same version here and am experiencing the same issue.  The burn-ins look as expected in PR, but the output file includes '#nbsp' header.  Please advise.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Sep 12, 2024 Sep 12, 2024

Copy link to clipboard

Copied

Beta versions are now at 25.0. Would you be able to test on this version?

Votes

Translate

Translate

Report

Report
Participant ,
Sep 12, 2024 Sep 12, 2024

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Sep 12, 2024 Sep 12, 2024

Copy link to clipboard

Copied

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. 

Votes

Translate

Translate

Report

Report
Community Beginner ,
Sep 12, 2024 Sep 12, 2024

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Sep 16, 2024 Sep 16, 2024

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
New Here ,
Oct 25, 2024 Oct 25, 2024

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
New Here ,
Oct 28, 2024 Oct 28, 2024

Copy link to clipboard

Copied

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)

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Oct 29, 2024 Oct 29, 2024

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
New Here ,
Dec 16, 2024 Dec 16, 2024

Copy link to clipboard

Copied

LATEST

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. 

Votes

Translate

Translate

Report

Report
Resources