Load the configuration schema

1. Under Select an application, click the line starting with Curator for Adobe - ....This line will mention one of the range of the Adobe products that Curator works with, but configuration will be applied to them all.
2. The com.IPV.Extension.config.json configuration type will be displayed when the above line is selected, along with the latest schema version present within Curator.
   If you are configuring Curator for Adobe as part of a Curator release, this will be the correct schema to use. If there are older schemas already configured on the server, these will also be available for use with older versions of Curator for Adobe as needed. These can be inspected and modified from the version dropdown.
   NOTE: If you are installing an individual upgrade to Curator for Adobe, you may need to manually add the updated schema prior to configuration.
3. Beneath the schema version dropdown, a list of available configuration profiles (usually defined for a workgroup) will be displayed in grey. Select Default to configure the application for all users. This will load the schema fields for configuration under the Selected Profile header (shown to the right of the dropdowns), confirming the Configuration Version:NOTE: If necessary, it is possible to configure settings differently for different groups of users. 
   NOTE: Other settings listed in the setup instructions below can be found by scrolling down in the Selected Profile section or by searching the page (ctrl+F (PC) or cmd+F (Mac)) for the heading or field name listed.

Necessary configuration to use Curator for Adobe out of the box:

1. Export Destinations (this affects Premiere Pro and After Effects)
   This allows you to set export destinations (types), the source for the corresponding Adobe Media Encoder preset files (.epr) used during the Local Conform export to AME, and the mediastore used during Process Engine's Remote Conform (this includes the definition of the presets file).
   IPV provides three example .epr files in the system settings delivered with Process Engine, which can be found within its Resources subdirectory. These can be replaced with your own settings as required.
   To set this up, scroll to or search for Export Destinations. Beneath the heading, there will be three example epr files under three destination names: High Quality, Web and Social and Low Bitrate.
   1. Create or rename the Export Destinations as required. These will be available in Curator for Adobe. Copy settings from the given examples if you are creating new ones.
   2. Configure Media Store to use for the Remote Conform in the given destination. If defaults for the examples are not suitable, you should seek IPV support if you need a new mediastore or you need to modify anything in a mediastore beyond the EPR file. For more details on this, see Setting Export locations for Curator for Adobe panel.
   3. Configure the EPR file path settings for Local Conform: EPR File Path (Windows) and EPR File Path (Mac) -  these should match the share locations set up in Process Engine (and its Mac mounting equivalent where in use).
      Below is an example for the High Quality destination, where the system folder of Curator is deployed on Example.ProcessEngineServer, shared as a Storage, mounted as Storage on Macs and the environment during the basic configuration was set out to be Example-Production:
      \\Example.ProcessEngineServer.com\Storage\Curator\Example-Production\Resources\EPR Files\HighQuality.epr
      /Volumes/Storage/Curator/Example-Production/Resources/EPR Files/HighQuality.epr
   4. Configure the folder path settings for Local Conform: Local Export Folder Path (Windows) and Local Export Folder Path (Mac). These paths need to be set to a network location accessible to Xfer Agent and Process Engine Agent e.g.: 
      \\Example.ProcessEngineServer.com\Storage\Curator\WorkInProgress\Conform Engine
      /Volumes/Storage/Curator/WorkInProgress/Conform Engine
      
   5. For out of the box functionality, leave the remaining settings as they are and repeat the configuration steps for the EPR, folder path and the Media Store if needed for all required Destination Names under Export Destinations. 
      
      
2. HLS Playback Settings (this affects Premiere Pro and After Effects)  
   Scroll down to the HLS Playback Settings section and enter the Video Server Address.
   For default out of the box functionality, this is the Curator Gateway server where proxies are routed from:
   
   
3. Image Proxy Settings are required to configure the image preview pop-ups that appear in Curator for Adobe prior to placing images in the project file.
   To configure these settings, pull up the PROXY-V3 mediastore in Process Engine Monitor to see the metadata settings used in proxy creation. If the ProxySubFolderMetadataKey and ProxyFileMetadataKey values differ from the out of the box values (ProxySubFolder and ProxyFile), you will need to adjust the values for the Path Metadata and File Metadata here to match. If the values match, there is no further configuration for proxy previews. (for more information on setting this up, please refer to the  Curator Clip Link web.config settings listed in  this article).

   

4. Appcues Settings (these settings affect all Adobe applications)
   Appcues allow users access to guides and introductions of new features directly from within their Curator application. To enable these, tick the Enabled checkbox. The other parameters should remain unchanged to receive IPV-generated Appcues for the correct application:
   
   
   

The below values should not require modification, but the basic setup needs these to agree across the system:

