• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

CEP Panel development, where to put CEP panel folders?

Engaged ,
May 08, 2020 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

TOPICS
How to , Scripting , SDK

Views

3.0K

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
community guidelines

correct answers 1 Correct answer

Engaged , May 10, 2020 May 10, 2020

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.

Votes

Translate

Translate
Community Expert ,
May 09, 2020 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...

Mathias Möhl - Developer of tools like BeatEdit and Automation Blocks for Premiere Pro and After Effects

Votes

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
community guidelines
Engaged ,
May 10, 2020 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.

Votes

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
community guidelines
Engaged ,
May 10, 2020 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.

Votes

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
community guidelines
Community Expert ,
May 10, 2020 May 10, 2020

Copy link to clipboard

Copied

LATEST

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" />
 
Mathias Möhl - Developer of tools like BeatEdit and Automation Blocks for Premiere Pro and After Effects

Votes

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
community guidelines