Skip to main content
Participating Frequently
November 23, 2021
Answered

Missing the Object app.encoder [14.3.1, 15.0, 15.1, 15.2]

  • November 23, 2021
  • 2 replies
  • 3248 views

Hello,

i wrote a Adobe Premiere extension and i have a big problem.

 

This object from ExtendScript "app.encoder" is null.
I have the Problem in the Following Version: 14.3.1, 15.0, 15.1 and 15.2.
At 15.4 and above the object ist fine and works.

What could be the problem?
Unfortunately, the customers who use the plug-in cannot simply update the Premiere version.

 

Is this a Premiere problem or am I doing something wrong?


My Setup: 
MacOS Monterey
Adobe CEP 9
Premiere Pro 14.3.1 to 15.2

 

This topic has been closed for replies.
Correct answer Dmitriy5FD0

I have same problem on 22.2.0 (Build 128) Windows

app.encoder is undefined, is there any way to fix that?


fixed by reinstalling Adobe CC

2 replies

Participating Frequently
December 2, 2021

I try it with the latest 15.4.2 version and i have the same problem. 

This Screenshot is from MacMini (end 2014) with macOS Montery 12.0.1

Premiere and Media Encoder are up and running.

Do I see it right that the object "Global => app.encoder" should never be null?

 

Participating Frequently
December 2, 2021

I have the problem now also with 14.3.1
The app.encoder object is simply null.

I would almost guess that it has to do with the latest macOS 12.0.1 version.

Participating Frequently
December 2, 2021

I test it also on a MacBook Pro mid 2014 with macOS 11.6 (Big Sur) and Premiere Pro 15.4.1

on this configuration is the encoder object avalible. 

Bruce Bullis
Community Manager
Community Manager
November 23, 2021

Bizarre; you're the first to report that. 

Is Media Encoder also installed on those systems?

Also, on line 10, you're using QE DOM; why? You can get the in and out points of sequences from the public DOM, as well...

 

 

 

 

Participating Frequently
December 1, 2021

Yes the same Media Encoder version ist installed.

 

Bruce Bullis
Community Manager
Community Manager
December 1, 2021

We have no idea what could be causing that behavior, on the customer's systems.

 

As mentioned, no one else has reported the issue, and your own testing shows it's been fixed for many releases...

I think the best path forward is to address whatever issues they feel prevent them from using a current version of PPro.