1. The Video Create Production Settings and Graphics New Project Settings (these affect appropriate Adobe applications). Out of the box settings will match the Create Production plugin out of the box settings for Clip Link, as set in the <CreateProduction> tag, found in the Curator Server installation path for all users in: Config\w[]-u[]-win[]-m[]\WebApplications\CuratorClipLink\Plugins\CreateProduction.config, and similarly for the deprecated Curator Clip Select.
   The Base Location will be Productions by default, and the metadata values will form the following path, in descending order: Production, Format, Destination. 
   These can be set separately as required, but users will need to be briefed that productions will then be saved in the locations defined for each of the applications (Curator for Adobe in one location versus Clip Link in another) and/or type (Media project for Premiere Pro and After Effects in one location versus Graphics projects for Photoshop and Adobe Illustrator in another).
2. Markers (this affects Adobe Premiere Pro).
   Import Markers Settings
   Curator Clipmarks are normally imported with imported media - this setting can be disabled by removing the tick from the Enable? checkbox. The named metadata view in this section can also be altered - this dictates which metadata will be imported in, with an optional selection filter for which subclips will be imported and a setting for the separator symbol.Show Live Markers
   Clipmarks can also be pushed live to a parent media imported from Curator for Adobe - this behaviour is enabled by default in an out of the box configuration. To disable live markers and set a different view for selection facets for which subclips will be imported, alter settings here: To set the view and the separator symbol for the metadata values shown in Adobe Premiere Pro, alter the values here:
   

   
   

The remaining values provided out of the box are suitable or necessary for use, unless the system has been otherwise modified.

1. In the Project Management Setup section, the metadata and Labels (hi-res) are correct to use in a standard system and should remain as provided.
   The metadata are only in use in Curator for Adobe and are needed for the user to see the project name, to manage its status (for example, whether it is in use or checked out by any other user) and store the structure of the bin in the saved project where relevant (not in graphics where the project is a single file). Users of the projects must have write permissions to these metadata. The default out of the box Editors workgroup will have all relevant permissions provided.
   The Labels are relevant to graphics within Adobe apps and the import of Hi-Res material, and should not be changed in the current use of the Curator System. These will be sent out to the Curator System during check-in, and the download file for graphics will be matched via this label.
   
   
2. In the Import settings.
   1. The ability to import as a proxy is set up by default, and additional settings are available for enabling the import of markers - see the Markers step in the section above. Further named import types apply to importing and connecting/swapping imported assets to the high-resolution media files and will need to be configured manually. These can be seen when right-clicking Import or Connect in Curator for Adobe: 
      See below for more information on which import type should be set.
   2. The analogous Place Embedded function in Curator for Adobe running in the graphics applications always uses a hi-res image and is managed using the set labels, while media files are imported using the set metadata. 
   3. Hi-Res Settings 
      Do not Remove the default Hi-Res settings - see the below screenshot for uses of +Add.
      The following default settings are provided out of the box for Hi-res import:
      • Name (default: Hi-Res) is the name that will appear in the drop-down next to Proxy to let you select the type of the import.
      • Media Store (default: HI-RES - the mediastore that defines the file types for workflows and is used during ingest).
      • Metadata Names - these allow you to set metadata in which the path to the media asset is stored. This needs to be provided (by default this will be HiResPath - this should only be adjusted if the PathMetadataKey has been set to different metadata in HI-RES MediaStore, for example on an older system)
      • Labels should remain hi-res. At the time of writing, Curator does not use labels other than hi-res.
      • Use as default MOGRT Source defines the default import method for Mogrt files (compressed graphics projects that encapsulate output from an After Effects project). Mogrts need to be imported as Hi-Res in order to decompress and enable links to Curator assets within. This checkbox should therefore remain ticked for the Hi-Res import type, or one of them if more than one is declared.
        
      • + Add - You can add an additional import type for source files that may be stored in addition to the default Hi-res, giving it a separate name. For example, additional import types could be added for a mezzanine file, or for a different type of Hi-Res that was ingested. In order to add these, you will need to know a mediastore that was created for their ingest and metadata holding the storage path. 
      • Directly below the setting for the Default Import Type, you are able to choose a type of default import (when not using the drop-down, but directly selecting the Import button or Connect button) that applies when users launch any version of the Curator for Adobe Panel for the first time. Following that, the import type can be saved using Curator for Adobe local settings. Leaving the field empty (default) sets the fresh launch import to default to Proxy.
        
      • The Check Hi-Res Accessibility checkbox should be ticked in order to check that the Hi-Res file is accessible before doing a swap. When this setting is enabled, you can use multiple Hi-Res paths - the first available Hi-Res will then be used.
      • If Hi-Res is requested for import but is inaccessible (usually because it has been archived) the process defined in Restore Hi-Res Process Definition will be called upon to restore the asset using Process Engine.
   4. The remaining Import settings applicable to Hi-Res are displayed directly below these settings. These provide path swapping for Macs (these can usually be used as provided out of the box) and where letter definitions of shared drives are used in customers' domains.
      Please note that the Swap Drive Letters checkbox needs to be ticked in order for the settings defined in The Mappings Between Drives section below this to apply.