Follow steps outlined in this README.md
.
Clone the project with git
:
git clone https://github.com/cb-rnag/PPro-Extension-Zoom-Chat-To-Markers.git
cd into the project directory:
cd PPro-Extension-Zoom-Chat-To-Markers
Create a symlink using the ZoomChatToMarkers/
folder to the directory where Adobe Premiere searches for extensions:
sudo ln -s "${PWD}/ZoomChatToMarkers" "/Library/Application Support/Adobe/CEP/extensions/ZoomChatToMarkers"
Open a sample project in Adobe Premiere Pro.
Select the extension in the top menu bar, Window > Extensions > Zoom Chat to Markers
. You should see a window pane pop up.
Open the project in an IDE.
Make a change to the UI in ZoomChatToMarkers/index.html
, and hit “Refresh Panel” in the extension popup window.
You should see new UI changes reflected in Premiere.
You are now set for development!
Certificate Password is saved in SSM Parameter in our apdaily-prod
AWS account.
It is saved under /adobe/extension/zoom-chat-to-markers/cert-password
.
Copy the password and save it to a .password
file.
If publishing a new version, update the version number in the CSXS/manifest.xml
file.
Run the build.sh
script to package the plugin directory into a ZoomChatToMarkers.zxp
file.
Create a new version for the plugin, and upload the .zxp
file here.
These samples demonstrate techniques for building an extension with an HTML5 UI and behavior implemented in JavaScript.
The samples are kept up to date with the latest CC2018 host applications. Make sue to check the manifest.xml
file for each sample's compatible host applications. To run the extensions you must have the compatible host application installed. Requirements for each sample are listed below.
Each version of CEP comes with its own samples in the CEP-Resources repository. Under each version name, CEP_N.x
, you will find the version specific samples, which cover broad use cases and topics of CEP.
Unlike the samples in the CEP-Resources repository, samples in this repository cover specific use cases covering a wide variety of topics. Check out the next section to choose a sample that suits your need.
- The provided samples are unsigned. This will cause the signature check (built into CEP when first running an extension) to fail. To bypass the signature check, please refer to the documentation.
- Although these extensions are initially setup for a particular version of CEP, you can adjust the product version targeted by modifying the range inside the
HostList
element of theCSXS/manifest.xml
file. - Some folders have a nested folder strucutre. For those samples, you will need to extract sub-directories into the extension folder.
Extension | Description | Supported Products |
---|---|---|
Premiere Pro Panel | Demonstrates a Premiere Pro panel. | Premiere Pro |
TypeScript | Demonstrates multiple sample codes thata demonstrate what's possible to build inside Premiere Pro. | Premiere Pro |