Skip to main content
Participant
November 18, 2025
Answered

How to Retrieve Sequence IDs from an Unopened .prproj File in CEP Panel ?

  • November 18, 2025
  • 1 reply
  • 107 views

Hi everyone,

I’m developing a CEP extension for Premiere Pro 2022. The workflow of the extension is roughly as follows:

  1. I prepare several .prproj files (each containing sequences with certain effects) and store them in a presets directory.

  2. My CEP panel allows users to freely import any of these preset .prproj files, and the extension will insert the chosen sequence into the current project as an adjustment-layer.

  3. I’m using the importSequences() API.

According to the Adobe sample:
https://github.com/Adobe-CEP/Samples/blob/ef77e70b0fb813c8db5b32159b98ed7fdd15c541/PProPanel/jsx/PPRO/Premiere.jsx#L287

importSequences() requires:

  • the path to the .prproj file

  • an array of sequence IDs to import

The issue is that I cannot find any way—via API documentation or previous forum discussions—to enumerate the sequences inside a .prproj file that is not currently opened, nor to obtain their sequence IDs.

Official API reference:
https://ppro-scripting.docsforadobe.dev/


My question:

Is there any API or workaround that allows ExtendScript or CEP to:

  • read the contents of an unopened .prproj file?

  • list the sequences inside it?

  • retrieve their sequence IDs?

From what I’ve seen, Premiere’s ExtendScript API only exposes the contents of the currently opened project, not external .prproj files. Before concluding that this is impossible, I wanted to ask whether anyone knows of any method—official or unofficial (XML parsing, indirect techniques, version quirks, etc.)—to retrieve sequence IDs from unopened project files.


Any insights or suggestions would be greatly appreciated.
Happy to provide additional details if necessary.

Correct answer bbb_999

>I’m developing a CEP extension for Premiere Pro 2022.

Why would you develop an extension specifically for a version of PPro, that is no longer supported? 

As you've discovered, the Premiere Pro ExtendScript API only acts on open projects. Since you're the one providing the template projects, you can already know the sequence IDs of the sequences in those projects, before you ever ship. 

 

There is no supported method for gathering such information directly from a .prproj file, nor do we have any plans to offer such functionality. 

1 reply

bbb_999
Community Manager
bbb_999Community ManagerCorrect answer
Community Manager
November 18, 2025

>I’m developing a CEP extension for Premiere Pro 2022.

Why would you develop an extension specifically for a version of PPro, that is no longer supported? 

As you've discovered, the Premiere Pro ExtendScript API only acts on open projects. Since you're the one providing the template projects, you can already know the sequence IDs of the sequences in those projects, before you ever ship. 

 

There is no supported method for gathering such information directly from a .prproj file, nor do we have any plans to offer such functionality. 

Participant
November 19, 2025

>  Why would you develop an extension specifically for a version of PPro, that is no longer supported? 

There’s one point I’d like to clarify, and I want to apologize for causing the misunderstanding.
In my original post, I mentioned Premiere Pro 2022, but what I meant was that I’m targeting 2022 as the minimum supported version, with compatibility moving forward. My wording wasn’t clear, which led to the confusion — sorry about that.

 

Your explanation about the API limitations makes perfect sense. I’ll follow your suggestion and pre-store the sequence IDs from the template projects.

Really appreciate your help and your time!