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

Panel does not appear in extension list after changing CSXS version to 8

Explorer ,
May 07, 2018 May 07, 2018

Copy link to clipboard

Copied

Hello,

I'm trying to get a barebones test panel to work in the latest version of Premiere (12.1.1). Right now, it doesn't show up in the list of extensions if I set <RequiredRuntime Name="CSXS" Version="7.0" /> to 8.0 instead of 7.0 in the manifest. If I keep it at 7.0, it works fine. I definitely enabled unsigned extensions for CSXS 8.0, so that shouldn't be the problem. According to the CEP 8 Cookbook, Premiere 12 and up should be using CEP 8, so I'm really not sure what's going on.

I guess I can keep the version at 7 if that's what I need to do, but I'd like to take advantage of the newer Node and Chromium if I can (and I need to use the 12.1 API features, but I think those are unrelated to the CEP version, correct?).

I'm on a Mac running 10.11.5. There doesn't seem to be any modification to any of the log files when I open Premiere, so I don't have any error message to show from them. My manifest.xml is below along with my com.adobe.CSXS.8.plist just to be sure the flag is set correctly. Any help would be appreciated.

Thanks in advance,

David

CSXS/manifest.xml:

If I change the version on line 14 to "7.0," it works without a problem.

<?xml version="1.0" encoding="UTF-8"?>

<ExtensionManifest Version="7.0" ExtensionBundleId="com.dh.testpanel" ExtensionBundleVersion="1.0" ExtensionBundleName="Test Panel" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<ExtensionList>

<Extension Id="com.dh.testpanel" Version="1.0.0" />

</ExtensionList>

<ExecutionEnvironment>

<HostList>

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

</HostList>

<LocaleList>

<Locale Code="All" />

</LocaleList>

<RequiredRuntimeList>

<RequiredRuntime Name="CSXS" Version="8.0" />

</RequiredRuntimeList>

</ExecutionEnvironment>

<DispatchInfoList>

<Extension Id="com.dh.testpanel">

<DispatchInfo >

<Resources>

<MainPath>./index.html</MainPath>

<ScriptPath>./index.jsx</ScriptPath>

<CEFCommandLine>

<Parameter>--allow-file-access</Parameter>

<Parameter>--allow-file-access-from-files</Parameter>

<Parameter>--enable-nodejs</Parameter>

<Parameter>--mixed-context</Parameter>

</CEFCommandLine>

</Resources>

<Lifecycle>

<AutoVisible>true</AutoVisible>

</Lifecycle>

<UI>

<Type>Panel</Type>

<Menu>Test Panel</Menu>

<Geometry>

<Size>

<Height>300</Height>

<Width>180</Width>

</Size>

</Geometry>

</UI>

</DispatchInfo>

</Extension>

</DispatchInfoList>

</ExtensionManifest>

com.adobe.CSXS.8.plist:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>LogLevel</key>

<string>1</string>

<key>PlayerDebugMode</key>

<string>1</string>

</dict>

</plist>

TOPICS
SDK

Views

901

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

Adobe Employee , Aug 26, 2018 Aug 26, 2018

CEP is an Adobe-wide architecture for hosting extensions as web pages in our applications.

CEP has nothing to do with PPro's ExtendScript API (where QE DOM and projectItem.moveBin() live).

PProPanel exercises the ExtendScript API. Documentation is available here​.

QE DOM will remain unsupported, and undocumented.

Votes

Translate

Translate
New Here ,
Aug 25, 2018 Aug 25, 2018

Copy link to clipboard

Copied

I can't say why, but the above is what I experienced also.  It was frustrating for a day until I figured out this also.  I would have loved to come across your post earlier.  I came across other posts that indicate that Adobe CEP 8 cookbook may be out in Oct of 18 with improved (and more accurate examples and documentation) ie QE Dom and moveBin().  It's all about documentation accuracy. Hopefully, since most of Adobe is A+, this will follow suite.

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
Adobe Employee ,
Aug 26, 2018 Aug 26, 2018

Copy link to clipboard

Copied

LATEST

CEP is an Adobe-wide architecture for hosting extensions as web pages in our applications.

CEP has nothing to do with PPro's ExtendScript API (where QE DOM and projectItem.moveBin() live).

PProPanel exercises the ExtendScript API. Documentation is available here​.

QE DOM will remain unsupported, and undocumented.

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