Premiere script exportAsMediaDirect() not working for Premiere Pro 2025

[Dev29789063rzh3]

Hello,

I have a plugin script to export the current active sequence in Premiere Pro using:
    app.project.activeSequence(outPath, presetPath, workArea)

It is no longer working for Premiere Pro 2025 and I'm not sure why, when running that API it returns "Unknown error" so I can't investigate any further.

That API still works with my Premiere Pro 2024. Some other scripting APIs also suffer from this issue in Premiere Pro 2025 where they simply don't work anymore and we had to come up with workarounds.

Are there any recent changes to the scripting APIs? I tried looking for such updates in the PPro 2025 change log but couldn't find anything.

I'm thinking of a workaround using the encoder but that would require changing a lot of the current plugin flow so I'd first want to know if anyone else has the same problem and whether there are any solutions/updates from Adobe.

Any help is very much appreciated.

[jane-e]

@Dev29789063rzh3 

I've moved your post from Coding Corner where it has not been answered for over a month to the Premiere Pro forum.

Jane

[Bruce Bullis · Accepted solution]

> app.project.activeSequence(outPath, presetPath, workArea) is no longer

> working for Premiere Pro 2025 and I'm not sure why...
> ...That API still works with my Premiere Pro 2024.

I feel safe in saying that code snippet has never exported the active sequence, in any version of PPro. 🙂

I've confirmed that PProPanel's example rendering code successfully renders, in current PPro shipping and beta releases, as does this snippet:

var seq = app.project.activeSequence;
if (seq){
	var result = 	seq.exportAsMediaDirect("/Users/bbb/Desktop/outName.mp4", 
											"/Users/bbb/Desktop/example.epr",
											app.encoder.ENCODE_ENTIRE);
	
}

[Dev29789063rzh3]

Hi,

Thank you for the reply. It was an error in what I typed.

The actual code to export the sequence is:

app.project.activeSequence.exportAsMediaDirect(sOutputPath, sPresetFilePath, iWorkAreaType)

and it has been working for several months now. It stopped working for about a week and now it's working again.