Highlighted

CEP Panel development, where to put CEP panel folders?

Engaged ,
May 08, 2020

Copy link to clipboard

Copied

I've downloaded a CEP panel sample from Adobe's repo  and according to the docs here I've put the sample AfterEffectsPanel folder in

C:\Program Files\Common Files\Adobe\CEP\extensions

and I tried in:

%Appdata%\Roaming\Adobe\CEP\extensions

But it's not showing up in the list of extensions in AE. Is there something I'm doing wrong?

C__Program Files_Common Files_Adobe_CEP_extensions-2020-05-09 16_51_55.png

I found the problem. The sample files that Adobe has on their github are all really old, because Adobe. So the max version number in the manifest.xml files were set to 15.9 or something. I changed it to 99.9 and the sample extensions are now visible.

Topics

How to, Scripting, SDK

Views

1.2K

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

CEP Panel development, where to put CEP panel folders?

Engaged ,
May 08, 2020

Copy link to clipboard

Copied

I've downloaded a CEP panel sample from Adobe's repo  and according to the docs here I've put the sample AfterEffectsPanel folder in

C:\Program Files\Common Files\Adobe\CEP\extensions

and I tried in:

%Appdata%\Roaming\Adobe\CEP\extensions

But it's not showing up in the list of extensions in AE. Is there something I'm doing wrong?

C__Program Files_Common Files_Adobe_CEP_extensions-2020-05-09 16_51_55.png

I found the problem. The sample files that Adobe has on their github are all really old, because Adobe. So the max version number in the manifest.xml files were set to 15.9 or something. I changed it to 99.9 and the sample extensions are now visible.

Topics

How to, Scripting, SDK

Views

1.2K

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
Adobe Community Professional ,
May 09, 2020

Copy link to clipboard

Copied

Did you enable debug mode? Without debug mode only signed extensions will show up.

https://github.com/Adobe-CEP/Getting-Started-guides/tree/master/Client-side%20Debugging#set-the-debu...

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
Reply
Loading...
Engaged ,
May 10, 2020

Copy link to clipboard

Copied

Dang, I was hoping that would do it, but by the looks of it debug mode is already on.

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
Reply
Loading...
Engaged ,
May 10, 2020

Copy link to clipboard

Copied

I found the problem. The sample files that Adobe has on their github are all really old, because Adobe. So the max version number in the manifest.xml files were set to 15.9 or something. I changed it to 99.9 and the sample extensions are now visible.

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
Reply
Loading...
Adobe Community Professional ,
May 10, 2020

Copy link to clipboard

Copied

Good that you found the issue!

Note that you can also just specify a single version number. When you do that the extension will be working for any version >= that number. So this should work on Premiere Pro 9.1 and any newer version, for example:

<Host Name="PPRO" Version="9.1" />
 

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
Reply
Loading...