Builds:

For Adobe Suite 2020+ (Premiere 14.4 or later):

2.14.0 for Macintosh

2.14.0 for Windows

For Adobe Suite 2019 and Photoshop 2020 (Premiere 14.3 or earlier):

2.14.0 for Macintosh

2.14.0 for Windows

Reach Engine Support:
2.3.16 - 2.14.0

Adobe Host Support:
2019 - 2021
Premiere Pro
After Effects
Photoshop
Illustrator
InDesign

GENERAL AVAILABILITY

Through close collaboration with early adopters the Reach Engine Panels are better than ever and we are excited to announce the 2.14.0 release of Panel Extension officially promotes it out of Beta and into General Availability. The legacy Premiere Craft panel and Prelude Acquire panel are still supported at this time for critical bug fixes but will not be receiving further feature updates. Official End of Sale and End of Life date announcements will be defined in the future.

Top Reasons to use the overhauled Reach Engine Panel Extension

1. Support for more Adobe applications! With one installer you’ll be able to natively interact with Reach Engine in Adobe Premiere, AfterEffects, Photoshop, Illustrator, InDesign with more coming soon!
2. Significantly improved User Interface and User Experience
   a. Overhauled layout with a consistent experience with Reach Engine’s latest UI
   b. Powerful advanced search and Faceted search
   c. Overhauled status activity screen with far greater detail and context for end users
3. Hundreds of stability, performance and quality of life improvements compared to older panels
   a. More secure interaction with S3
   b. Less configuration for Administrators
   c. Significant improvements to asset import and project tracking performance and stability

2.14.0 Highlights

Automatically Restore Content

What’s New?

• When a panel user is interacting with Reach Engine assets that have Content that is archived the panel will automatically prompt the user to restore the content if desired.
  • Restore on Import
  • Restore on Check-Out

Why is it Valuable?

• Saves time and complexity for creatives by automating the restoration process through automated workflows
• Existing Restore workflows can be mapped to the panel configuration to immediately start importing archived content in one step
• Panel restore workflows can be customized for any specific custom behavior required

Execute Custom Workflows

What’s New?

• Primary workflow menu-bar shown in panel with workflows organized by their configured group
• Use the workflow menu tool bar to select and run Reach Engine workflows. From within the panel you can execute workflows on existing assets, workflows that runs against no assets and most importantly pass content from your Adobe Application to any Reach Engine Workflow File Input.
• All the progress of your custom workflow executions can be monitored in the Panel Status tab and of course in the Reach Engine UI

Why is it Valuable?

Significantly improved flexibility between creative users and the value of custom workflow. Now that Adobe media can be contributed directly to various workflows it becomes much easier to complete creative tasks across the content supply chain
Save time and stay in your creative tool by running workflows against existing assets and not switching context into another UI
For example, select a placeholder asset in Reach Engine and ingest a sequence straight to the placeholder via workflow and exporting via Media Encoder on the way. The Panel will automatically display all the required workflow form information and allow you to select your Project file or any Sequences as the input file. If a Sequence is selected a preset can then be selected for use by the Panel to automatically render and upload your sequence to Reach Engine and run the workflow.

S3 Transfer Acceleration Support

What's New?

In conjunction with our Reach Engine 2.14.0 and only supported on Reach Engine 2.14.0+ comes support for S3 Transfer Acceleration. With this functionality, creatives can save valuable time by accelerating user file uploads and user download especially over long distances. Please refer to the Reach Engine 2.14.0 Release Notes and User Guides for implementing S3 Transfer Acceleration. Once configured in Reach Engine the Panel will automatically utilize acceleration appropriately.

Release Details

Item Type	Title	Release Notes
Feature	Execute Custom Workflows in Panel	Use the workflow menu tool bar to select and run Reach Engine workflows. From within the panel you can execute workflows on existing assets, workflows that runs against no assets and most importantly pass content from your Adobe Application to any Reach Engine Workflow File Input. For example, select a placeholder asset in Reach Engine and ingest a sequence straight to the placeholder via workflow and exporting via Media Encoder on the way. The Panel will automatically display all the required workflow form information and allow you to select your Project file or any Sequences as the input file. If a Sequence is selected a preset can then be selected for use by the Panel to automatically render and upload your sequence to Reach Engine and run the workflow.  All the progress of your custom workflow executions can be monitored in the Panel Status tab and of course in the Reach Engine UI
Feature	Leverage S3 Acceleration in the Panel	When AWS S3 Transfer Acceleration is configured in Reach Engine (available 2.14.0+) the panel will utilize accelerated endpoints in any of its interactions for downloads and uploads.
Feature	Automatically Restore Content	The panel will now prompt a user to restore any content they've requested to import that is currently archived. When "Yes" is selected the panel will call the configured Reach Engine Workflow to restore the content. The Restore Workflow can be configured by setting local property one the Reach Engine Application server - workflows.restoreAsset.premiere=myRestoreAssetWorkflow
Feature	Miscellaneous UI Updates	Various adjustments were made to the Panel UI to improve clarity.  Status Page now reads "No Activity" when there is...no activity Login screen is simplified to display the Reach Engine logo or Client Logo as configured The "Settings" menu now reads "Preferences" to be in line with the presented "Preferences" modal View Settings has been renamed to "Configure View"
Feature	Make Proxy Mapping Optional	It is now possible to use the same content for in the Panel Preferences for users that don't with to pass a different file to premiere's proxy reference.
Feature	Do not include Offline Media in Unmanaged Assets List	Any Offline Media in a project will not be included in the Unmanaged Assets ingest as the data will never be available to ingest and correlate with a Reach Engine asset.
Resolved Bug	Workflow Right Curtain does not show in single asset and Collection view	Resolved an Issue where the workflow Right Side Bar was not being presented in Collection or Single Asset Views.
Resolved Bug	Proxy / Proxy Imports Requiring User to Restore Source / Mezz	Resolved an issue where proxy only workflow were prompting for the restore of the source / mezzanine content even though the proxy was online.
Resolved Bug	Manual Downloads set incorrect file extension	Resolved an issue where manual downloads were always using the source content's file extension instead of the content type that was selected.
Resolved Bug	Pagination isn't resetting when a new search is performed	Resolved an issue where new searches weren't resetting the page number on the paginator to page 1 but were accurately showing the first page of results.
Resolved Bug	Unresponsive Facets	Resolved an issue where facet selections, advanced search criteria and search resets were causing lockups, unresponsive results or incorrect results.
Resolved Bug	"Update Adobe Source File Path" fails when importing an asset.	Root Cause not resolved due to a Premiere SDK bug. However, additional debugging has been implemented to reduce troubleshooting overhead. There is an active bug with Adobe where Premiere provides the wrong references to the current project, so the Panel can not match the imported file with something in the active project.
Resolved Bug	Reveal in Finder action does not path map	Resolved an issue where the "Reveal in Finder" action would not properly path map content locations.