Skip to main content
B
Birdofscript
Participant
March 19, 2025
Answered

Metadata missing in exported media

  • March 19, 2025
  • 2 replies
  • 383 views

Hi there,

When I export a sequence using a CEP panel with the command:

app.project.sequences[index].exportAsMediaDirect(outputPath, presetPath, workAreaType)

the output file does not contain the metadata corresponding to the project path (among other details).

https://ppro-scripting.docsforadobe.dev/sequence/sequence/?h=exportasmediadirect#sequenceexportasmediadirect

 

However, when exporting using the same preset (.epr) via Premiere's built-in export tool, this metadata does appear.

 

I have attached a screenshot comparing the metadata outputs:

  • On the left, the export was done via script.
  • On the right, it was done using Premiere's built-in export tool.

As seen on line 97, the project path appears in the Premiere export but is missing in the script-based export.

 

 

What could be causing this? Any idea?

I've attached a screenshot containing all the generated metadata.

Thanks in advance!

Joan

    Correct answer Bruce Bullis

    >...I've noticed that the metadata is also missing when exporting (via code).

    Cool, feature parity between ExtendScript and UXP! 🙂

    > When exporting via code, is it possible to ensure that metadata—especially the project path—is included in the exported file?

    Your testing suggests otherwise...

    >    How can this be achieved?

    >Is there a way to insert custom metadata via code?

    Yes!

    Here's how PProPanel adds custom metadata to a project item (which includes sequences). Since your panel is driving the export, you already know the project in which the sequence resides. MAM vendors save this info in the newly-created asset's genealogy.

     

     



    2 replies

    Bruce Bullis
    Community Manager
    Bruce BullisCommunity Manager
    Community Manager
    July 18, 2025

    Scripted export follows a different code path than export via the UI, which would account for the differences. 

    Are you using MediaInfo for that metadata comparison? 

    Since you're programatically driving the export, your panel knows what project (and sequence) the media is coming from, so hopefully you can use/maintain that information without relying on the only-generated-via-UI information.


    B
    BirdofscriptAuthor
    Participant
    July 22, 2025

    Thank you, Bruce, for your response! 🙂

     

    I used ExifTool to extract the metadata, generated two text files, and then compared them in Visual Studio Code.

     

    I'm currently migrating the code to UXP, and I've noticed that the metadata is also missing when exporting (via code).

     

    My questions are:
    When exporting via code, is it possible to ensure that metadata—especially the project path—is included in the exported file? How can this be achieved?

    Is there a way to insert custom metadata via code?

     

    Having the project path embedded in the exported file’s metadata is extremely helpful for tracing the origin of past projects.

    Bruce Bullis
    Community Manager
    Bruce BullisCommunity ManagerCorrect answer
    Community Manager
    July 23, 2025

    >...I've noticed that the metadata is also missing when exporting (via code).

    Cool, feature parity between ExtendScript and UXP! 🙂

    > When exporting via code, is it possible to ensure that metadata—especially the project path—is included in the exported file?

    Your testing suggests otherwise...

    >    How can this be achieved?

    >Is there a way to insert custom metadata via code?

    Yes!

    Here's how PProPanel adds custom metadata to a project item (which includes sequences). Since your panel is driving the export, you already know the project in which the sequence resides. MAM vendors save this info in the newly-created asset's genealogy.

     

     



    Kevin-Monahan
    Community Manager
    Kevin-MonahanCommunity Manager
    Community Manager
    July 18, 2025

    Hi,

    Thanks for your post. I added the SDK tag to your post. This will bring the right dev or Adobe Expert to your post. I hope we can help you shortly. Sorry for the frustration.

     

    Cheers,
    Kevin

     

    Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
    B
    BirdofscriptAuthor
    Participant
    July 22, 2025

    Thankyou Kevin 🙂

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices