Skip to main content
Participating Frequently
April 2, 2025

CEP BUG - Can't set Column.PropertyText.OriginalAudioFileName

  • April 2, 2025
  • 10 replies
  • 897 views

Hello, 

 

I have an ALE metadata tool I've developed and from all of my testing I'm finding that I can't update the Original Audio File Name field using the setProperty() function on a XMPMetaInstance. 

 

For example:

 

  var kPProPrivateProjectMetadataURI = "http://ns.adobe.com/premierePrivateProjectMetaData/1.0/";
  var xmp = new XMPMeta(childItem.getProjectMetadata());
  xmp.setProperty(kPProPrivateProjectMetadataURI, "Column.PropertyText.OriginalAudioFileName", "MyWaveFileData.wav")
  var xmpAsString = xmp.serialize();
  childItem.setXMPMetadata(xmpAsString);

 

This works completely as expected when updating any other default property, such as 

Column.PropertyText.OriginalVideoFileName.
 
Also, when I use dumpObject() I can see the Column.PropertyText.OriginalAudioFileName property, but premiere isn't reading it correctly, and will display incorrect data. See screen grabs and txt file attached.
 
Peremiere 2025 (25.1.0)
MacOS - 15.3.2
 
 

 

10 replies

Bruce Bullis
Community Manager
Community Manager
May 6, 2025

Thanks Dave, the package was very helpful. 

You're right, something is going wrong within PPro; we're tracking the issue as DVAPR-4257906, and we'll keep you informed of our progress. 

Participating Frequently
April 3, 2025

Thanks, Burce. Sent you a package!

Bruce Bullis
Community Manager
Community Manager
April 2, 2025

The video was helpful, thanks!

I propose you send me your panel, and some import-able .ALE files with blobs of data that reliably reproduce the problem you recorded.  🙂

Participating Frequently
April 2, 2025
Participating Frequently
April 2, 2025

*and I can update Original Video File Name with an ALE in an existing project as expected.

Participating Frequently
April 2, 2025

Thanks again Bruce, I'm just not seeing that function working for me at all the way you describe. I think what you're suggesting is that the data field is derived from the media? And by using changeMediaPath() then I should see that field updated? 

 

I can clearly input anything I like in those fields, so I'm confused as to how it's media derived, and I can update Original Audio File Name with an ALE in an existing project as expected.

 

 

Bruce Bullis
Community Manager
Community Manager
April 2, 2025

I require a way to modify the field from an ALE that has AudioFileName, the same way
> I can batch modify clips with an ALE that had ImageFileName. 

Do I understand correctly that your panel imports an .ALE, and updates the metadata of existing projectItems, with info from that .ALE?

If so, in the cases where the value of OriginalAudioFileName has changed, then your panel could use projectItem.changeMediaPath() to reflect that change, right?

Am I missing something?

Participating Frequently
April 2, 2025

Thanks, Bruce.

I don't think that solution is going to work unfortunately. I require a way to modify the field from an ALE that has AudioFileName, the same way I can batch modify clips with an ALE that had ImageFileName. 

Here's the tool I've developed: https://en.editingtools.io/plugins/ale-toolkit/ - happy to send you a copy if you'd like.

I was hoping there's a way for users to update their existing projects with ALE data, which they can, except this Original Audio File Name. 

Bruce Bullis
Community Manager
Community Manager
April 2, 2025

Given your metadata interest, you may wish to check out our UXP sample plugin, "Metadata Handler".


https://github.com/AdobeDocs/uxp-premiere-pro-samples/tree/main

For now, UXP support is only available in PPro beta builds, but UXP is the future. 🙂

 

Bruce Bullis
Community Manager
Community Manager
April 2, 2025

Though the file name shows up in metadata, that field is actually "data"; that file path is from the associated projectItem. 

Here's how to change the file path of a projectItem.