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

Question

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 &#128578;
 
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 · Accepted Answer

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.

bbb_999 · Answer

>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

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.