Handling Inconsistent NodeIDs in Adobe Team Projects Across Different Users

[dt3792439]

Hi - 

I've developed an Adobe Extension that uses NodeIDs to:

1. Identify media within a project (e.g., video-xyz.mp4 is identified as 000f4241).
2. Identify the project itself (e.g., Test.pproj is identified as a9b11661-ac5b-4817-842d-e60257dd84ed).

This method works well when I'm a single user working on an individual project. However, I've recently started to implement this in a Team Project environment and encountered issues. It seems that Adobe Premiere Pro assigns different NodeIDs to the same project and media when accessed from different computers. For example:

• User 1:

  • Project: TestTeamProject is a9b11661-ac5b-4817-842d-e60257dd84ed
  • Media: video-xyz.mp4 is 000f4241

• User 2:

  • Project: TestTeamProject is 036cd539-acf1-49d8-9eab-726a19c9384c
  • Media: video-xyz.mp4 is 000f4244

This discrepancy breaks my script because the NodeID stored by one user does not match what another user sees. However, Premiere Pro itself recognizes these as the same project and media items. Is there a different identifier within Premiere’s ecosystem, accessible from CEP, that remains consistent across different instances/users in a Team Project setting? How can I handle this to ensure consistent identification across multiple users?

Thank you for your insights!

[R Neil Haugen]

@Udo Pawlik might be able to help ... 

[dt3792439]

Thanks @R Neil Haugen!. And yes @Udo Pawlik  - any direction here would be most appreciated.

[Udo_Pawlik]

Sorry, Node IDs are not stable in Team Projects and the proper AssetIdentifier is currently not accessible from CEP. 

[dt3792439]

Copy that. Is there a recommended strategy (e.g. using a hash of metadata). And I assume this is Media Node ID that we’re talking about. 

What about a project unique identifier that connects a local project ID to that of a global project ID. I’ve seen both cloudLocalID, which I assume represents a projectNodeID locally, and the concept of a Guid (unique identifier of a project) listed in Project Properties, but not sure if these uniquely identify the project globally, if that makes sense.

Then finally - does any of this change with UXP?