ASCII codes incorrectly parsed in metadata fields

BenH-Foundry · 2026-02-26T12:07:42+00:00

Issue – When importing an FCPXML, if you have ASCII codes in the string, they are incorrectly parsed in Premiere. (specifically here, " is returned as #34; instead of “) Steps to reproduce – * Import the attached sequence Expected result – The metadata “comment” for the sequence should be {“Test”} Actual result – The metadata comment is {#34;Test#34} Adobe Premiere Pro version – 26.0.1 (build 3) Operating system – Windows and Mac OS Comparative information this began occurring with Premiere Pro 25.4

4 replies
86 views
Translate

Issue – When importing an FCPXML, if you have ASCII codes in the string, they are incorrectly parsed in Premiere. (specifically here, " is returned as #34; instead of “)
Steps to reproduce –
* Import the attached sequence
Expected result – The metadata “comment” for the sequence should be {“Test”}
Actual result – The metadata comment is {#34;Test#34}
Adobe Premiere Pro version – 26.0.1 (build 3)
Operating system – Windows and Mac OS
Comparative information this began occurring with Premiere Pro 25.4

Sequence 01.xml

Stan Jones

Community Expert

@BenH-Foundry,

ASCII issues are always interesting to me, so I gave it a whirl. Win 11 only.

I have just updated to PR 26.0.1. I tested in 26.0.0, then after the update, tested mine again and opened yours.

When I open your sequence XML, I see what you describe in the comment field:

{#34;Test#34;}

In my project/test sequence, I used the Description and Comments fields, and added test, with and without quotes. And after seeing that you were using curly brackets, I added test with curly brackets and quote marks to the comments field.

In all of my tests, 26.0.0 and 26.0.1, and with and without curly brackets, I see only quote marks (no #34;).

Stan

Translate

BenH-FoundryAuthor

Participant

Thanks for looking. Yeah its not a problem with direct in and out of Premiere, it is only ingesting from other applications. (specifically we are generating an FCPXML that uses the ascii codes).

So if you edit the the xml to use the codes, you would see the problem.

Translate

R

Rach McIntire

Community Manager

Thanks for sharing the FCPXML — this is very helpful. I’ve filed a bug report based on what you described regarding ASCII codes in FCPXML metadata being incorrectly parsed in Premiere Pro 26.0.1.

A couple quick clarifications that may help:

Does this occur with all FCPXML exports or only from a specific application?
Which FCPXML version is being generated?
Does the issue affect only the “Comment” field, or other metadata fields as well?

If you have a project file or any additional sample files that reproduce the issue, you can DM me if that’s preferable. This will help the team confirm and investigate the behavior more efficiently.

Sorry for the trouble. I hope we can get clarity on this soon.

Translate

BenH-FoundryAuthor

Participant

This is a problem when exporting from our application, Flix. We write a dictionary of data into the metadata for tracking things going into and out of various applications.

This does not occur when exporting from Premiere directly, because the ascii codes are not written into the XML, the raw “ is used. We have to use the codes to ensure correct ingest across applications and platforms.

So the flow is: We export with the ascii codes > Import into Premiere > ascii codes are correctly interpreted > export from Premiere > its written the quotes instead of the ascii > all is good because they are the same thing.

The problem here is Premiere is not correctly swapping the ascii codes to the correct character. It is just removing the ampersand.

I will reiterate that this has worked for years, and broke in premiere 25.4.
I can use 25.3 and below without issue.

This is our version stuff.

<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE xmeml><xmeml version="4">

You can reproduce it in any field. I tried shottake and it did the same thing.

Translate

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.