IMPORTANT: If using Remote Adobe Media Encoder (RAME), OnePanel 2.17.3 REQUIRES RAME 2.16.2 or greater.

Release date:
December 21st, 2022

Builds:

OnePanel:

2.17.3 for Macintosh
2.17.3 for Windows

OnePanel Desktop:

2.17.3 for Macintosh
2.17.3 for Windows

RAME:

2.17.3 for Macintosh
2.17.3 for Windows

Reach Engine Support:
2.3.16 - 2.17.1

Adobe Application Support:
2019 - 2022
Premiere Pro
Prelude
After Effects
Photoshop
Illustrator
InDesign

Highlights

OnePanel and OnePanel Desktop:

Adobe 2022 Metadata Plugin:

• We built the latest C++ Metadata Plugin, which is meant to transfer reach-engine-user-metadata between ReachEngine and PremierePro's internal panels (Project Panel, Metadata Panel and so on). This new built includes all new Adobe item types, so no more issues related to the project file are expected from Adobe side.
• New Adobe's security updates are included in the latest built.

Configuration File:

• Now you can have a config file to save your preferences as Reach Engine URL, Local Repository Path, Source and Proxy settings. You can start by modifying the example file located in the Reach Engine Directory, near to OnePanel location.
• All OnePanel, OnePanelDesktop and RAME use the same json config file. Each one will own a section into the json file, with 100% compatibility of structure.

What uses has this config file in OnePanel?

• Instead of configure yours settings in each Adobe app (and re repeating that every time you install a new version of Adobe), you can save and sync all yours settings between all Adobe Apps: PremierePro, AfterEffect, Photoshop and more in only one place.
• You can make a mass deploy of the Panel to several user workstations and saving a lot of effort by configuring the Panel just one time.

The "source of truth" problem:

RAME doesn't have a UI, that is why the config file is the only "source of truth" when it comes to settings. No problems with RAME.
The previous is not true for OnePanel and OnePanelDesktop. You can configure reachEngine, local repository path, secondary local repository path, source and proxy settings in the UI with the configuration modal, which will store those between sessions.
Then we can see how OnePanel and OnePanelDesktop have two "sources of truth": The UI and the config file. So, when a field exists in both, what are we going to use?

• when "force" or "forceAll" is true, we use the config file.
• in other case, we use the value indicated in the UI.

Example:

{
  "onePanel": {
    "forceAll": false,
    "reachEngine": {
      "force": false,
      "url": "https://my-server.com/"
    },
    "repositories": {
      "force": false,
      "localRepositoryPath": "/my/local/repository/path",
      "secondaryLocalRepositoryPath": "/my/other/local/repository/path/"
    },
    "contentUses": {
      "force": false,
      "source": "source",
      "proxy": "proxy"
    }
  },
  "onePanelDesktop": {
    "forceAll": false,
    "reachEngine": {
      "force": false,
      "url": "https://my-server.com/"
    },
    "repositories": {
      "force": false,
      "localRepositoryPath": "/my/local/repository/path",
      "secondaryLocalRepositoryPath": "/my/other/local/repository/path/"
    },
    "contentUses": {
      "force": false,
      "source": "source",
      "proxy": "proxy"
    }
  },
  "rame": {...}
}

RAME:

Configuration File Modifications:

• In order to maintain compatibility between OnePanel, OnePanelDesktop and RAME configuration files, the latter underwent a small modification.
• Now, the "localRepositoryPath" and "secondaryRepositoryPath" fields come out of the "reachEngine" object and are included inside a new "repositories" object.

Old config file example:

{
  "onePanel": {...},
  "onePanelDesktop": {...},
  "rame": {
    "reachEngine": {
      "url": "https://my-server.com/",
      "apiKey": "reach-engine-valid-api-key",
      "localRepositoryPath": "/my/local/repository/path",
      "secondaryLocalRepositoryPath": "/my/other/local/repository/path/"
    },
    "localCache": {
      "input": "/my/cache/folder/for/RemoteAdobeMediaEncoder/input",
      "output": "/my/cache/folder/for/RemoteAdobeMediaEncoder/output"
    },
    "port": 3001,
    "OUTPUT_FORMAT": ".mp4"
  }
}

which now becomes:

{
  "onePanel": {...},
  "onePanelDesktop": {...},
  "rame": {
    "reachEngine": {
      "url": "https://my-server.com/",
      "apiKey": "reach-engine-valid-api-key"
    },
    "repositories": {
      "localRepositoryPath": "/my/local/repository/path",
      "secondaryLocalRepositoryPath": "/my/other/local/repository/path/"
    },
    "localCache": {
      "input": "/my/cache/folder/for/RemoteAdobeMediaEncoder/input",
      "output": "/my/cache/folder/for/RemoteAdobeMediaEncoder/output"
    },
    "port": 3001,
    "OUTPUT_FORMAT": ".mp4"
  }
}