EDIUS/GV Render Engine Setup

Install/upgrade EDIUS and GV Render Engine software as directed by standard instructions in GV STRATUS customer documentation. Make sure you follow the proper sequence for installation and running applications.
Verify that the V: drives of your K2 Summit system(s) have been shared, in order to allow the GV Render Engine(s) to access them.

Note: If the GV Render Engines are clients of a K2 SAN, the K2 SAN’s V: drive does not need to be shared.
Add an EDIUS project folder at the root of the V: drive, as directed by standard instructions in GV STRATUS customer documentation.
In GV STRATUS Control Panel, set the UNC path as follows:
- For EDIUS XS and Workgroup, click Applications | EDIUS | EDIUS Project and set Default project location to the UNC path of the above EDIUS folder. For a GV STRATUS Express system with K2 Summit standalone systems, use a path such as the following:
  \\K2SummitStandaloneName\V\[EDIUSFolderName]
- For the GV Render Engine server, click Core | MDI Configuration | Add | Summit and do one of the following:
  - Select Standalone for the type of K2 device. Then set the UNC path for the K2 Summit standalone system, use a path such as the following:
    \\standalone_summit\V

If you have EDIUS Workgroup or EDIUS XS workstations, on the Render Engine configure Plug-in settings as follows:

These settings must be the same as those on your EDIUS Workgroup workstations. The settings identify the storage locations EDIUS accesses. A K2 storage location can be a K2 Summit standalone system or for a K2 SAN, the K2 Media Server with role of file system server (FSM).

From the Windows desktop, click Start | All Programs | Grass Valley | XREAdminConsole. XREAdminConsole opens.
In XREAdminConsole, open Plug-in. Settings opens.
In the Importer/Exporter tree-view, click K2 (SAN). Server settings open.
For the Configure automatically setting, take note of the following:
- If the Configure automatically check-box is selected, the K2(SAN) drives will be automatically populated after each installation or software upgrade.
  Note: If the K2 Summit MDI has UNC path settings configured for third party storage, K2 central, or K2 Summit standalone; each server will be mapped according to its UNC path and not to a drive letter.
- If the Configure automatically check-box is not selected, configure the K2 storage location following these steps below.
In Server section, click Add. The Server Settings dialog box opens.

Verify or make settings as follows.

Table 1. Server Settings
Setting	Value
Name	Enter a name that identifies the K2 storage location to display in the folder view.
Address	Enter the IP address or DNS name of the server that is the K2 storage location.
Address(Backup)	If the K2 storage location is a redundant K2 SAN, the IP address or DNS name of the redundant K2 Media Server with role of file system server (FSM).
Username	Enter the user name required when making the connection to the server configured above. For example, GVAdmin.
Password	Enter the password required for the user name configured above.
Domain	Enter the domain for the user credentials configured above. If not a domain account, leave this setting blank.
Storage Drive	Select the K2 storage location. It must be a drive available on the local system. For a K2 SAN this is typically the V: drive. For a K2 Summit standalone system this is typically a mapped network drive.
Show only SNFS drives	For a K2 SAN, select this setting. For a K2 Summit standalone system, clear this setting.
Connection Test	Click this button to test the connection to the server with the settings entered in the Server settings dialog box.

Click OK to save settings and close.

Follow the instructions in the this Topic Library to complete EDIUS and GV Render Engine setup.