Skip to main content
S
Suhail36154911kr4q
Participating Frequently
June 15, 2025
解決済み

Premier Pro 25.3 `exportFramePNG` exports with an extra ".png" in filename

  • June 15, 2025
  • 返信数 1.
  • 350 ビュー

With the latest release (Premiere Pro 25.3.0),

`qe.project.getActiveSequence().exportFramePNG` exports frames with an extra .png in the filename, breaking any functionality where we are later looking for the expected filename with `fs.existsSync` but don't find it
 

 

"QE is not supported, recommended, documented": Yes but we don't have a way of getting a frame from the video through the main API, and UXP is not in GA yet.

 

This will break functionality for any plugins relying on analysing frames from the user's sequence so.... worth fixing IMHO 🙂

 

Also seeing this popup in Premiere in the bottom-right which we didn't used to see before but it doesn't break any functionality:

 

解決に役立った回答 bbb_999

And yes, we are aware of the double extension issue; it also impacts UXP extensibility. We plan to address it in UXP's official initial release.

返信数 1

bbb_999
Community Manager
bbb_999Community Manager
Community Manager
June 16, 2025

>we don't have a way of getting a frame from the video through the main API...

That's not true, and has not been for years. PProPanel shows how to output just one frame, without using QE DOM (and without a double extension).

https://github.com/Adobe-CEP/Samples/blob/9efca02ea88ad32a8c22571f5ffe2407ae732cd8/PProPanel/jsx/PPRO/Premiere.jsx#L128

bbb_999
Community Manager
bbb_999Community Manager解決！
Community Manager
June 16, 2025

And yes, we are aware of the double extension issue; it also impacts UXP extensibility. We plan to address it in UXP's official initial release.

契約条件Accessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices