Hi! I'm having trouble sorting out a function in my Premiere CEP panel that used to seem to work, but is no longer behaving the way I expect it to. My goal is to create a custom metadata field if that field doesn't already exist in the Premiere project's metadata schema, and return whether or not that operation was successful. It works sometimes, and doesn't work depending on what Premiere project is active, even though the metadata field seems to be successfully created in either one. Here's my function, which is based on the PPro sample panel:
createCustomMetadata: function (name, label, type) {
var kPProPrivateProjectMetadataURI = "http://ns.adobe.com/premierePrivateProjectMetaData/1.0/";
var customMetadataSuccess = false;
if (app.isDocumentOpen()) {
var projectItem = app.project.rootItem.children[0];
if (projectItem) {
if (ExternalObject.AdobeXMPScript === undefined)
ExternalObject.AdobeXMPScript = new ExternalObject('lib:AdobeXMPScript');
if (ExternalObject.AdobeXMPScript !== undefined) {
var projectMetadata = projectItem.getProjectMetadata();
var xmp = new XMPMeta(projectMetadata);
//check if custom metadata field already exists in this project.
var propertyExists = xmp.doesPropertyExist(kPProPrivateProjectMetadataURI, label);
if (!propertyExists){ // if the custom field doesn't already exist, add it now.
var successfullyAdded = app.project.addPropertyToProjectMetadataSchema(name, label, type);
alert('successfully added: ' + successfullyAdded);
var newProjectMetadata = projectItem.getProjectMetadata();
var newXMP = new XMPMeta(newProjectMetadata);
propertyExists = newXMP.doesPropertyExist(kPProPrivateProjectMetadataURI, label);
}
if (propertyExists) //should be true at this point unless successfullyAdded is false
customMetadataSuccess = true;
}
}
}
return customMetadataSuccess;
}
And I call it elsewhere like this:
var success = $.runScript.createCustomMetadata("TranscodeOriginalPath", "TranscodeOriginalPath", 2);
if (!success) // if metadata field still doesn't exist, immediately stop.
alert("Could not initialize replace function.")
I'm running four tests to compare what happens.
In Test 1, I'm using a project I did this with a few months ago (so it already has the TranscodeOriginalPath metadata field created). When createCustomMetadata() runs, it doesn't print anything because it never enters the if (propertyExists){...} block. It's called in my second code snippet with no issues.
In Test 2, I'm using the same project as Test 1 but I manually deleted the TranscodeOriginalPath metadata field from within the Premiere project. When createCustomMetadata() runs, it prints "successfully added: true" and also returns true in my second code snippet.
However, in Test 3 I'm using another project (I've tried multiple projects, including one with a similar bin structure to the project from the first two tests as well as new projects with nothing but one sequence and one video clip).When createCustomMetadata() runs, it prints "successfully added: true" but then returns false in my second code snippet and prints "Could not initialize renaming function." However, the TranscodeOriginalPath field is created (which I confirm by looking at the project's Metadata Display).
In Test 4, I'm using the same project as Test 3 without making any changes. When createCustomMetadata() runs, it prints "successfully added: undefined" (which I assume is because the field already exists), returns false in my second code snippet and prints "Could not initialize renaming function."
What gives? Why is it that I can confirm the custom metadata field is successfully created in every test, but my calls to doesPropertyExist() return different values depending on the project? I tried writing the new XMP to a file and reading through it, and indeed the TranscodeOriginalPath field only shows up in the first two tests. Why is that the case when my call to addPropertyToMetadataSchema() works as expected every time (or even when I manually add TranscodeOriginalPath to my project through the Metadata Display in Premiere)? It seems like something is preventing my panel from properly reading the XMP data, but only under certain circumstances that I don't understand.
I'm also wondering if it's just not worth using doesPropertyExist() to be safe and check for the new custom field, even if that's the way the PPro sample panel does it. Is it enough to check
if (propertyExists || successfullyAdded)
customMetadataSuccess = true;
instead of
if (propertyExists)
customMetadataSuccess = true;
near the end of my first code snippet, and assume that calls to addPropertyToMetadataSchema() will never fail? That seems to be a more reliable indicator that the field was created than doesPropertyExist(), at least, unless there's something I'm missing.
Any help is really appreciated, thanks!
1 Correct answer
6
Replies
AdChoices