Avid/MEWS considerations

Assets transferred from GV STRATUS to Avid via MEWS retain GV STRATUS markers and keywords. In Avid Media Composer, a GV STRATUS marker displays a red indicator and a GV STRATUS keyword displays a yellow indicator.

GV STRATUS supports operation with multiple MEWS engines running on separate servers. Each MEWS engine supports up to 3 concurrent transcode jobs at a time.

To ensure the MEWS Service machine(s) are correctly configured and the required license exists, you should check whether the resources provided per MEWS Service are registered in the GV STRATUS Control Panel via Core | Resource Management | Resource Monitor. The status of the MEWS license and MEWS Server machine should be Online on the Resource Monitor. Below are corresponding display of both MEWS licenses in SabreTooth and the Resource Monitor:

SabreTooth MEWS Licenses	SubResource Provider in Resource Monitor
STRATUS-XCODECONTROLMEWSEXT	MEWS
STRATUS-XCODECONTROLMEWS	MEWS-ELITE

When editing HD material you must use an HD project. When editing SD material you must use an SD project.

The Avid sequence can be of mixed codecs but they must be the same definition/standard.

The GV STRATUS rule that imports an Avid sequence must use a transcode format that matches the Avid Media Composer Project window Format settings. If transcoding, an HD project must use an HD transcode format and an SD project must use an SD transcode format. If not transcoding, select As Source.

For a standalone Avid Media Composer workstation, configure Media Composer as follows:

In Media Creation settings, on every tab set Video Drive and Audio Drive to the C: drive.
In Export Settings, set Export As to AAF and for both Video/Data Details and Audio Details, do the following:
- Set Export Method to Consolidate Media.
- Set all Media Destinations to Media Drive and select Use Media Creation Settings.

For a system with AVID ISIS, do the following:

Install Avid ISIS Client Manager on the following
- The machine where the XCode Control Engine is running
- The machine where MEWS is running
- Every Avid Media Composer workstation
Configure Avid ISIS Client Manager as follows:
- Map a drive, such as drive Z:, to the ISIS share.
- Configure the user to the internal system account, which by default is GVAdmin
For an AVID ISIS Media Composer workstation, configure Media Composer as follows:
- In Media Creation settings, on every tab set Video Drive and Audio Drive to the drive letter, such as drive Z:, mapped to ISIS.
- In Export Settings, set Export As to AAF and for both Video/Data Details and Audio Details, do the following:
  - Set Export As to AAF.
  - Set Export Method to Link to (Don't Export) Media.
  - Set all Media Destinations to Media Drive.
Configure GV STRATUS as follows:
- The GV STRATUS Xcode Control Engine Service and the MEWS Service must be installed to use the internal system account, which by default is GVAdmin.
- In GV STRATUS Control Panel Locations Configuration settings, Location Path must point to the \MXF\ subfolder on Avid ISIS and Host Name must point to the hostname of the Avid Media Composer workstation.
- Create an Import Rule Watchfolder, which is a share that can be accessed by the Rules Engine and the Avid Media Composer workstations.
- Create an Import Rule as follows:
  - Source: The Import Rule Watchfolder
  - Destination: K2 folder
  - Transcode Format: a MEWS format that matches the Avid project.
  - Avid Server Type: Isis
  - Avid Media Host: The Isis server name
  - Set Rule Conditions to trigger on .aaf file extension