Highlighted

Requesting Feedback from 3rd Party Extension and Plugin Developers

Adobe Employee ,
Aug 07, 2020

Copy link to clipboard

Copied

If you build extensions or plugins for Premiere Pro or After Effects, please be sure to try out the latest beta build, as the CEP team is looking for feedback on CEP 10. Please comment on it in this thread so feedback can be given back to the CEP team.

Here are the release notes regarding this update:

CEP 10 includes a major update to CEF(Chromium Embedded Framework) from v61 to v74. More details are available at

https://medium.com/adobetech/summer-cep-update-cep-10-is-coming-in-august-bcc30d22c38f

 

Of note for CEP 10

  1. Issues seen on NWJS version 0.38 will also be applicable in CEP 10

For example: There are errors noticed when node module "winston" is used with any other node module which uses duplex. Workaround: In case you are using the node module "winston" please add this below script to the extension.

var {Duplex} = require('stream')

var {Writable} = require('stream')

{

  // Allow the keys array to be GC'ed.

  const keys = Object.keys(Writable.prototype);

  for (var v = 0; v < keys.length; v++)

  {    

               const method = keys[v];    

               if (!Duplex.prototype[method])      

               Duplex.prototype[method] = Writable.prototype[method];  

  }

}

 

2. Update your node modules

CEP 10 works with NodeJS 12.3.1 and Node-WebKit 0.38 versions. If extensions were built on older version of NodeJS there can be cases where these extensions may not load in CEP 10 due to incompatible node modules. In such cases, the node modules need to be updated using NodeJS version 12.3.1 or higher.

3. Issues in CSS properties due to deprecation in Chromium will be applicable in CEP 10

In such cases, extension developers will need to update the CSS for the extension, in order for the extension to render correctly in CEP 10. For eg: https://bugs.chromium.org/p/chromium/issues/detail?id=927066


4. Unsigned Extensions

If you are in the midst of development and are not using HTML Extension Builder for debug workflows and want to bypass the need to sign your extensions, you can bypass the check for extension signatures by editing the CSXS preference properties file, located at:

  • Win: regedit > HKEY_CURRENT_USER/Software/Adobe/CSXS.10, then add a new entry PlayerDebugMode of type "string" with the value of "1".
  • Mac: In the terminal, type: defaults write com.adobe.CSXS.10 PlayerDebugMode 1 (The plist is also located at /Users/<username>/Library/Preferences/com.adobe.CSXS.10.plist)

 

Topics

Feedback

Views

24

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Requesting Feedback from 3rd Party Extension and Plugin Developers

Adobe Employee ,
Aug 07, 2020

Copy link to clipboard

Copied

If you build extensions or plugins for Premiere Pro or After Effects, please be sure to try out the latest beta build, as the CEP team is looking for feedback on CEP 10. Please comment on it in this thread so feedback can be given back to the CEP team.

Here are the release notes regarding this update:

CEP 10 includes a major update to CEF(Chromium Embedded Framework) from v61 to v74. More details are available at

https://medium.com/adobetech/summer-cep-update-cep-10-is-coming-in-august-bcc30d22c38f

 

Of note for CEP 10

  1. Issues seen on NWJS version 0.38 will also be applicable in CEP 10

For example: There are errors noticed when node module "winston" is used with any other node module which uses duplex. Workaround: In case you are using the node module "winston" please add this below script to the extension.

var {Duplex} = require('stream')

var {Writable} = require('stream')

{

  // Allow the keys array to be GC'ed.

  const keys = Object.keys(Writable.prototype);

  for (var v = 0; v < keys.length; v++)

  {    

               const method = keys[v];    

               if (!Duplex.prototype[method])      

               Duplex.prototype[method] = Writable.prototype[method];  

  }

}

 

2. Update your node modules

CEP 10 works with NodeJS 12.3.1 and Node-WebKit 0.38 versions. If extensions were built on older version of NodeJS there can be cases where these extensions may not load in CEP 10 due to incompatible node modules. In such cases, the node modules need to be updated using NodeJS version 12.3.1 or higher.

3. Issues in CSS properties due to deprecation in Chromium will be applicable in CEP 10

In such cases, extension developers will need to update the CSS for the extension, in order for the extension to render correctly in CEP 10. For eg: https://bugs.chromium.org/p/chromium/issues/detail?id=927066


4. Unsigned Extensions

If you are in the midst of development and are not using HTML Extension Builder for debug workflows and want to bypass the need to sign your extensions, you can bypass the check for extension signatures by editing the CSXS preference properties file, located at:

  • Win: regedit > HKEY_CURRENT_USER/Software/Adobe/CSXS.10, then add a new entry PlayerDebugMode of type "string" with the value of "1".
  • Mac: In the terminal, type: defaults write com.adobe.CSXS.10 PlayerDebugMode 1 (The plist is also located at /Users/<username>/Library/Preferences/com.adobe.CSXS.10.plist)

 

Topics

Feedback

Views

25

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Have something to add?

Join the conversation