Verifying the GV I/O configuration

  • Valid signal feed must be connected to the inputs of GV I/O server.
  • The required licenses have been added to the GV I/O Live Ingest and Playout Server. For more info, refer to SabreTooth GV I/O license process.
  • Embedded Security Manager on the GV I/O device had been set to Enabled mode.
  • For the GV I/O client of GV AMS Pro - Advanced Media Storage system, the V: drive of the GV I/O had been mapped to the UNC path of the system's hi-res media storage.
  • For GV I/O Standalone devices, share the V: drive with “Everyone”.
  • For GV I/O devices with SD and HD workflows, the configuration can be done via GV STRATUS Control Panel or the GV I/O web configuration utility.
  • For GV I/O devices that support UHD and NMOS workflows, configuration must be done via the GV I/O web configuration utility only. For more info, refer to Configuring the GV I/O Live Ingest and Playout Server.

Within the GV STRATUS system, do the following to verify the GV I/O Live Ingest and Playout Server is configured properly. Grass Valley recommends the GV STRATUS Control Panel is only configured on the Core Server:

  • For GV I/O Live Ingest and Playout Standalone Servers, do the following:
    • Create a new Grass Valley Media Server MDI in the GV STRATUS Control Panel for each GV I/O under MDI Configuration settings, just as you would a K2 Summit Standalone. For more info, refer to Grass Valley Media Server MDI standalone settings.
    • Reboot the GV I/O devices and Core Server before continuing.
  • For GV I/O Live Ingest and Playout Server with iSCSI or LAN Connect media connection, do the following:
    • Run the iSCSI Initiator on each GV I/O server with iSCSI connection before attempting to configure them in K2Config.
    • Add the GV I/O server(s) as GV I/O Live Ingest & Playout devices in K2Config and configure them as you would a K2 Summit client. GV I/O supports either LAN Connect or iSCSI connection.
    • Sync K2Config to the GV STRATUS Core server.
  • In the GV STRATUS Control Panel application, do the following:
    • In Core | MDI Configuration settings, re-save all Grass Valley Media Server MDIs with GV I/O servers attached.
    • In Core | Proxy Config | Proxy Settings tab, re-select check-boxes, resave the proxy settings and verify in Test Connections tab that the STRATUS GV I/O Client Device Types are connected with the proxy server. This must be done to push proxy settings to the GV I/O.
    • Reboot the GV I/O servers.
    • After the GV I/O servers have finished booting, log in manually to each GV I/O server. You must log in with a user account that has full permissions to the proxy share. If shared storage is used for high resolution media, the user account must also have full permissions to the shared storage location used for high resolution media storage.
    • Then, reboot the GV STRATUS Core server. This sequence is required for the changes to take effect.
    • Verify that you can see the STRATUS GV I/O Appliance in the Core | K2 Storage | K2 Standalone Storage tab for the GV I/O standalone server.
    • Verify that you can see the STRATUS GV I/O Client in the Core | K2 Storage | K2 SAN Storage tab for the GV I/O client in K2 Summit SAN or GV ION - Advanced Media Storage system.
    • Then in General | Format tab, add formats according to input/output signal feed, if they are not readily available.
    • In the General | Channels | GV I/O tab, verify that the GV I/O channels are displayed. The Channel Format should be set according to signal feeds configured to each channel. Change the Channel Format setting to match the format of signal feed already connected to the channel.
    • Configure GV I/O channels according to GV I/O Record Channel settings or GV I/O Playout Channel settings.
    • To add GV I/O channels to the Scheduler tool: In the Applications | Ingest | Channel Setup tab, add one or more GV I/O Device channels:
      • Type of device: Select either SAN Client or Standalone Client.
      • SAN Name: Choose a SAN with one or more GV I/O devices.
      • Primary Device: Select the desired GV I/O device in the drop-down list.
      • Select Standalone: Select the standalone GV I/O device in the drop-down list.
      • Channel Type: Select Recorder.
      • Client Channel: Select a channel from the drop-down list.
      • Router Destination: Select a router destination, if applicable.
      • Timecode Format: Select Time of Day.
  • In the GV STRATUS application, do the following:
    • In the Scheduler tool, verify that GV I/O channels configured in Ingest settings of the GV STRATUS Control Panel are displayed and able to record.
  • To add GV I/O channels to the Channel Panel: In the Navigator panel, expand the Tools node and select Channel Panels. Right-click on the desired Channel Panel and select Open With | Inspector.
    • Verify that all configured GV I/O Live Ingest and Playout Servers are displayed.
    • Add one or more channels from a GV I/O Live Ingest and Playout Server.
    • Verify that GV I/O channels have a button and you can set the Timecode Source to Time of Day or a specific Start Time for each GV I/O channel.
    • Verify that you can record on those GV I/O channels.
  • To add GV I/O servers to the GV STRATUS Rundown application: In the GV STRATUS Control Panel, go to Applications | Rundown | Media tab. Add one or more GV I/O Device as the Playout Server(s) and click Save.

    Then, launch the GV STRATUS Rundown application and go to Tools | Options | Channel Configuration tab to add GV I/O channels as playout channels.

    Verify that GV I/O channels configured in GV STRATUS Rundown are able to playback assets.


Copyright © 2020 Grass Valley Canada. All rights reserved. Specifications subject to change without notice. GV STRATUS 6.10 gvtp_20200811_04:57:17