Skip to main content
Premiopolis
Premiopolis
Inspiring
May 22, 2018
Answered

ExtendScript and Metadata -- accessing any and all metadata

  • May 22, 2018
  • 1 reply
  • 4384 views

Haven't found a way access many of the metadata entries offered offered up under PPro's Metadata" panel and the "Metadata Display..." popup

e.g. from "Dublin Core": "Keywords", "Title", "Type" or those under "Rights Management", "Media Management" etc.

Can ExtendScript 'get' and 'set' any and all metadata properties or are there limits?

This topic has been closed for replies.
Correct answer Bruce Bullis

PProPanel demonstrates getting and setting XMP metadata, both the media-specific XMP metadata, and PPro's own private project metadata.

General XMP:  Samples/Premiere.jsx at master · Adobe-CEP/Samples · GitHub

Private project metadata: Samples/Premiere.jsx at master · Adobe-CEP/Samples · GitHub

1 reply

Bruce Bullis
Community Manager
Bruce BullisCommunity ManagerCorrect answer
Community Manager
May 22, 2018

PProPanel demonstrates getting and setting XMP metadata, both the media-specific XMP metadata, and PPro's own private project metadata.

General XMP:  Samples/Premiere.jsx at master · Adobe-CEP/Samples · GitHub

Private project metadata: Samples/Premiere.jsx at master · Adobe-CEP/Samples · GitHub

Premiopolis
PremiopolisAuthor
Inspiring
May 22, 2018

Yes, familiar with that.  Where I was having trouble was targeting specific fields of a projectItem.

So, referencing an old post How to use ExtendScript to edit metadata on project items?​, if you're trying to get/set Comments for a projectItem, the namespace for that is Column.PropertyText.Comment.

For MediaStart the namespace is Column.Intrinsic.MediaStart

There's even access to Hide & Good Column.PropertyBool.Hide and Column.PropertyBool.Good

Those namespaces don't relate to the metadata categories under which the above properties fall in Metadata Panel and Metadata display... popup

Comment, MediaStart, Hide, and Good are found under the "Premiere Pro Project Metadata" section of the Metadata display... popup

There is another, unrelated Comment and a Good under "Dynamic Media"

So what I was getting at was accessing any and all properties, across the variety of metadata categories.

The mungeXMP function at Samples/Premiere.jsx at master · Adobe-CEP/Samples · GitHub  didn't seem to reveal how that might work.

guntramp26642460
guntramp26642460
Inspiring
January 29, 2024

Bruce Bullis​

Following up on this.

As far as I can tell it's only possible to able to programmatically read and (when it makes sense) write Metadata entries for a limited number of categories (26, to be exact. See attached list below)

All valuable but hardly exhaustive.

There are many more (13 under "Dublin Core", another 10 under "Basic", more than 50 under "Premiere Project Metadata")

Why this matters: I've got a real-world case: clients asking if we can code up abilities to control Metadata not included in the 26 listed in the table below, including customized categories.

Trying to get them a "yes" answer asap.  Any ideas?

NameColumn.Intrinsic.Name
TapeNameColumn.Intrinsic.TapeName
DescriptionColumn.PropertyText.Description
CommentColumn.PropertyText.Comment
LabelColumn.PropertyText.Label
MediaTypeColumn.Intrinsic.MediaType
MediaTimebaseColumn.Intrinsic.MediaTimebase
MediaStartColumn.Intrinsic.MediaStart
MediaEndColumn.Intrinsic.MediaEnd
MediaDurationColumn.Intrinsic.MediaDuration
MarkInColumn.Intrinsic.VideoInPoint
MarkOutColumn.Intrinsic.VideoOutPoint
TimeDisplaytime_display
VideoInfoColumn.Intrinsic.VideoInfo
AudioInfoColumn.Intrinsic.AudioInfo
VideoUsageColumn.Intrinsic.VideoUsage
AudioUsageColumn.Intrinsic.AudioUsage
FilePathColumn.Intrinsic.FilePath
StatusColumn.PropertyText.Status
GoodColumn.PropertyBool.Good
HideColumn.PropertyBool.Hide
PropogateHideColumn.PropertyBool.PropagatedHide
SoundTimeCodeColumn.Intrinsic.SoundTimeCode
SyncOffsetColumn.PropertyText.SyncOffset
CodecColumn.PropertyText.Codec
FieldOrderColumn.PropertyText.FieldOrder

If you want to access "MasterComment3" for example, you can see inside the metadata, that its identifier looks like "Master_Comment_3" without that other stuff "Column.Intrinsic.Something".

So if you do not find your metadata field, look into the data you get from projectItem.getProjectMetadata():

<?xpacket begin="" id="W5M0MpCehiHzreSzNTczkc9d"?>
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 7.1-c000 79.b0f8be9, 2021/12/08-19:11:22        ">
   <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
      <rdf:Description rdf:about=""
            xmlns:premierePrivateProjectMetaData="http://ns.adobe.com/premierePrivateProjectMetaData/1.0/">
         <premierePrivateProjectMetaData:Column.Intrinsic.Name>USA/ARIZONA: NB - HOBBYFILMER NIMMT SELTENEN JAGUAR MIT KAMERA AUF</premierePrivateProjectMetaData:Column.Intrinsic.Name>
         <premierePrivateProjectMetaData:Column.PropertyText.Label>BE.Prefs.LabelColors.1</premierePrivateProjectMetaData:Column.PropertyText.Label>
   
[...]
 
 <premierePrivateProjectMetaData:Column.PropertyText.FieldOrder>Upper Field First</premierePrivateProjectMetaData:Column.PropertyText.FieldOrder>
         <premierePrivateProjectMetaData:Column.PropertyText.Proxy>Attached</premierePrivateProjectMetaData:Column.PropertyText.Proxy>
         <premierePrivateProjectMetaData:Master_Comment_3>SOME VALUE</premierePrivateProjectMetaData:Master_Comment_3>
      </rdf:Description>
   </rdf:RDF>
</x:xmpmeta>            
<?xpacket end="w"?>
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices